roadmap
Use when the user wants outcome-based delivery phases or exit criteria at docs/product/roadmap.md. Drafts or re-sequences the document. Triggers on "build the roadmap", "what are our delivery phases", "phase exit criteria". Requires product.md. Re-authoring is also how an existing roadmap.md gets critiqued or revised — docs-review checks writing quality and cross-document consistency, not sequencing soundness. Do NOT use for epic breakdown or work paths (tasks), PRD (product), per-work-item technical design (tdd), tasks (tasks), or architecture detail (solution).
- License 许可
- MIT
- 最近更新
- 2026-08-20
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- roadmap
- license
- MIT
- metadata
- { "owner": "product", "author": "Carinya Parc", "version": "2.0", "work_shape": "planning", "output_class": "delivery-artefact" }
- description
- Use when the user wants outcome-based delivery phases or exit criteria at docs/product/roadmap.md. Drafts or re-sequences the document. Triggers on "build the roadmap", "what are our delivery phases", "phase exit criteria". Requires product.md. Re-authoring is also how an existing roadmap.md gets critiqued or revised — docs-review checks writing quality and cross-document consistency, not sequencing soundness. Do NOT use for epic breakdown or work paths (tasks), PRD (product), per-work-item technical design (tdd), tasks (tasks), or architecture detail (solution).
- allowed-tools
- Read Write Glob Grep
- argument-hint
- [--context <notes>]
02 资源文件 1
- 资产文件assets/roadmap.template.md1.0 KB
03 SKILL.md 正文
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
<artifacts> [Provided by the caller: docs/product/product.md, docs/product/backlog.md (epic list with dependencies), cross-squad dependency context.] </artifacts>
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
Related skills
product,tasks,solutiondocs-review— review or critique an existing roadmap.md
04 同仓库更多 Skills
skill-name
Replace with description of the skill and when the agent should use it.
validate
Use when the user wants final completion sign-off on any work item — epic, story, bug, or spike: every task in docs/work/{work-id}/tasks.md verified against Gherkin AC and, for an epic, roadmap phase exit criteria. Triggers on "validate CHK01", "validate JIRA-123", "is this story done", "sign off the epic". Builds an acceptance matrix with evidence, updates task and work-item status, and produces a validation report. Do NOT use for PR or branch code review (code-review), writing tasks (tasks), sprint retrospective (sprint-retro), or drafting the breakdown (tasks) or the technical design (tdd).
ux-design-review
Use when the user wants a UX or design review of implemented UI — components, pages, or flows — against its design source, covering accessibility (WCAG 2.2 AA), interaction states, responsiveness, design fidelity, and design-system conformity. Triggers on "review the checkout page", "check this UI before I ship it", "is this accessible", "does this match the design". Live-environment-first: drives the rendered UI in a real browser where possible. Works with any framework or design tooling. Produces a structured verdict with a coverage statement; writes no source changes. Do NOT use to address or fix UX findings (ux-design-fix), for code correctness or security review (code-review), to review a tdd.md document (docs-review), or to implement features (implement).
ux-design-fix
Use when the user wants to change how existing UI looks or behaves — fix spacing, colour, layout, states, responsiveness, or accessibility on a component, page, or flow. Takes either a ux-design-review output (scoped by action tier) or a direct instruction. Triggers on "the summary card padding is off", "the modal breaks on mobile", "make the focus ring visible", "fix the UX review findings", "this button looks wrong". Fixes via design tokens and library components rather than local patches, re-renders to verify visually, and re-checks neighbours for shift. Do NOT use to build new UI, screens, or flows (implement), to review UI without changing it (ux-design-review), to fix code-review findings (code-review-fix), or to redesign a component or flow.
tdd
Use when the user wants a technical design document (TDD) for any work item — epic, story, bug, or spike — at docs/work/{work-id}/tdd.md, in skeleton or full mode. Pass a work item ID (CHK01, or a Linear/Jira/GitHub key like JIRA-123). Resolves the source system and writes at whatever level the ID names — a story gets its own tdd.md beside its parent epic's, not nested inside it. Cite solution.md — do not re-narrate architecture. Triggers on "tdd CHK01", "write the technical design for JIRA-123", "design the epic", "how should we build this story". For reviewing an existing tdd.md, use docs-review instead. Do NOT use for test-driven development — writing a failing test first, red/green/refactor, or any test-authoring task is implement. Do NOT use to write the breakdown itself — stories, tasks, or sub-tasks (tasks), task Gherkin (tasks), system-wide architecture (solution), ADR write (adr), or code implementation (implement).
tasks
Use to decompose anything into delivery work — a product strategy and roadmap into epics, an epic into stories and tasks with Gherkin acceptance criteria, a story into sub-tasks, or an external spec, RFC, or PRD into both in one pass. Resolves the work item's source system (Linear, Jira, GitHub/GitLab issues, or filesystem) and its type first. Writes docs/product/backlog.md and docs/work/{work-id}/tasks.md, or the tracker directly when one is resolved. Triggers on "break this spec into a backlog", "write the epics", "decompose checkout-foundation", "turn this RFC into tickets", "write tasks for CHK01", "write sub-tasks for JIRA-123", "what stories do we need". EARS with --ears. Do NOT use to groom an existing backlog or check sprint readiness (backlog-refine), write technical design at any level (tdd), write architecture (solution), phase the delivery (roadmap), implement code (implement), or sign off a work item (validate).