Fast single-pass code review of a diff. Use for a quick read-only review of a PR or the current branch — pulls the diff, runs one consolidated pass against the shared severity rubric, and prints a severity-tiered summary. No subagents, never posts. For deep multi-reviewer review use /review-heavy.
Breaks a technical design document into an epic (or several epics) and actionable user stories with acceptance criteria, dependencies, and explicit out-of-scope items. Use this whenever a user shares a design doc, RFC, technical spec, PRD, ADR, or implementation proposal and wants it turned into work items — tickets…
Create a technical design document from a PRD interactively. Walks tdd-[nnn].md section-by-section, then a contracts-[nnn].md companion for field-level wire shapes — surfacing every choice via AskUserQuestion.
Produces a cold-read feasibility findings draft for a technical design. Reads TDD, contracts, PRD, and prior research in a forked context with no conversation history; extracts claims; verifies load-bearing ones via web research; writes .feasibility-[nnn]-draft.md. Used by feasibility-study as its research phase, and…
Pressure-tests a technical design document, runs research in a forked cold-read subagent, walks the user through findings, produces feasibility-[nnn].md. Use when reviewing a TDD, running a feasibility study, sanity-checking a design, or validating whether NFR targets are achievable with the chosen tech.
Multi-phase technical design workflow for adding features to existing codebases. Covers codebase reconnaissance, change strategy, delta-focused integration design, and automated review. Use when extending a system that already exists with established patterns.
Multi-phase technical design workflow for building new systems from scratch. Covers landscape analysis, decision locking, full system design, and automated review. Use when there is no existing codebase or when building an entirely new service/application.
Enforces Python best practices for typing, structure, and tooling during both planning and implementation. Use when designing, planning, or writing Python code, modules, APIs, or applications. Triggers: 'python', 'pytest', 'pydantic', 'dataclass', 'fastapi', 'django', 'flask', 'uv', 'poetry', 'ruff', 'mypy', '.py…
Composable modifier that adds legacy analysis, migration strategy, behavior preservation, and cleanup planning to either the greenfield or feature-integration design workflow. Apply when the task involves replacing, restructuring, or rewriting significant existing code.
Deep, risk-tiered multi-reviewer code review. Sizes the change, fans out to the right set of read-only reviewer subagents in parallel, cross-checks findings with a verification pass, then prints one severity-tiered report and verdict — and optionally posts it to the PR (inline + summary). Never approves or merges.
Subagent-Powered Iterative Coding Engine — A multi-phase SDLC workflow using context-efficient patterns. Subagents for research/planning, main context for implementation with /clear discipline. Activates on: feature requests, multi-step implementations, complex refactoring, mentions of 'spice', 'workflow', 'plan and…
Guides Terraform/HCL configuration structure, module design, state management, and provider usage during both planning and implementation. Use when designing infrastructure, planning Terraform architecture, or writing .tf files. Triggers: 'terraform', 'tofu', 'HCL', '.tf', 'tfvars', 'terraform plan', 'terraform…
Enforces test-driven development via RED-GREEN-REFACTOR when writing code. Use when implementing features, fixing bugs, refactoring, or writing any functional code. Triggers: 'write tests first', 'TDD', 'test-driven', 'red-green-refactor', new feature, bug fix, refactor. Does not apply to pure config files (JSON…
Drafts and refines tickets (Story, Task, Bug, Spike, Epic) with concrete acceptance criteria, observable behaviour, and explicit out-of-scope. Use whenever the work is to write up a piece of work — a story, ticket, issue, AC, "write this up", "turn this into a ticket" — regardless of whether it will be published to…
★not rated 5 1mo agoA123 tokens
originalMIT
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: