Roadmap
Use when you have a large feature, project, or initiative to plan. Breaks it into discrete, sequenced milestones and writes them to a ROADMAP.md that milestone can consume.From its SKILL.md
npx -y skills add bitfootco/bender --skill roadmapAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
4.6 KB, as published. Nobody here has run it
Roadmap
Core Rule
PLAN THE WORK, THEN WRITE IT DOWN.
The output of this skill is a ROADMAP.md with sequenced, single-session milestones in - [ ] format. Every decision made here should be captured in that document — not in conversation history.
Phase 1: Orient
Before asking anything, understand the current state:
- Check whether a
ROADMAP.mdorMILESTONES.mdalready exists. If it does, read it — this may be an update session, not a fresh start. - Run
git log --oneline -15to see what has already shipped. Do not propose milestones for work that's already done. - Read
CLAUDE.mdandREADME.mdfor project context, constraints, and conventions.
Phase 2: Understand the goal
If $ARGUMENTS describes the goal clearly, use it. Otherwise ask one question to establish:
- What are we planning? (the feature, initiative, or project)
- What does "done" look like at the end of the roadmap?
- Anything that is explicitly out of scope?
One question only. If the scope is still unclear after one round, propose a narrower framing rather than asking again.
Phase 3: Draft the milestones
Break the goal into a sequenced list of milestones:
- Each milestone must be implementable in a single session — if it feels larger, split it.
- Sequence matters — put foundational work before dependent work.
- Be concrete — a milestone name should make it obvious what gets built, not just what area it touches. Prefer "Add JWT authentication to the API" over "Authentication work".
- Apply YAGNI — do not add milestones for hypothetical future needs. Plan to the stated goal, not beyond it.
- Don't re-plan completed work — items already in git history should not appear as
- [ ]items. - If milestones have dependency relationships (some can run in parallel), assign milestone IDs (
M1:,M2:) and add{depends: M1}markers sopipelinecan parallelize independent work.
Aim for 3–8 milestones. If the breakdown exceeds 8 items, the goal is probably too large for one roadmap — propose splitting into phases.
Phase 4: Review
Present the draft milestone list to the user. State:
- The goal as you understood it (one sentence)
- The milestone list, in order
- Any sequencing decisions worth calling out (e.g. "X must come before Y because…")
- Anything explicitly left out
Ask for feedback. Incorporate it. One round of revision is expected — if a second round is needed, the goal likely needs narrowing first.
Phase 5: Write the ROADMAP.md
Once the milestone list is approved:
- If no roadmap file exists: create
ROADMAP.mdat the project root. - If one already exists: ask whether to append a new section or replace. Do not silently overwrite.
Write the file using this format:
# Roadmap
## [Goal or Phase Name]
- [ ] Milestone one description
- [ ] Milestone two description
- [ ] Milestone three description
When milestones have parallel potential, use milestone IDs and {depends:} markers:
# Roadmap
## [Goal or Phase Name]
- [ ] M1: Set up project scaffolding
- [ ] M2: Add database schema {depends: M1}
- [ ] M3: Implement API endpoints {depends: M2}
- [ ] M4: Add auth middleware {depends: M2}
- [ ] M5: Integration tests {depends: M3, M4}
- [ ] M6: Add CI config
If all milestones are strictly sequential, IDs and dependency markers are optional.
Use - [ ] for every planned item. Use - [x] only for items already completed. Do not use any other done-marker — milestone parses this format.
After writing, confirm the file path and tell the user they can run /bender:milestone to start executing.
If no bin/ci script or CI command was found in CLAUDE.md during Phase 1, suggest the user add one. Example: "Consider adding your CI/test command to CLAUDE.md (e.g., Run tests: npm test) so milestone and pipeline can discover it automatically."
Hard Rules
- Do not start writing the file until the milestone list is approved.
- Each milestone must fit in one implementation session. Split anything larger.
- Never add milestones for work already in git history.
- Use
- [ ]format — this is whatmilestoneparses. - Do not silently overwrite an existing roadmap. Always ask first.
- YAGNI: plan to the goal, not beyond it.
- When milestones have parallel potential, use milestone IDs and
{depends:}markers.