# Solo Sdd Routing

> Use when Superpowers brainstorming has classified new work as Architectural and a solo developer must decide whether the work needs durable Spec Kit artifacts before implementation.

- Skill: `zokmi/solo-sdd-routing` (Agent Skill)
- Install (CLI): `npx skillmds@latest add zokmi/solo-sdd-routing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zokmi/solo-sdd-routing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: zokmi (https://skillmd.com/u/zokmi)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/zokmi/solo-sdd-routing

---


# Solo SDD Routing

Apply this skill as a policy overlay after Superpowers brainstorming. Do not repeat its Spike, Bounded, or Architectural classification.

## Route

- **Spike or Bounded:** continue with Superpowers. Do not create Spec Kit artifacts.
- **Architectural:** evaluate whether a durable formal specification will reduce requirement or compatibility risk.

Use Spec Kit when one or more of these concerns is material:

- a public API, protocol, file format, or compatibility contract changes;
- persistence, migration, or durable data semantics change;
- multiple subsystems must agree on a new contract or ownership boundary;
- a long-lived architectural decision needs explicit review and traceability;
- requirement ambiguity is significant enough that implementation planning cannot resolve it safely.

If none is material, continue with the Superpowers architectural workflow and its design artifact.

## Risk Signals, Not Gates

Do not use Spec Kit solely because:

- several files or internal modules change;
- implementation may take more than one focused day;
- tests are extensive;
- the implementation is technically difficult;
- UI and internal persistence both change without a new contract.

Complex implementation is not the same as complex specification.

## Output Contract

State one route and the evidence:

- `Superpowers only` — no durable formal specification is justified; or
- `Spec Kit -> spec-handoff -> Superpowers` — identify the contract, persistence, cross-subsystem, long-lived decision, or ambiguity risk.

If discovery exposes a material risk later, stop implementation and rerun this gate. Do not create specification artifacts merely for ceremony.