agentleFS
Sign inStart free
gologo13gologo13/agent-skills/skills/roadmap/SKILL.md

roadmap

Skill0 starsChanged 9 months agoMITView on GitHub

Analyze the codebase and generate a visual roadmap of potential features and improvements; keywords: mermaid, diagram, performance, roadmap. Use only on explicit request; skip in routine implementation discussions.

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create these todos with todo_write and update as you go:

    line 12
  2. Distinctive:

    Create timeline diagram (phased overview)

    line 16
  3. Distinctive:

    Create current vs proposed flowchart (integration points)

    line 17
  4. Distinctive:

    Ask user which features to plan

    line 18
  5. Distinctive:

    Look for opportunities in these areas:

    line 22
  6. Distinctive:

    Ask: "Would you like me to create a plan for any of these features?"

    line 95

“Common” is measured: kept by at least 6 in 10 of the 40 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Roadmap: Feature & Improvement Suggestions

Analyze the codebase and generate a visual roadmap of potential features and improvements. Track progress with todos.

Todo List

Create these todos with todo_write and update as you go:

  1. Scan codebase architecture, patterns, and conventions
  2. Identify feature gaps and improvement opportunities
  3. Create timeline diagram (phased overview)
  4. Create current vs proposed flowchart (integration points)
  5. Ask user which features to plan

Analysis Focus

Look for opportunities in these areas:

  • Missing common patterns (auth, caching, error handling, logging)
  • Performance optimization opportunities
  • Developer experience improvements
  • User-facing feature enhancements
  • Code quality / refactoring candidates

Diagram 1: Timeline Overview

A phased roadmap showing features by effort level.

  • 3 sections: Quick Wins, Medium Effort, Strategic
  • Group related features within each phase
  • Colors: warm neutrals with themed variables
%%{init: {'theme': 'base', 'themeVariables': {
  'primaryColor': '#F7F7F4',
  'primaryBorderColor': '#D4D4D0',
  'primaryTextColor': '#333',
  'secondaryColor': '#EAEBE7',
  'tertiaryColor': '#FEF0ED'
}}}%%
timeline
    title Feature Roadmap
    section Quick Wins
        Feature A : Low effort, high impact
        Feature B : Simple addition
    section Medium Effort
        Feature C : Requires some refactoring
    section Strategic
        Feature D : Architectural change

Diagram 2: Current vs Proposed Flowchart

Visual distinction between existing and suggested features.

  • Solid borders (#F7F7F4, #D4D4D0): existing features
  • Dashed orange borders (#FEF0ED, #F34F1D): proposed features
  • Solid arrows: direct dependencies
  • Dashed arrows: suggested connections
flowchart TB
    subgraph Current["Current Features"]
        direction LR
        A[Existing A]
        B[Existing B]
    end
    subgraph Proposed["Proposed Features"]
        direction LR
        C[Suggested A]
        D[Suggested B]
    end

    A --> C
    B -.-> D

    style A fill:#F7F7F4,stroke:#D4D4D0
    style B fill:#F7F7F4,stroke:#D4D4D0
    style C fill:#FEF0ED,stroke:#F34F1D,stroke-dasharray:5 5
    style D fill:#FEF0ED,stroke:#F34F1D,stroke-dasharray:5 5

Output

Render directly in chat (don't write files):

  1. Brief assessment of current codebase state
  2. Prioritized feature list (5-8 items with rationale)
  3. Timeline diagram (phased overview)
  4. Current vs Proposed flowchart (integration points)
  5. Ask: "Would you like me to create a plan for any of these features?"

Mermaid Syntax

  • Timeline sections: section Name
  • Subgraphs: subgraph ID["Name"]
  • Dashed lines: A -.-> B
  • Dashed borders: stroke-dasharray:5 5
  • Special chars need quotes: A["@scope/pkg"]

Download now (ZIP)

  • Other versions47 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 47

    1. cloudposse/atmos★ 1.4ksame name
    2. me2resh/apexyard★ 532same name
    3. andreaskelm/pm-brain★ 234same name
    4. genkovich/sdd★ 187same name
    5. YougLin-dev/Aha-Loop★ 181same name
    6. Ovid/paad★ 147same name
    7. facebookresearch/autoform-bot★ 130same name
    8. Mehdibargach/claude-code-pm-skills★ 97same name
    9. joshuadavidthomas/agent-skills★ 49same name
    10. spmtitsolution/OpenBA-Kit★ 38same name

    37 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use sequence, stakeholder-update and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • GTMifySkill

      sequence

      Build a multi-channel outreach cadence (email + LinkedIn + phone) for a target persona or named prospect. Use when the user says 'build a sequence', 'outreach cadence', 'multi-touch sequence', 'multi-channel cadence', 'follow-up sequence', or needs a coordinated multi-channel play. Do NOT use for single cold emails — use cold-email instead.

      Also in 3 projects that use this

    • AnthropicSkill

      stakeholder-update

      Generate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing versions.

      Also in 3 projects that use this

    • EpistatesSkill

      strategy

      Plan weekly or monthly X content strategy. Use when the user wants to plan their content calendar, set growth goals, build a content pipeline, or think strategically about their X presence.

      Also in 3 projects that use this

    • Itsokay-coSkill

      discover

      Automated pattern discovery — finds what correlates with your best and worst sleep nights. Scans workouts, meals, caffeine, tags, gut scores, and timing patterns. Use when the user wants to know what actually affects their sleep.

      Also in 4 projects that use this

    • GitHubSkill

      prd

      Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

      Also in 7 projects that use this

    • thoughtbotSkill

      challenge

      Pressure-test an assumption, decision, or inherited constraint — Socratic cross-examination that forces you to defend or abandon your position

      Also in 3 projects that use this

  • In this repository31 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free