Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation through collaborative dialogue.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Requires root cause investigation before any fix attempts. Random fixes waste time and create new bugs.
Transform ambiguous specs into implementable work items through adversarial refinement. This skill should be used PROACTIVELY when receiving specs, claiming epics, or starting work on complex (l/xl) tasks. Use /breakdown for spec->tasks decomposition, /refine for sharpening individual items.
Expert Haskell developer specializing in type-driven development, pure functional programming, and idiomatic patterns. Use PROACTIVELY when working on any Haskell code.
Activate at session start when you are the primary Claude instance. Establishes orchestrator role with delegation protocols, subagent launch templates, token efficiency rules, and parallel safety constraints. You orchestrate; subagents implement.
Activate when you are a delegated subagent (not the orchestrator). Establishes subagent protocol with terse returns, details to history/, file ownership boundaries, and escalation rules. You implement; orchestrator reviews and commits.
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with beads integration via bd worktree commands.
★not rated 5 7mo agoA33 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: