sdd-workflow | Skill Performance & Reviews | TopRankSkills

TopRank Skills

Home / Skills / tools / sdd-workflow

sdd-workflow

maintained by h2b-dev-studio

star 0 account_tree 0 verified_user MIT License
bolt View GitHub

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: docs/sdd-guidelines.md sections 4, 5, 8, 10

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!

Skill Details

GitHub Stars 0
GitHub Forks 0
Created Jan 2026
Last Updated 5 months ago
tools tools productivity tools

Related Skills

planning-with-files
chevron_right
agent-browser
chevron_right
building-agents
chevron_right
notebooklm
chevron_right
grafana
chevron_right

Build your own?

Join 12,000+ developers contributing to the Claude ecosystem.