roadmap

1# Roadmap
2 
3Generate 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.
4 
5This 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.
6 
7## When to Use
8 
9- Starting a major new product (after deep-research, or from a product brief)
10- Converting a vague idea into an executable plan
11- Planning a multi-week build that will span many Claude Code sessions
12- Before saying "build this" — the roadmap is what you hand Claude Code to execute
13 
14## Inputs
15 
16The skill needs one of these:
17 
18| Input | Where to find it |
19|-------|-----------------|
20| Deep research brief | `.jez/artifacts/research-brief-{topic}.md` (from `/deep-research`) |
21| Product brief | User describes what they want to build |
22| Existing partial app | Read CLAUDE.md + codebase to understand what exists |
23| Competitor to clone/improve | URL or product name — skill analyses it |
24 
25If the user just says "plan a note-taking app on Cloudflare", that's enough — ask clarifying questions as needed.
26 
27## Workflow
28 
29### 1. Establish the Vision
30 
31Before any technical planning, nail down:
32 
33- **One sentence**: What is this? ("A cloud-native markdown knowledge workspace for teams and AI agents")
34…