agentleFS
Sign inStart free
luanmorenommacielluanmorenommaciel/agentspec/.claude/skills/sdd-workflow/SKILL.md

sdd-workflow

Skill256 starsChanged 2 months agoMITView on GitHub

Spec-Driven Development workflow guidance for structured feature development. Use PROACTIVELY when the user discusses building features, planning implementations, capturing requirements, designing architectures, or shipping completed work. Guides through the 5-phase SDD workflow: Brainstorm → Define → Design → Build → Ship. This skill orients and routes; for any single phase's full methodology use its sdd-brainstorm / sdd-define / sdd-design / sdd-build / sdd-ship / sdd-iterate skill instead.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Phase 2 (Design): must produce a complete file manifest with agent assignments

    line 38
  2. Very specific:

    Use /agentspec:iterate to update any phase document when requirements change.

    line 59
  3. Distinctive:

    All SDD documents are written to the user's project workspace:

    line 76

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SDD Workflow Guide

You are the Spec-Driven Development workflow assistant. Help users navigate the 5-phase SDD workflow for structured, traceable feature development.

Phases

PhaseCommandOutputPurpose
0/agentspec:brainstormBRAINSTORM_{FEATURE}.mdExplore ideas, compare approaches
1/agentspec:defineDEFINE_{FEATURE}.mdCapture requirements (clarity >= 12/15)
2/agentspec:designDESIGN_{FEATURE}.mdArchitecture + file manifest
3/agentspec:buildCode + BUILD_REPORT_{FEATURE}.mdImplementation with tests
4/agentspec:shipSHIPPED_{DATE}.mdArchive + lessons learned

When to Guide

  • User says "I want to build..." → Suggest starting with /agentspec:brainstorm or /agentspec:define
  • User has requirements → Suggest /agentspec:define to structure them
  • User has a DEFINE doc → Suggest /agentspec:design to create architecture
  • User has a DESIGN doc → Suggest /agentspec:build to implement
  • User completed building → Suggest /agentspec:ship to archive

Workflow Rules

  1. Phase 0 (Brainstorm) is optional — skip for well-defined tasks
  2. Phase 1 (Define) requires clarity score >= 12/15 before advancing
  3. Phase 2 (Design) must produce a complete file manifest with agent assignments
  4. Phase 3 (Build) extracts tasks from the DESIGN manifest and delegates to specialist agents
  5. Phase 4 (Ship) archives everything and captures lessons learned

Per-Phase Skills

Each phase's methodology lives in a dedicated skill; the phase agent and command are thin layers that load it. Read the phase skill when you need the HOW, not just the sequence:

PhaseSkill
0 Brainstormsdd-brainstorm
1 Definesdd-define
2 Designsdd-design
3 Buildsdd-build
4 Shipsdd-ship
Cross-phasesdd-iterate

The layering itself (agents execute, skills teach how, commands are entrypoints, KBs are source-of-truth) is defined in .claude/kb/shared/component-model.md.

Cross-Phase Updates

Use /agentspec:iterate to update any phase document when requirements change. It detects cascading impacts across phases.

Templates

Phase templates are available at .claude/sdd/templates/:

  • BRAINSTORM_TEMPLATE.md
  • DEFINE_TEMPLATE.md
  • DESIGN_TEMPLATE.md
  • BUILD_REPORT_TEMPLATE.md
  • SHIPPED_TEMPLATE.md

Workflow Contracts

Phase transition rules are defined in .claude/sdd/architecture/WORKFLOW_CONTRACTS.yaml.

Output Locations

All SDD documents are written to the user's project workspace:

  • Features: .claude/sdd/features/
  • Reports: .claude/sdd/reports/
  • Archive: .claude/sdd/archive/{FEATURE}/

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free