# Spec Handoff

> Use when approved Spec Kit artifacts must be checked for consistency, traceability, scope, and implementation readiness before Superpowers executes the work.

- Skill: `zokmi/spec-handoff` (Agent Skill)
- Install (CLI): `npx skillmds@latest add zokmi/spec-handoff`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zokmi/spec-handoff/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/spec-handoff

---


# Spec Handoff

Treat approved requirements as authoritative. This skill validates the Spec Kit-to-Superpowers boundary; it does not redesign the feature or duplicate an implementation plan.

## Readiness Gate

Read the applicable `spec.md`, `plan.md`, and `tasks.md`. Confirm:

- requirements and acceptance criteria are unambiguous and mutually consistent;
- the plan implements the approved behavior without silently changing it;
- component boundaries, state ownership, interfaces, persistence, errors, and testing strategy are sufficiently defined for the approved scope;
- tasks are executable, ordered where dependencies exist, and have observable completion conditions;
- important edge cases and failure paths have verification work.

## Traceability Gate

For every material requirement, establish this semantic chain:

```text
requirement -> acceptance criterion -> task -> test or verification
```

IDs are optional; coverage is not. Report any requirement with no implementation task, any acceptance criterion with no verification, and any task with no approved requirement.

## Scope Gate

Every task must trace to approved scope. Remove or return speculative infrastructure—future registries, generalized platforms, migration frameworks, or extension points—unless a requirement needs it now. Technical elegance alone does not justify an orphan task.

## Handoff Result

- **Ready:** identify the authoritative artifacts and hand their executable tasks to the appropriate Superpowers workflow.
- **Not ready:** list the exact contradiction, missing decision, orphan task, or unverifiable criterion; return to Spec Kit for correction.

When implementation discovers requirement ambiguity or a needed architectural change, stop, update and reapprove the relevant artifacts, rerun this gate, then resume. Never resolve product ambiguity by silently changing implementation behavior.