enriching-roadmaplisted

# Enriching Roadmap Enriches a confirmed structural roadmap so every chunk becomes self-contained enough for a developer-agent to begin work — adding acceptance criteria, pattern references, and contextual notes without modifying any structural field decomposing-work produced. **Position:** decomposing-work (ROADMAP.md structural) → enriching-roadmap (acceptance criteria, pattern refs, notes) → planning-software (orchestration plan). **Inputs:** confirmed ROADMAP.md; approved ARCHITECTURE.md (source for pattern references and component context); PRD.md (source of testable success criteria); workflow tier; optionally `.interface-design/system.md` — if present, derive design-specific acceptance criteria for UI chunks. If the tier was not specified, infer from the roadmap (1-3 chunks = Quick, 4-8 = Standard, 9+ or phased DAG = Thorough), state the inference, and proceed. **Output:** the same ROADMAP.md, modified in place — three fields appended to each chunk (`Acceptance criteria`, `Pattern references`, `Contextual notes`). Do not alter existing fields (`Type`, `Component`, `Status`, `Size`, `Depends on`, `Files`, `Description`). Present the enriched roadmap for human review before treating it as the working baseline. **Not covered:** chunk structure and dependencies (decomposing-work), plan creation (planning-software), technology-specific implementation guidance (developer-agent skills). ## Workflow ### Step 1: Read All Inputs Read PRD.md, ARCHITECTURE.md, and ROADMAP.