superspec

Orchestrate specification-driven development with spec-kit governance and obra/superpowers capabilities.

60|9|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/WangX0111/superspec --skill superspec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superspec
Source: https://github.com/WangX0111/superspec/tree/main
Command: npx skills add https://github.com/WangX0111/superspec --skill superspec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Superpowers Bridge solves the problem of getting from a clear specification to correct, well-tested implementation—without losing momentum when sessions are interrupted or when you lack coverage for edge cases and quality gates.

Core Features & Use Cases

  • Resumable spec-driven workflow: Persists governance, specs, plans, tasks, and execution progress in a project-local .specify/ workspace so work can be resumed safely.
  • Edge-case discovery and refinement: Runs brainstorming to uncover boundary conditions, error scenarios, security/privacy issues, and UX pitfalls, updating the target spec with open questions and logs.
  • Plan-to-tasks execution discipline: Generates phased task breakdowns with execution markers like [TDD], [REVIEW], [SUBAGENT], and [P], then orchestrates implementation with TDD-style verification and human checkpoints.
  • Optional superpowers enhancement with graceful fallback: Uses installed obra/superpowers skills when available for richer brainstorming/planning/execution/review, but always falls back to built-in protocols if not.

Quick Start

Use the skill to create a project constitution, write a feature spec, brainstorm edge cases, then generate a plan and execute implementation with TDD and review gates.

Frequently Asked Questions about superspec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain progress on spec-driven development across interrupted sessions?

To maintain progress on spec-driven development across interrupted sessions, you need a resumable workflow that persists governance, specs, plans, and execution markers in a local `.specify/` workspace. This allows safely resuming implementation from the last checkpoint without losing context.

How do I uncover edge cases and security issues before writing feature code?

To uncover edge cases and security issues before writing feature code, use brainstorming workflows that probe boundary conditions, error scenarios, and UX pitfalls. This refines the target specification by appending open questions and logs to ensure comprehensive requirements coverage.

How do I break down a feature specification into phased tasks for TDD execution?

To break down a feature specification into phased tasks for TDD execution, generate a task breakdown using markers like **[TDD]**, **[REVIEW]**, and **[SUBAGENT]**. This orchestrates implementation with test-driven verification gates and human checkpoints throughout the process.

Do I need to install obra/superpowers to use spec-driven development workflows?

You do not need to install obra/superpowers to use spec-driven development workflows. The system detects optional external `SKILL.md` files for richer brainstorming and execution, but automatically falls back to built-in protocols if those dependencies are missing.

What is the best way to transition from a specification document to a tested implementation?

The best way to transition from a specification document to a tested implementation is using an orchestration workflow that combines edge-case discovery, phased task decomposition, and TDD-focused execution with code review gates. This ensures correct implementation without losing momentum.

Why does my task decomposition workflow lack execution discipline during implementation?

Your task decomposition workflow lacks execution discipline if it omits structured markers like **[TDD]** and **[REVIEW]**. Applying these markers enforces test-driven verification and human checkpoints, ensuring the implementation adheres strictly to the specification plan.