feat: evolutionary PROJECT.md system
PROJECT.md evolves throughout project lifecycle: - Requirements have states: Validated, Active, Out of Scope - Decisions track outcomes: Good, Revisit, Pending - Phase transitions update requirements and log decisions - Milestone completions trigger full PROJECT.md review STATE.md now references PROJECT.md (not a copy): - Claude reads PROJECT.md directly for full context - Smaller STATE.md footprint (~100 lines) - Project Reference section with core value and focus Brownfield projects infer Validated requirements from existing code. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -38,7 +38,7 @@ If missing STATE.md or ROADMAP.md: inform what's missing, suggest running `/gsd:
|
||||
|
||||
- Read `.planning/STATE.md` for living memory (position, decisions, issues)
|
||||
- Read `.planning/ROADMAP.md` for phase structure and objectives
|
||||
- Read `.planning/PROJECT.md` for project vision (brief summary only)
|
||||
- Read `.planning/PROJECT.md` for current state (What This Is, Core Value, Requirements)
|
||||
</step>
|
||||
|
||||
<step name="recent">
|
||||
|
||||
Reference in New Issue
Block a user