roadmap

User Input

$ARGUMENTS

Setup

1. Read .coco/config.yaml for:
   • discovery.prd_path (default: docs/prd.md)
   • discovery.analysis_dir (default: docs/analysis)
   • discovery.roadmap_dir (default: docs/roadmap)
   • project.specs_dir (default: specs)
   • issue_tracker.provider
2. $ARGUMENTS specifies the release name (e.g., "v1.0", "MVP"). If empty, use AskUserQuestion to ask for the release name.
3. Check if a roadmap already exists at {roadmap_dir}/{release}.md:
   • If yes, enter update mode (load existing roadmap)
   • If no, enter create mode

Execution

1. Load Context

PRD (required): Read {discovery.prd_path}. If the file does not exist, ERROR: "No PRD found at {discovery.prd_path}. Run /coco:prd first."

Analysis docs (optional): Glob {discovery.analysis_dir}/*.md and read all found documents. Extract:

• Key findings from each
• "Implications for Roadmap" sections

Constitution (optional): Read .coco/memory/constitution.md if it exists. Use project principles to inform prioritization.

Existing specs (optional): Glob {specs_dir}/*/design.md (with {specs_dir}/*/spec.md as legacy fallback). These represent features already designed -- they should appear in the roadmap as already-scoped items.

Existing roadmap (update mode only): Load {roadmap_dir}/{release}.md. Preserve Change Log and completed feature statuses.

2. Extract Feature Candidates

Build a consolidated feature list from all sources:

Source	How
PRD "Feature Candidates" table	Parse rows: name, description, goal(s), priority
Analysis "Implications for Roadmap" sections	Extract referenced features and adjustments
Existing specs/ directories	Add as already-specced features

Deduplicate by name/description similarity. Output the consolidated list as text (do NOT put it inside AskUserQuestion — it must be visible before the prompt):

Feature Candidates for {release}
================================
| # | Feature | Source | Already Specced | Notes |
|---|---------|--------|-----------------|-------|