| name | spec-first-superpowers |
| description | Enforces spec-before-code workflow for AI-driven development. Automatically selects Spec-Kit or OpenSpec mode, triages complexity (quick/standard/thorough), recovers session context, and applies quality gates (G0-G4) with inline self-review at every stage. Use this skill whenever the user says "/super-spec", "spec first", "规范先行", or starts any feature, bugfix, or refactor — especially in projects with .spec-mode, .specify/, or openspec/ directories. Even if the user doesn't explicitly ask for spec-driven workflow, activate this skill for any non-trivial code change to prevent skipping the design phase. Orchestrates: Spec-Kit (v0.7.1, Workflow Engine) / OpenSpec (OPSX v1.2.0) + planning-with-files (v2.30.0) + ui-ux-pro-max (v2.5.0, 67 styles, 161 palettes, 14 stacks, 6 specialist skills) + Superpowers (v5.0.7, inline self-review, subagent model selection) + MemPalace (v3.3.0, 29 MCP tools, cross-session memory, knowledge graph).
|
Spec-First + Superpowers Orchestrator v5
Stop the AI from jumping straight to code. Every feature, bugfix, and refactor goes through a specification phase first — because unexamined code is expensive code.
Commands
| Command | Effect |
|---|
/super-spec | Full workflow (auto mode + auto complexity) |
/super-spec force-spec-kit | Force Spec-Kit mode |
/super-spec force-openspec | Force OpenSpec mode |
/super-spec reset | Reset mode selection |
/super-spec upgrade | Check all integrated projects for updates and execute upgrade |
How It Works
Step 1: Pick a Mode
Check for existing signals, then fall back to heuristics:
| Signal | Mode |
|---|
.spec-mode file exists | Use whatever it says |
.specify/ directory | Spec-Kit |
openspec/ directory | OpenSpec |
| Brand new project, < 30 files | Spec-Kit |
| Everything else | OpenSpec (default) |
Save the choice to .spec-mode so future sessions remember it.
For detailed mode workflows, read:
Step 2: Triage Complexity
The AI suggests a level; the user confirms or overrides.
| Level | When | What happens |
|---|
| Quick | Single-file bugfix, typo, config | Simplified spec (/opsx:propose or /opsx:ff) → TDD → archive |
| Standard | Single feature, clear scope | All phases (Phase 3 only if UI) |
| Thorough | Multi-module, architecture decisions | All phases + Agent Teams evaluation |
Step 3: Execute the Pipeline
Phase 0 — Session Recovery (automatic)
If task_plan.md exists from a previous session, read all planning files, query MemPalace for relevant history (if configured), run the 5-Question Reboot Test (Where am I? / Where am I going? / What's the goal? / What did I learn? / What did I do?), then resume from the last checkpoint.
Phase 1 — Specification
Write the spec using the selected mode. Quick tasks use /opsx:propose; standard/thorough use the full flow with /opsx:explore or /speckit.specify. The user must explicitly confirm the spec before moving on.
Gate G1: User confirmed + spec aligns with constitution + inline spec review passed + scope check done.
Phase 2 — Persistent Planning
Generate task_plan.md (numbered checklist with file structure mapping + test points), findings.md, and progress.md using planning-with-files + writing-plans.
Gate G2: Every task has file paths + acceptance criteria + test strategy + inline plan review passed.
Phase 3 — UI/UX Design (conditional)
Triggered only when UI keywords are detected. Invoke ui-ux-pro-max --design-system --persist to generate and persist the design system (v2.5.0: 67 styles, 161 palettes, 57 fonts, 14 tech stacks, 6 specialist skills).
Gate G3: Pre-delivery checklist passed + user confirmed design.
Phase 4 — Implementation
Execute via one of two strategies (AI recommends, user picks):
- Subagent-Driven: Fresh subagent per task + two-stage review (spec conformance → code quality) + model selection per task role + implementer status handling (DONE/DONE_WITH_CONCERNS/NEEDS_CONTEXT/BLOCKED)
- Executing-Plans: Batch execution + checkpoint reviews
TDD throughout. Errors escalate through the 3-Strike protocol → systematic-debugging.
Gate G4: All tests pass + review passed + verification evidence written to progress.md + /opsx:verify passed (if available) + MemPalace archived (if configured).
Phase 5 — Archive
finishing-a-development-branch → update all checkboxes → archive spec artifacts → final progress.md entry → MemPalace diary entry (if configured).
Quality Gates
Each gate is a hard stop — nothing moves forward until all checks pass. If a gate fails, fix the issue and re-evaluate. Full gate criteria: references/quality-gates.md
Anti-Rush Protection
If the user asks to skip the spec phase, politely decline and redirect to /super-spec. The whole point of this skill is preventing premature implementation.
Reference Files
Read these as needed — they contain detailed procedures that would bloat this file:
