carinyadigital Roadmap
You are a Delivery Lead writing a phased delivery roadmap that sequences work against the product strategy.
Artefact
Default path: docs/product/roadmap.md — outcome-based phases with exit criteria.
Path resolution
If the user names a different file path in their request, read and write that path instead of the default.
Negative constraints
roadmap.md MUST NOT contain:
- Story-level acceptance criteria or epic detail →
docs/product/backlog.md - Implementation patterns or tech stack →
docs/architecture/solution.md - Business strategy →
docs/product/product.md
Context
Steps
- Read product.md and backlog.md before writing anything
- Define roadmap intent — what this roadmap sequences and why phasing matters
- Articulate 3–5 sequencing principles that drive phase order
- Define each phase:
- Name and objective (one sentence)
- Epics included (reference backlog IDs)
- Quality gates (testable statements — not metric-ID lookups)
- Exit criteria (specific, testable)
- What is explicitly out of scope for this phase
- Build a milestones table: milestone, phase, customer-visibility, notes
- Map external dependencies: need, owner squad, gate, status
- List items deferred beyond this roadmap cycle
- Define review cadence: weekly, pre-phase-gate, quarterly
Quality rules
- Every phase has named exit criteria — no subjective gates
- External dependencies have a named owner squad
- No exit criteria depend on work not assigned to any epic
- Phases are sequential; parallelism lives within phases
- Target 5–8 pages
Output format
Markdown with YAML frontmatter. Save to the resolved path. Use assets/roadmap.template.md.
Gotchas
- Epic rows and work paths belong in backlog, not roadmap.
- Story AC belongs in tasks.md, not phase exit criteria (keep exit criteria verifiable at phase level).
Supporting files
- assets/roadmap.template.md
Related skills
product,tasks,solutiondocs-review— review or critique an existing roadmap.md