SDD Workflow Management

VerifiedSafe

Manage SDD document state, handoffs, and versioning for web-playground. Enables multi-agent/session continuity with progress tracking and escalation handling.

Sby Skills Guide Bot
DevelopmentIntermediate
306/2/2026
Claude Code
#sdd#workflow#state-management#handoff#versioning

Recommended for

Our review

Manages SDD state, handoffs, and versioning for multi‑agent or multi‑session development continuity.

Strengths

  • Clear tracking of document phases and ownership
  • Smooth handoff between sessions or agents
  • Structured escalation and blocking handling
  • Semantic versioning for changes

Limitations

  • Requires manual discipline to keep state accurate
  • Local YAML file – no automatic sync across sessions
  • Overkill for trivial projects or single‑session work
When to use it

Use this skill when collaborating on a Software Design Document across multiple sessions or agents to ensure continuity and accountability.

When not to use it

Avoid when the project lacks a formal design document or when work is completed in a single session with no handoff needed.

Security analysis

Safe
Quality score88/100

The skill only creates and modifies local state files (.sdd/state.yaml, .sdd/handoff.md) using standard file operations like mkdir and YAML editing. No external scripts, network calls, deletion commands, or obfuscated payloads are involved.

No concerns found

Examples

SDD Workflow Status
Run SDD workflow – show current state and next actions.
Session Handoff
Prepare a handoff document for the SDD project. Summarize completed items, current blockers, and next steps.
Propagate Changes
Propagate changes from foundation to requirements – update alignments and re-run verification.

name: sdd-workflow description: | Manage SDD state, handoffs, and versioning for web-playground. Use when: tracking progress, handing off between sessions/agents, propagating changes. Triggers: "sdd workflow", "sdd status", "propagate changes", "handoff"

Web Playground SDD Workflow

Track state and enable multi-agent/session continuity for SDD work.

State File

Location: .sdd/state.yaml

version: 1
updated: 2025-01-15T10:00:00Z
current_phase: requirements  # foundation | requirements | design

documents:
  foundation: { status: verified, version: 1.0.0, owner: human }
  requirements: { status: partial, version: 1.1.0, owner: claude }
  design: { status: draft, version: 0.1.0, owner: unassigned }

packages:
  react-sample: { foundation: verified, requirements: draft }

gaps: []
escalations: []

Status Values

| Status | Meaning | |--------|---------| | draft | Created, not verified | | verified | Passed verification | | blocked | Waiting on escalation resolution | | partial | Some items verified, some draft |

Owner Values

| Owner | Meaning | |-------|---------| | claude | Current Claude session owns this | | human | Human is responsible | | unassigned | Available for next agent |

Instructions

1. Initialize

mkdir -p .sdd

Create .sdd/state.yaml with current_phase: foundation.

2. Claim Ownership

Before modifying a document, update owner:

documents:
  requirements: { status: draft, owner: claude }

3. Track Progress

Update state after completing work:

documents:
  foundation: { status: verified, version: 1.0.0, owner: human }

4. Escalate When Blocked

When needing human decision:

escalations:
  - id: ESC-001
    type: scope_decision
    description: "Should QUALITY-MINIMAL allow lodash?"
    items_affected: [REQ-003]
    status: pending  # pending | resolved

Set affected items to blocked status.

5. Propagate Changes

Foundation change -> Re-verify Requirements (@aligns-to links)
Requirements change -> Re-verify Design (@derives links)

6. Session Handoff

At session end, write .sdd/handoff.md:

# SDD Handoff - 2025-01-15

**From:** claude
**To:** human (or next claude session)

## Ownership Transfer
- requirements: claude -> unassigned

## Completed
- Foundation verified with SCOPE-MONOREPO, QUALITY-TYPESCRIPT anchors

## In Progress
- REQ-002: 50% complete, needs verification criteria

## Blocked
- REQ-003: waiting on ESC-001 (scope decision)

## Next Steps
1. Resolve ESC-001 (human decision needed)
2. Complete REQ-002 verification criteria
3. Run alignment check

Versioning

| Change | Bump | |--------|------| | Anchor/REQ deleted or modified meaning | MAJOR | | New anchor/REQ, clarification | MINOR | | Typo, formatting | PATCH |

Multi-Level

Package specs in packages/{pkg}/spec/. Reference root with root:: prefix:

  • root::SCOPE-MONOREPO
  • root::REQ-001

Verification

  • [ ] State file reflects actual document status
  • [ ] Ownership assigned before modifications
  • [ ] Escalations documented when blocked
  • [ ] Handoff enables next agent to continue without questions

Reference

For full details: .claude/skills/sdd-guidelines/reference/guidelines-v4.4.md sections 4, 5, 8, 10

Related skills