spec-to-design

Spec to Design

You are running the automated implementation pipeline. Given a feature spec and its design docs, you will:

1. Align design docs to the spec
2. Produce detailed implementation plans
3. Align implementation plans to each other and the spec
4. Execute the implementation via parallel subagents

This skill requires zero user interaction. The user is unavailable. Do all work autonomously, committing at each phase.

Arguments

Parse the following from the user's command or calling skill:

• SPEC_PATH (required): Path to the feature spec (e.g., docs/specs/user-auth-spec.md)
• DESIGN_GLOB (optional): Glob for design phase docs (default: derived from spec path — replace -spec.md with -design-phase-*.md in docs/superpowers/specs/)
• PLAN_GLOB (optional): Glob for plan docs (default: derived from spec path — replace -spec.md with -implementation-phase-*-task-*.md in docs/superpowers/plans/)
• --slug SLUG (optional): Feature slug for commit messages and file naming (default: derived from spec filename)

Prerequisites

1. Verify SPEC_PATH exists. If not, notify Teams and stop.
2. Verify at least one file matches DESIGN_GLOB. If not, notify Teams and stop.
3. Read all input files to confirm they're valid markdown.

Phase 1: Design Alignment

Purpose: Ensure design phase docs are coherent with the spec and with each other.

Steps:

1. Read the spec at SPEC_PATH thoroughly.
2. Read ALL design docs matching DESIGN_GLOB.
3. Review holistically for:
   • Alignment to the spirit of the spec (not just surface conformance)
   • Internal consistency across design phases (terminology, data models, use cases)
   • End-to-end coherence (does Phase 1's output feed correctly into Phase 2's input?)
   • Integration seams between phases
4. Fix any contradictions, inconsistencies, or misalignments directly in the design docs.
5. If no issues found, note that alignment is clean.
6. Commit:

git add docs/superpowers/specs/
git commit -m "docs: align {SLUG} design phases to spec"