Tech stack decision phase for the enterprise pipeline. Auto-detects which technology domains need decisions (runtime, framework, database, auth, etc.), presents options with decision matrices, and locks choices into stack-decisions.json for downstream consumption by enterprise-plan. Incumbent bias for existing…
Evidence-based verification before any completion claim. No 'should work' or 'probably fine' — paste fresh test output or don't claim done. 7-check verification sequence. Use before committing or claiming work is complete.
Use when enterprise work is about to be declared complete and the claim needs fresh evidence, postcondition tracing, and an explicit proof-scope verdict.
Use when starting a feature, significant refactor, enterprise hardening effort, GitHub issue intake/processing, or multi-stage bugfix that needs end-to-end workflow control, portable repo-local artifacts, and explicit proof scope.
Multi-orchestrator fleet management. Takes a batch of tasks, analyzes dependencies and boundaries, assigns optimal models (Opus/Sonnet/Haiku/Worker), sets up isolated worktrees, and dispatches concurrent orchestrators with merge coordination. Use when the user has multiple tasks to parallelize across agents.
Lightweight rapid development workflow. Agent Harness with minimal ceremony. No research agents, no review agents, no TDD enforcement. Just analyze, plan, build, verify. Use for small features, config changes, quick fixes that are too big for "just do it" but don't need the full pipeline. Invoked with /full-cycle-fast…
Research-heavy development workflow. Agent Harness + Compound Engineering deep research. 8+ parallel research agents explore best practices, framework docs, security patterns, and performance before any code is written. Use for unfamiliar territory, new integrations, architectural decisions, or when you want maximum…
TDD-first development workflow. Agent Harness + Superpowers TDD discipline. Every task starts with a failing test. No code without a test first. Use for bug fixes, features where correctness is critical, or when you want maximum test coverage. Invoked with /full-cycle-tdd followed by a description.
Complete structured development workflow combining Agent Harness, Superpowers, Compound Engineering, and Agent Teams. Use when starting any new feature, bug fix, refactor, or development task. Invoked with /full-cycle followed by a description of what to build. Interactive planning then fully autonomous execution.…
Use when turning a diagnose.buildpacket.v1 JSON packet, bug diagnosis, or agent handoff into GitHub issues or issue comments, especially when the user wants ready-for-agent work items created without implementing code.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".