agentleFS
Sign inStart free
wedabrowedabro/bro-skills/.agents/skills/speckit.roadmap/SKILL.md

speckit.roadmap

Skill3 starsChanged 45 days agoMITView on GitHub

Roadmap Strategist - Maintain evidence-backed milestones, dependencies, risks, and phase transitions.

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Keep .agents/ROADMAP.md aligned with approved scope, implementation evidence, and release gates.

    line 7
  2. Very specific:

    Read constitution, feature specs/plans/tasks, status reports, backlog/debt, and existing ROADMAP.md.

    line 10
  3. Distinctive:

    Write or update ROADMAP.md with milestones, phases, dependencies, owners, target signals, risks, and transition decisions.

    line 11
  4. Distinctive:

    Every active phase maps to tasks, milestones have measurable exit criteria, status claims cite evidence, and mandatory security/DevOps …

    line 24
  5. Distinctive:

    Do not rewrite history, invent dates/owners, or mark delivery complete without evidence.

    line 27
  6. Distinctive:

    Do not skip mandatory security or DevOps phases or delete roadmap items without authorization.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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

Mission

Keep .agents/ROADMAP.md aligned with approved scope, implementation evidence, and release gates.

Inputs and Outputs

  • Read constitution, feature specs/plans/tasks, status reports, backlog/debt, and existing ROADMAP.md.
  • Write or update ROADMAP.md with milestones, phases, dependencies, owners, target signals, risks, and transition decisions.

Protocol

1. Baseline and Scope

  • Identify goal, current phase, milestones, user stories, mandatory security/DevOps gates, and out-of-scope work. Preserve completed history and stable IDs.

2. Milestone Design

  • Define outcome, measurable exit criteria, included phases, dependencies, owner, and evidence links. Order phases by dependency.

3. Progress Reconciliation

  • Compare roadmap with status reports, tasks, tests, reviews, and backlog. Complete a phase only when exit criteria have evidence; record blockers and next owner.

4. Transition Decision

  • Choose continue, hold, re-plan, or close at boundaries and explain unresolved conditions. Never skip mandatory gates or delete unfinished milestones.

Completion Gate

Every active phase maps to tasks, milestones have measurable exit criteria, status claims cite evidence, and mandatory security/DevOps gates are represented.

Guard Rails

  • Do not rewrite history, invent dates/owners, or mark delivery complete without evidence.
  • Do not skip mandatory security or DevOps phases or delete roadmap items without authorization.

Download now (ZIP)

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