# Sdd Full Lifecycle

> Turn a feature request into verified implementation results by composing the catalog's atomic specification, planning, implementation, and test skills. Use when a user wants the complete spec-driven development lifecycle for an approved repository change rather than one isolated SDD phase.

- Skill: `knuckles-team/sdd-full-lifecycle` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add knuckles-team/sdd-full-lifecycle`
- Raw SKILL.md: https://api.skillmd.com/api/skills/knuckles-team/sdd-full-lifecycle/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: Knuckles-Team (https://skillmd.com/u/knuckles-team)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/knuckles-team/sdd-full-lifecycle

---


# SDD Full Lifecycle Workflow

## Steps

### Step 0: spec-intake-wizard [skill: spec-intake-wizard]

Invoke `$spec-intake-wizard` with the workflow request.

Expected: `intake_result`

### Step 1: spec-generator [skill: spec-generator] [depends_on: Step 0]

Invoke `$spec-generator` with `intake_result`.

Expected: `specification`

### Step 2: spec-verifier [skill: spec-verifier] [depends_on: Step 1]

Invoke `$spec-verifier` with `specification`.

Expected: `verified_specification`

### Step 3: task-planner [skill: task-planner] [depends_on: Step 2]

Invoke `$task-planner` with `verified_specification`.

Expected: `implementation_plan`

### Step 4: sdd-implementer [skill: sdd-implementer] [depends_on: Step 3]

Invoke `$sdd-implementer` with `implementation_plan`.

Expected: `implementation_result`

### Step 5: automated-test-runner [skill: automated-test-runner] [depends_on: Step 4]

Invoke `$automated-test-runner` with `implementation_result`.

Expected: `test_result`

## Execution

- **Run first:** Step 0 — `$spec-intake-wizard`.
- **After Step 0:** Step 1 — `$spec-generator`.
- **After Step 1:** Step 2 — `$spec-verifier`.
- **After Step 2:** Step 3 — `$task-planner`.
- **After Step 3:** Step 4 — `$sdd-implementer`.
- **After Step 4:** Step 5 — `$automated-test-runner`.

**Execution:** If graph-os is reachable, offload the whole DAG via `graph_orchestrate action=execute_workflow` (or the `kg-delegate` skill) for true parallel/swarm execution. Otherwise execute the steps natively in dependency order: run steps with no unmet `depends_on` in parallel, then their dependents.

