// Update specifications with discoveries made during development. Use when implementation reveals new requirements, constraints, or design changes.
Generate technical plans from specifications. Use when creating architecture documents, designing system components, or preparing for implementation.
Pattern investigation and technical research before specification. Use when technical approach is unclear, exploring existing solutions, or analyzing codebase patterns. Supports deep research mode for thorough external investigation.
Compare implementation against specifications, identify gaps and issues. Use for code review, quality assurance, and verifying spec compliance.
Execute planned implementations following todo-lists systematically. Use for code generation, building features, and executing SDD plans.
| name | sdd-evolve |
| description | Update specifications with discoveries made during development. Use when implementation reveals new requirements, constraints, or design changes. |
Keep specifications in sync with implementation discoveries.
## Changelog
### [Date] - [Category]: [Brief Description]
**Context**: [Why this change is needed]
**Change**: [What specifically changed]
**Impact**: [How this affects existing work]
**Decision**: [What was decided]
Modify the appropriate files: spec.md, plan.md, tasks.md, todo-list.md.
references/changelog-format.md — Standard changelog formats for briefs, specs, and standalone changelogsreferences/propagation-guide.md — How to detect and flag stale downstream documents when a spec changesscripts/check-staleness.sh <task-id> — Compare spec modification dates against plan, tasks, and todo-listsdd-implementer subagent work/evolve command/audit runs