Creates mechanical contracts with postconditions, invariants, error cases, and consumer maps. Every postcondition is traceable to a test and a code line. Contracts must exist before any source code edits. Use after enterprise-plan.
Creates mechanical contracts with postconditions, invariants, error cases, and consumer maps. Every postcondition is traceable to a test and a code line. Contracts must exist before any source code edits. Use after enterprise-plan.
Use when an enterprise implementation plan exists and work needs a locked contract with postconditions, invariants, consumer mapping, and traceability before build starts.
Systematic enterprise debugging for bugs, failing tests, and unexpected behavior. Reproduce, trace, scan blast radius, identify root cause, then fix with TDD and prevention records.
Full enterprise workflow for legacy enterprise-dev invocations. 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.
Use when starting enterprise work in a new repo, new worktree, unfamiliar package, or new computer, or whenever commands, paths, conventions, portability, or project traps are not yet known.
Use when enterprise work has been built and reviewed and needs a final mechanical ship or release gate before merge, PR readiness, install, deploy, or signoff. Checks proof trace, current diff, architecture, post-merge test kit, rollback, observability, security/privacy, and performance regression readiness.
Use when an approved enterprise design exists and the next step is to turn it into an exact implementation plan with file paths, task boundaries, and verification commands.
End-to-end PR conversation closer and advisory review harvester for enterprise work. Use this whenever the user mentions unresolved PR conversations, Copilot/GitHub review comments, a PR that cannot merge, skipped/non-blocking Copilot feedback, a failed PR review, or asks to address/resolve/learn from PR feedback. It…
End-to-end enterprise workflow for turning multiple refactor opportunities into serial green pull requests. Use when the user asks to identify refactor/domain opportunities, create lane plans, run Helpdesk enterprise gates, use specialist subagents, loop code reviews such as /review, CodeRabbit, Copilot, or GitHub…
Use when enterprise implementation is complete enough for a structured review that separates spec compliance from code quality and classifies drift explicitly.
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.
★not rated 7 1mo agoA46 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: