superspec

Plugin superspec from marketplace superspec-dev in anupam20sep/IRA. Commands read from the repo's manifest — 27 days ago.

Skills (16)

• superspec-architect

  Use when designing the technical solution architecture, translating requirements into decisions, data models, and contracts. Follows SuperSpec's unified design template (Technical Context, Architecture, Decisions, Data Model, Contracts) and produces design.md.

• superspec-explore

  Use when exploring ideas, requirements and design before implementation. Helps turn ideas into fully formed designs and specs through natural collaborative dialogue.

• superspec-fix

  Use for targeted bug fixes that do not need a full spec lifecycle. Reproduces with a failing regression test, applies a minimal patch, skips spec.md/design.md/plan.md, and hands off to superspec-ship for validation.

• superspec-forge

  Use when you have an execution map or task plan ready to implement — runs the autonomous forge loop that dispatches fresh implementer and reviewer subagents per task, tracks state via the forge-loop state machine (next-task/record-task-result/forge-status), and escalates stuck tasks instead of retry

• superspec-ingest

  Use when bootstrapping a spec from existing documentation or code rather than greenfield exploration. Extracts functional requirements with provenance, flags source conflicts, writes sources.lock, and hands off to superspec-scope.

• superspec-init

  Use once per repository to bootstrap SuperSpec. Runs the init CLI, asks lite vs full mode, and creates constitution.md, specs/, and .superspec/ at the repository root.

• superspec-plan

  Use when you have a spec or requirements for a multi-step task, before touching code — writes comprehensive TDD plans with full task decomposition and FR traceability

• superspec-program

  Use when coordinating multiple spec workstreams in one repository. Maintains program.md at the repo root with a backlog table and Open Decisions, with per-row ownership for safe concurrent edits.

• superspec-refine

  Use when your specification contains open questions or [NEEDS CLARIFICATION] markers. Asks up to 5 targeted clarifying questions, collects answers, and writes them back into spec.md to resolve ambiguities before moving to architecture.

• superspec-route

  Use when transforming a task plan into a parallelizable execution schedule with model routing, windowing, and verification gates

• superspec-scope

  Use when you have a brainstormed design and need to formalize it into a numbered, testable specification. Generates a spec.md with functional requirements (FR-###), success criteria (SC-###), and prioritized user stories with acceptance scenarios.

• superspec-ship

  Use when implementation is complete, validation has passed, and you need to decide how to integrate the work - runs SuperSpec's clean-validation gate, then guides completion of development work by presenting structured options for merge, PR, or cleanup

• superspec-status

  Use to get a program-wide or repo-wide status view. Reads program.md, infers lifecycle stage per spec from artifacts, calls forge-status for in-flight specs, and renders a single consolidated status table.

• superspec-validate

  Use when about to claim a feature is complete and ready for release — runs the actual verification commands (coverage matrix, plan linting, constitution compliance, execution gates) and confirms output before allowing completion claims; evidence before assertions always.

• superspec-worktree

  Use when starting plan or forge work that needs isolation from the current workspace — creates isolated git worktrees with smart directory selection, safety verification, and baseline tests; pairs with superspec-ship for cleanup

• using-superspec

  Use when starting any conversation - establishes how to find and use SuperSpec skills, requiring skill invocation before ANY response including clarifying questions

Subagents (3)

• implementer

  Use when dispatching a fresh subagent to implement exactly one task from a SuperSpec plan.md, with zero prior context, following red-green-refactor TDD.

• spec-reviewer

  Use when reviewing a SuperSpec spec.md for quality — every FR testable, every user story independently demonstrable, no lingering ambiguity.

• task-reviewer

  Use when reviewing one completed SuperSpec task's implementation against its brief and the constitution — spec compliance and code quality verdicts.

MCP servers (1)

• superspec

  runs: npx -y @superspec-dev/[email protected] mcp

Hooks (1)

• SessionStart

  echo 'SuperSpec: invoke the using-superspec skill before any task — explore/ingest → scope → refine → architect → plan → route → forge → validate → ship.'

Similar plugins