sdd-evolve — for Claude Code sdd-evolve, spec-kit-command-cursor, community, for Claude Code, ide skills, Evolve, specifications, implementation, discoveries, reveals

v1.0.0
GitHub

About this Skill

Ideal for Development Agents like Cursor IDE needing to synchronize specifications with implementation discoveries Update specifications with discoveries made during development. Use when implementation reveals new requirements, constraints, or design changes.

Features

Keep specifications in sync with implementation discoveries.
Implementation reveals new requirements
Technical constraints discovered during development
Design changes needed based on learnings
Edge cases found not in original spec

# Core Topics

for Claude Code Evolve specifications implementation discoveries reveals
madebyaris madebyaris
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reviewed Landing Page Review Score: 10/11

Killer-Skills keeps this page indexable because it adds recommendation, limitations, and review signals beyond the upstream repository text.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review Locale and body language aligned
Review Score
10/11
Quality Score
57
Canonical Locale
en
Detected Body Locale
en

Ideal for Development Agents like Cursor IDE needing to synchronize specifications with implementation discoveries Update specifications with discoveries made during development. Use when implementation reveals new requirements, constraints, or design changes.

Core Value

Empowers agents to maintain structured approaches to handling new requirements and technical constraints through categorization of discoveries, refinements, additions, and modifications, streamlining the development process with protocols like SDD Evolve

Ideal Agent Persona

Ideal for Development Agents like Cursor IDE needing to synchronize specifications with implementation discoveries

↓ Capabilities Granted for sdd-evolve

Categorizing implementation discoveries for specification updates
Refining existing requirements based on technical constraints
Adding new requirements to original scopes
Modifying design changes based on learnings and edge cases

! Prerequisites & Limits

  • Requires integration with development environments like Cursor IDE
  • Limited to handling discoveries, refinements, additions, and modifications within the SDD Evolve protocol

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team workflows, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is sdd-evolve?

Ideal for Development Agents like Cursor IDE needing to synchronize specifications with implementation discoveries Update specifications with discoveries made during development. Use when implementation reveals new requirements, constraints, or design changes.

How do I install sdd-evolve?

Run the command: npx killer-skills add madebyaris/spec-kit-command-cursor/sdd-evolve. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for sdd-evolve?

Key use cases include: Categorizing implementation discoveries for specification updates, Refining existing requirements based on technical constraints, Adding new requirements to original scopes, Modifying design changes based on learnings and edge cases.

Which IDEs are compatible with sdd-evolve?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for sdd-evolve?

Requires integration with development environments like Cursor IDE. Limited to handling discoveries, refinements, additions, and modifications within the SDD Evolve protocol.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add madebyaris/spec-kit-command-cursor/sdd-evolve. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use sdd-evolve immediately in the current project.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

sdd-evolve

Install sdd-evolve, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

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
1## Changelog
2
3### [Date] - [Category]: [Brief Description]
4**Context**: [Why this change is needed]
5**Change**: [What specifically changed]
6**Impact**: [How this affects existing work]
7**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

Related Skills

Looking for an alternative to sdd-evolve or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

openclaw-release-maintainer is an AI agent skill for openclaw release maintainer.

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

flags is an AI agent skill for use this skill when adding or changing framework feature flags in next.js internals.

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

pr-review is an AI agent skill for pytorch pr review skill.

★ 98.6k
⑂ 0
Developer