skills.rest
madebyaris
madebyarisCOMMUNITY
Explore all skills by this author →
Website𝕏@arisberikutGitHub

sdd-evolve

Update specification files and changelog after implementation discoveries.

192|21|Updated Sep 19, 2025
Search Tags:#planning#changelog#documentation#specifications#change-management#evolve
One-click install
npx skills add https://github.com/madebyaris/spec-kit-command-cursor --skill sdd-evolve
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-evolve
Source: https://github.com/madebyaris/spec-kit-command-cursor/tree/main/.cursor/skills/sdd-evolve
Command: npx skills add https://github.com/madebyaris/spec-kit-command-cursor --skill sdd-evolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps keep specifications in sync with implementation discoveries during development, ensuring that changes are reflected across all relevant artifacts.

Core Features & Use Cases

  • Change tracking: Detects and document changes to requirements, constraints, and design decisions.
  • Cross-file updates: Updates spec.md, plan.md, tasks.md, and other related artifacts with minimal manual effort.
  • Changelog preservation: Maintains a clear history of evolution decisions for traceability.

Quick Start

After discovering a change, run the evolution workflow to record and propagate updates. For example, update spec.md and add a new entry to the changelog, then proceed with plan and task adjustments.

Frequently Asked Questions about sdd-evolve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep specifications in sync with implementation discoveries during development?▼

To keep specifications in sync with implementation discoveries, you can run an evolution workflow that detects changes to requirements and design decisions, then updates spec.md, plan.md, and tasks.md to reflect the new reality.

What is the best way to track requirement changes across specification and planning files?▼

Tracking requirement changes across specification files involves documenting the evolution of constraints and decisions, then propagating those updates across spec.md and plan.md while preserving a clear changelog history for traceability.

How do I update spec.md and plan.md without losing the history of changes?▼

Updating spec.md and plan.md without losing history requires a change management process that applies cross-file updates while preserving changelog entries, ensuring every evolution decision remains traceable over time.

Can I use change management workflows to update tasks.md alongside specification documents?▼

Yes, change management workflows can update tasks.md alongside specification documents by enforcing cross-file updates, ensuring that task adjustments immediately reflect discoveries surfaced during implementation.

When do I need to evolve documentation after implementation changes?▼

You need to evolve documentation after implementation changes when discoveries surface new constraints or design decisions, requiring you to record updates in the changelog and adjust related artifacts to maintain alignment.

Related Skills

Explore More Software Engineering Skills→
dreamingechoesdreamingechoes
2

spec-driven-development

Draft structured project specs covering requirements, design, testing, and acceptance criteria.

Community
Advanced
rodacatorodacato

sdd-tasks

Create an ordered tasks.md checklist from an accepted SDD-lite plan.

Community
Intermediate
ajsai47ajsai47
11

document-release

Update project markdown documentation by cross-referencing git diffs after code commits.

Community
Advanced
qmuqmu
1

write-changelog

Generate changelog entries from archived tickets and update CHANGELOG.md.

Official
Intermediate