makelore/.project-docs/05-agent-entry/read-before-planning.md

Read Before Planning

Before writing any coding plan, follow this order:

1. Run the Concurrent Task Gate.
2. Read memory-index.md.
3. Read the active task record at .project-docs/30-worklog/tasks/{task_id}.md.
4. Read project-positioning.md.
5. Read current-state.md as the integrated snapshot.
6. Read decision-index.md and system-overview.md.
7. Inspect other locally active task scopes.

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 Concurrent Task Gate and Planning Gate pass.