# Read Before Planning

Before writing any coding plan, follow this order:

1. Run the repository-local Concurrent Worktree Check in `concurrent-task-gate.md`.
2. Read `.project-docs/05-agent-entry/memory-index.md`.
3. Read the active task record, or create one for repository-changing work before planning.
4. Read `.project-docs/00-brief/project-positioning.md`.
5. Read `.project-docs/30-worklog/current-state.md` as the integrated snapshot.
6. Read `.project-docs/10-decisions/decision-index.md` and `.project-docs/20-architecture/system-overview.md`.
7. Inspect other locally active worktrees and any available task records for scope overlap.

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 accepted ADRs 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 integrated context: `.project-docs/90-maintenance/stale-items.md`

Treat shared files as the last integrated snapshot, not as live state from concurrent feature tasks. Do not write a plan until both the repository-local worktree check and Planning Gate pass. No external Skill or task registry is required.