# Sdd Evolve

> Update specifications with discoveries made during development. Use when implementation reveals new requirements, constraints, or design changes. Use when this capability is needed.

- Skill: `tomevault-io/sdd-evolve` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/sdd-evolve`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/sdd-evolve/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/sdd-evolve

---


# SDD Evolve Skill

Keep specifications in sync with implementation discoveries.

## When to Use

- Implementation reveals new requirements
- Technical constraints discovered during development
- Design changes needed based on learnings
- Edge cases found not in original spec

## Protocol

### Step 1: Categorize the Discovery
- **Discovery**: New information that was unknown
- **Refinement**: Clarification of existing requirement
- **Addition**: New requirement not in original scope
- **Modification**: Change to existing requirement
- **Removal**: Requirement no longer needed

### Step 2: Assess Impact
1. Which spec files are affected?
2. Does this change the plan?
3. Are there downstream impacts?
4. Should implementation pause for review?

### Step 3: Document the Change

```markdown
## 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]
```

### Step 4: Update Specs
Modify the appropriate files: `spec.md`, `plan.md`, `tasks.md`, `todo-list.md`.

## Best Practices

1. **Document immediately** — don't wait until end of implementation
2. **Be specific** — include enough detail to understand later
3. **Link to context** — reference related tasks
4. **Assess impact** — flag if review is needed
5. **Preserve history** — never delete, always add changelog
6. **Propagate downstream** — mark stale docs when upstream spec changes

## References

- `references/changelog-format.md` — Standard changelog formats for briefs, specs, and standalone changelogs
- `references/propagation-guide.md` — How to detect and flag stale downstream documents when a spec changes

## Scripts

- `scripts/check-staleness.sh <task-id>` — Compare spec modification dates against plan, tasks, and todo-list

## Integration

- Called during `sdd-implementer` subagent work
- Triggered by `/evolve` command
- Feeds into future `/audit` runs
- Use the ask question tool if change requires stakeholder input

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/madebyaris) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-11 -->