# Read Before Planning

Before writing any coding plan, read these files in order:

1. `.project-docs/05-agent-entry/memory-index.md`
2. `.project-docs/00-brief/project-positioning.md`
3. `.project-docs/30-worklog/current-state.md`
4. `.project-docs/10-decisions/decision-index.md`
5. `.project-docs/20-architecture/system-overview.md`

Then read additional files when relevant:

- Architecture or refactor task: `.project-docs/20-architecture/module-map.md` and `.project-docs/20-architecture/data-flow.md`
- Product or behavior task: `.project-docs/40-domain/business-rules.md` and `.project-docs/00-brief/success-criteria.md`
- Ambiguous terms: `.project-docs/40-domain/glossary.md`
- Decision-sensitive task: referenced ADR files in `.project-docs/10-decisions/`
- Evidence-heavy bug, investigation, or experiment: `.project-docs/50-evidence/evidence-index.md`
- Repeated workflow issue, skipped gate, or skill/script candidate: `.project-docs/60-reflection/reflection-index.md`
- Follow-up, loop, timed check, or restart-point task: `.project-docs/80-commitments/commitments.md`
- Suspicious context: `.project-docs/90-maintenance/stale-items.md`

Do not write a plan until the planning gate passes.