Roadmap Builder
Create execution-ready roadmap through one-question-at-a-time dialogue.
Process
Ask questions one at a time. Use AskUserQuestion tool with clear options.
Questions Sequence
1. Project name?
- Free text input
- Example: "Calculator CLI"
2. Programming language?
- Options: Python, Go, Rust, TypeScript, Java, Other
- If Other: ask for specific language
3. Test command?
- Show common options for selected language:
- Python:
pytest tests/ -v
- Go:
go test ./... -race -cover
- Rust:
cargo test
- TypeScript:
npm test or jest
- Java:
mvn test or gradle test
- Allow custom command
4. Lint command?
- Show common options for selected language:
- Python:
ruff check . or pylint
- Go:
golangci-lint run ./...
- Rust:
cargo clippy --all-targets
- TypeScript:
eslint .
- Java:
mvn checkstyle:check
- Allow custom command
5. One-sentence project goal?
- Free text input
- Example: "Build a command-line calculator with expression parsing"
6. How many phases?
- Options: 2, 3, 4, 5, 6, More than 6
- Recommend: 3-6 phases for most projects
7-N. For each phase, ask:
- Phase name? (e.g., "Foundation", "Core Feature", "Integration")
- Phase goal? (one sentence, what this phase accomplishes)
- Success criteria? (2-4 measurable outcomes)
- Ask: "What are 2-4 things that must work when this phase is done?"
- Examples: "Calculator.add() works", "Tests pass", "CLI parses input"
Build Roadmap YAML
After gathering all info, create roadmap at:
docs/roadmaps/[YYYY-MM-DD]-[project-name-slug]-roadmap.yml
Format:
proj:
name: "[Project Name]"
lang: "[Language]"
test: "[Test Command]"
lint: "[Lint Command]"
goal: "[One-sentence goal]"
phases:
- id: 0
name: "[Phase Name]"
goal: "[Phase goal]"
success:
- "[Success criterion 1]"
- "[Success criterion 2]"
- "[Success criterion 3]"
- id: 1
name: "[Phase Name]"
goal: "[Phase goal]"
success:
- "[Success criterion 1]"
- "[Success criterion 2]"
Validate Roadmap
Check:
- All required fields present
- Phase IDs sequential (0, 1, 2, ...)
- Each phase has 2-4 success criteria
- Valid YAML syntax
Output
Display:
✅ Roadmap created: docs/roadmaps/[filename]
Project: [name]
Language: [lang]
Phases: [count]
To execute:
/autonomous-dev docs/roadmaps/[filename]
To review first:
cat docs/roadmaps/[filename]
Tips for Good Roadmaps
Phase granularity:
- Each phase: 2-8 hours of work
- Too small: overhead of phase management
- Too large: hard to review, risky
Success criteria:
- Specific and measurable
- Testable (can verify with command)
- Clear definition of done
Phase sequencing:
- Foundation first (structure, utilities)
- Core features next (main functionality)
- Integration/polish last (CLI, API, docs)
Examples:
Good success criteria:
- "Calculator.add() returns correct sum"
- "Parser handles nested parentheses"
- "CLI prints result to stdout"
Bad success criteria:
- "Code is good" (not measurable)
- "Everything works" (not specific)
- "Ready for production" (ambiguous)
1---2name: roadmap-builder3description: Interactive roadmap creation through structured questioning, optimized for ephemeral execution4when_to_use: when user wants to create a new development roadmap5version: 3.0.06metadata:7 source: https://skillmd.com/skills/yarlson/roadmap-builder8---910# Roadmap Builder1112Create execution-ready roadmap through one-question-at-a-time dialogue.1314## Process1516Ask questions one at a time. Use AskUserQuestion tool with clear options.1718### Questions Sequence1920**1. Project name?**2122- Free text input23- Example: "Calculator CLI"2425**2. Programming language?**2627- Options: Python, Go, Rust, TypeScript, Java, Other28- If Other: ask for specific language2930**3. Test command?**3132- Show common options for selected language:33 - Python: `pytest tests/ -v`34 - Go: `go test ./... -race -cover`35 - Rust: `cargo test`36 - TypeScript: `npm test` or `jest`37 - Java: `mvn test` or `gradle test`38- Allow custom command3940**4. Lint command?**4142- Show common options for selected language:43 - Python: `ruff check .` or `pylint`44 - Go: `golangci-lint run ./...`45 - Rust: `cargo clippy --all-targets`46 - TypeScript: `eslint .`47 - Java: `mvn checkstyle:check`48- Allow custom command4950**5. One-sentence project goal?**5152- Free text input53- Example: "Build a command-line calculator with expression parsing"5455**6. How many phases?**5657- Options: 2, 3, 4, 5, 6, More than 658- Recommend: 3-6 phases for most projects5960**7-N. For each phase, ask:**6162- **Phase name?** (e.g., "Foundation", "Core Feature", "Integration")63- **Phase goal?** (one sentence, what this phase accomplishes)64- **Success criteria?** (2-4 measurable outcomes)65 - Ask: "What are 2-4 things that must work when this phase is done?"66 - Examples: "Calculator.add() works", "Tests pass", "CLI parses input"6768### Build Roadmap YAML6970After gathering all info, create roadmap at:71`docs/roadmaps/[YYYY-MM-DD]-[project-name-slug]-roadmap.yml`7273Format:7475```yaml76proj:77 name: "[Project Name]"78 lang: "[Language]"79 test: "[Test Command]"80 lint: "[Lint Command]"81 goal: "[One-sentence goal]"8283phases:84 - id: 085 name: "[Phase Name]"86 goal: "[Phase goal]"87 success:88 - "[Success criterion 1]"89 - "[Success criterion 2]"90 - "[Success criterion 3]"9192 - id: 193 name: "[Phase Name]"94 goal: "[Phase goal]"95 success:96 - "[Success criterion 1]"97 - "[Success criterion 2]"98```99100### Validate Roadmap101102Check:103104- All required fields present105- Phase IDs sequential (0, 1, 2, ...)106- Each phase has 2-4 success criteria107- Valid YAML syntax108109### Output110111Display:112113```114✅ Roadmap created: docs/roadmaps/[filename]115116Project: [name]117Language: [lang]118Phases: [count]119120To execute:121/autonomous-dev docs/roadmaps/[filename]122123To review first:124cat docs/roadmaps/[filename]125```126127## Tips for Good Roadmaps128129**Phase granularity:**130131- Each phase: 2-8 hours of work132- Too small: overhead of phase management133- Too large: hard to review, risky134135**Success criteria:**136137- Specific and measurable138- Testable (can verify with command)139- Clear definition of done140141**Phase sequencing:**142143- Foundation first (structure, utilities)144- Core features next (main functionality)145- Integration/polish last (CLI, API, docs)146147**Examples:**148149Good success criteria:150151- "Calculator.add() returns correct sum"152- "Parser handles nested parentheses"153- "CLI prints result to stdout"154155Bad success criteria:156157- "Code is good" (not measurable)158- "Everything works" (not specific)159- "Ready for production" (ambiguous)