Roadmap
Plan and execute entire application builds.
Install
npx skills add jezweb/claude-skills --skill roadmap -g -a claude-code -y- Repository
- jezweb/claude-skills1.1k
- Category
- Testing
- Updated
- 26d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Plan and execute entire application builds. Generates phased delivery roadmaps, then executes them autonomously, phase by phase, committing at milestones, deploying, testing, and continuing until done or stuck. Modes: plan (generate roadmap), start (begin executing), resume (continue from where you left off), status (show progress). Triggers: 'roadmap', 'start building', 'resume the build', 'keep going', 'build the whole thing', 'execute the roadmap', 'what phase are we on'.
Roadmap
Generate a comprehensive technical roadmap for building an entire application. Detailed enough that Claude Code can pick up any phase and execute it autonomously for hours.
This is not a high-level strategy doc. It's a delivery blueprint, every phase has concrete tasks, every task is actionable, and the whole thing is ordered so you can build from phase 1 through to launch without backtracking.
When to Use
- Starting a major new product (after deep-research, or from a product brief)
- Converting a vague idea into an executable plan
- Planning a multi-week build that will span many Claude Code sessions
- Before saying "build this", the roadmap is what you hand Claude Code to execute
Inputs
The skill needs one of these:
| Input | Where to find it |
|---|---|
| Deep research brief | .jez/artifacts/research-brief-{topic}.md (from /deep-research) |
| Product brief | User describes what they want to build |
| Existing partial app | Read CLAUDE.md + codebase to understand what exists |
| Competitor to clone/improve | URL or product name, skill analyses it |
If the user just says "plan a note-taking app on Cloudflare", that's enough, ask clarifying questions as needed.
Workflow
1. Establish the Vision
Before any technical planning, nail down:
- One sentence: What is this? ("A cloud-native markdown knowledge workspace for teams and AI agents")
- Who: Primary users, secondary users, agents? ("Jez first, then Jezweb team, then clients")
- Why: What existing tools fail at? What's the gap? ("Existing tools are headless, you can't browse them or stumble across things")
- Constraint: Stack, budget, timeline, must-haves? ("Cloudflare, must have MCP, needs to be a PWA")
- Not building: What's explicitly out of scope? ("No real-time CRDT collab, no plugin ecosystem")
2. Define the Stack
Based on the vision and constraints, lock in the technical stack:
