A command is the one you type. It runs exactly when you ask it to, and never before.
1,184 commands across 626 plugins.
Post-execution verification gate. Tests, lint, type-check, then see it working.
Complete a worktree task. Verifies all phases are complete, commits code changes (excluding planning files), merges to target branch, and removes worktree. Can…
Show execution status dashboard. Usage: /plan-cascade:dashboard [--verbose|-v] [--json]
Generate a technical design document. Auto-detects level: project-level from mega-plan.json, or feature-level from prd.json. Provides architectural context for…
Build web client application (Next.js, React, Vite)
Deep bug investigation with architectural fix plan generation - works with any executor (loop or swarm)
Run a lightweight Socratic design dialogue (3-5 AUQ rounds) and write a spec markdown file before any implementation work. Use BEFORE /plan feature when…
End session with verification, commits, and documentation
Classify and apply a version bump to a machine-readable contract (JSON Schema, API spec, config schema) — version literals, consumer compatibility, changelog…
This file is read by parent commands (cycle-design, story-new) that need to run content-spark logic inline instead of via nested Skill invocation. The…
Main entry point for the Craft harness. Start here to work on stories.
Post-cycle analysis — QA, UX, Creative, and Style audits using MCP browser tools.
Run proposal refine/review/deep-lit loops in parallel until proposals are ready.
Open the Compound V observability dashboard — a present-only, read-only browser view over docs/superpowers/execution/** (runs, epics, per-job status,…
Execute a Compound-V-ready plan, manifest, or run-id via batched parallel multi-backend dispatch. Accepts a bare plan path (auto-materializes the manifest), or…
Drive an EPIC — chain several features into one autonomous, resumable, dependency-ordered build on a single branch. Each feature runs through the FULL v1.0…
Unified front-end planning entrance - implementation/architecture plan or testing strategy. The implementation path is taken by default; when the user clearly…
Identify and clean up front-end dead code, unused exports, outdated components, styles and dependencies under validation protection.
Conduct a standardized review of the specified file or recently changed front-end code, output a graded review report and save it as a Markdown file.
Audit the rules/ directory for missing foundational principles; output gap list with priority and justification
Validate ~/.claude/settings.json hooks block — event names, file existence, executability, matcher syntax; --fix repairs common issues
Catch Resend-class bug (isError: false on HTTP 4xx/5xx) across all MCP server tool handlers
Generate the master PRD from a user-provided requirements document
Generate the UX PRD companion document from design requirements
Quick Docker Compose build and start with full output
Analyze and optimize Claude Code's context configuration (analyze, optimize, or reset).
Continue working on a change - create the next artifact (Experimental)
Scaffold a new scaffolding-compatible skill: an interactive flow that creates `skills/<name>/SKILL.md` from the canonical template, composes a `TRIGGER`/`SKIP`…
Run the parallel Auto-Harness orchestration flow with worktree workers. /auto-harness:harness-parallel <brief or clarification/spec-approval reply>
Run the Planner side only. First create a detailed clarification questionnaire, then draft the spec after the user answers. /auto-harness:plan <brief or…
Run the parallel Planner side only. First create a clarification questionnaire, then draft the spec after the user answers. /auto-harness:plan-parallel <brief…
Verify project structure aligns with official Claude Code standards
Interactive, section-by-section restructuring of a story into the canonical template through a collaborative conversation. Slower than `improve` on purpose.
© 2026 Flowy · Free and open source
Built for Claude Code · Not affiliated with Anthropic