Implements exactly one task spec end-to-end and verifies it against the command contract. Use when a spec is ready to build, and when review findings need applying to work already done.
Product-manager agent. Reads the backlog, prioritizes, and shapes the next most valuable item into a build-ready task spec. Use when deciding what to work on next, or when a request is too vague to implement and needs acceptance criteria first. Read-only on code; it never implements.
Judges a diff strictly against its task spec, grounded in commands it actually ran, and returns a structured APPROVE/REQUESTCHANGES verdict. Read-only on source; never fixes anything itself. Use when finished work needs an independent verdict before it ships.
Interactively plan a feature with the user, then land it as right-sized build-ready tasks: one spec handed straight to /build, or dependency-ordered backlog issues. Use when the user says "plan X", "break down X", "create issues for X", or brings an idea too large for a single /build task.
Run the outer agentic loop once. Triage the backlog, pick the most valuable ready item, shape its spec, and hand it to the inner loop. Use when the user asks "what's next", "groom the backlog", "run the PM", or on a schedule. Pass --dispatch to label the chosen issue for CI instead of building locally.
One-time template adaptation. Pick a language/framework, scaffold a minimal project, and fill in the command contract in CLAUDE.md that all agents verify against. Use right after creating a repo from this template, or to swap the stack later.
★not rated 6 1mo agoA52 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: