ROADMAP.md + task files as Claude Code project management pattern¶
Insight: A proven Claude Code workflow uses ROADMAP.md as the single entry point for all project planning, combined with individual task files (numbered 001-description.md, 002-description.md) for each unit of work. The ROADMAP.md is explicitly imported into CLAUDE.md via import syntax, giving the agent full high-level project context for every task. Task files contain specifications, acceptance criteria, implementation steps, and progress checkboxes — creating a loop where the agent works through steps, updates the task file, and waits for instructions.
Detail: The workflow follows four phases: (1) Task Planning — study codebase, update ROADMAP; (2) Task Creation — create numbered task file with specs and acceptance criteria, referencing the last completed task as format example; (3) Task Implementation — follow specs, update step progress, stop after each step; (4) Roadmap Updates — mark completed tasks with ✅. This pattern gives Claude Code persistent grounding across sessions via the ROADMAP, while task files provide granular, scoped context for each work unit. The /status command confirms correct import structure.
Sources
Related: existing entry "Prompt engineering for coding is a systematic skill" in external/claude-code.md — COMPLEMENTS