openspec-superpowers

Plugin openspec-superpowers from marketplace openspec-superpowers-marketplace in OlivierFortier/openspec-superpowers. Commands read from the repo's manifest — 1 month ago.

Skills (22)

• dispatching-parallel-agents

  Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

• finishing-a-development-branch

  Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

• openspec-apply-change

  Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

• openspec-archive-change

  Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

• openspec-bulk-archive-change

  Archive multiple completed changes at once. Use when archiving several parallel changes.

• openspec-continue-change

  Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

• openspec-explore

  Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

• openspec-ff-change

  Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

• openspec-new-change

  Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

• openspec-onboard

  Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

• openspec-propose

  Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

• openspec-sync-specs

  Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

• openspec-update-change

  Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.

• openspec-verify-change

  Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

• receiving-code-review

  Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

• requesting-code-review

  Use when completing tasks, implementing major features, or before merging to verify work meets requirements

• subagent-driven-development

  Use when executing implementation plans with independent tasks in the current session

• systematic-debugging

  Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

• test-driven-development

  Use when implementing any feature or bugfix, before writing implementation code

• using-git-worktrees

  Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

• using-openspec-superpowers

  Route OpenSpec work through automated exploration, artifact creation, isolated implementation, review, verification, synchronization, and archival.

• verification-before-completion

  Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Subagents (1)

• openspec-superpowers

  Routes OpenSpec changes through automated exploration, artifact creation, isolated implementation, review, verification, and archival.

Similar plugins