Implement tasks inside an OpenSpec change. Use when the user wants to start implementation, continue implementation, or advance a change task by task. Prefer using Superpowers to refine and complete one or more unlocked tasks in the current implementation slice.
Continue an OpenSpec change by creating the next ready artifact. Use when the user wants to keep advancing proposal, specs, design, tasks, or similar artifacts without entering code implementation yet.
Enter exploration mode before or during an OpenSpec change. Use when the user wants to brainstorm first, explore options, think through requirements, compare approaches, or is not ready to move into propose/apply yet.
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.
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.
Use when a rough change request needs to be turned into structured OpenSpec proposal-stage artifacts such as a change proposal, RFC, architecture or design doc, spec, and task breakdown before implementation.
Generate blackbox test docs, API docs, or sync API references for OpenSpec changes. Use when a change needs documentation artifacts like blackbox-test.md, api-doc.md, or stable API reference updates.
Generate or refresh project documentation artifacts including surfaces.yaml and codemaps. Use when the user needs to initialize project docs, update codemaps after changes, or create AI-readable project overviews.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.