my-dotclaude

Run one task through the plan→build→review pipeline — a Step-0.5 classify-task call routes the planner/implementer/reviewer models to the task's complexity tier, then the plan is written (planner subagent or inline), the implementer builds it in an isolated worktree, the my-review agent reviews the diff, and findings route by severity (low→issues, medium→triaged fix-list, high→collective replan, critical→own cycle). For single tasks not worth slicing into an issue graph. Use for "/pipeline <issue#|task>", "pipeline this".

Deep, security-weighted review of your changes or a PR — routes the reviewer model to the change's complexity (opus by default; fable for a complex diff, on ask), then spawns the my-review agent (xhigh reasoning) on that model. Read-only, report-only. Use for "/my-review", "/my-review <PR#>".

Classify one task or issue into a complexity tier — trivial, standard, or complex — and emit that tier plus a rationale; consumers resolve the tier's {model, effort} roster via the plugin's resolve-tier.sh. Grounds the call by fanning out 1–3 Explore subagents over the touched codebase areas, then asks you to confirm or override. Use for "/classify-task <issue#|brief>", "classify this task".

Run N rounds of the autonomous issue-solving loop — pick the ready set (blockers closed, skip hitl), fan out parallel implementers in isolated git worktrees, hand the completed branches to a merger that merges in dependency order and resolves conflicts under the done-check, close finished issues, then a reviewer files blocking follow-ups. Use for "/orchestrate", "run the loop", "build the ready issues".

Check whether the plan(s)/PRD(s)/issue-slice(s) under discussion still match the decisions made in this session — a sonnet subagent reads the current session log, later decisions win, and reports drift read-only. Use for "/verify-plan", "does my plan still match what we decided?".

Capture the just-approved plan after exiting plan mode and hand it to a fresh session — write the plan to a file plus the resume pointer the workflow plugin reads, then tell me to /clear and send `go` to execute it. Use for "/handoff-plan", "hand off this plan".

Capture a rich handoff before /clear — write a markdown handoff doc (work done, in-flight state, next steps, key files, gotchas) plus the resume pointer the workflow plugin reads, then tell me to /clear and send `go`. Use for "/handoff", "hand this off", "save state and clear".

Slice a feature into tracer-bullet vertical-slice GitHub issues via gh — each slice cuts every layer and is demoable alone, published in dependency order so Blocked by refs resolve, labeled for the agent loop. Works from a PRD issue, a .md spec, or the current discussion. Use for "/to-issues", "break the PRD into issues", "slice this".

Turn an aligned task into a Product Requirements Doc and publish it as a labeled GitHub issue via gh — explore the repo, map the testing seam with me, fill the PRD template verbatim, then file it as a `prd`-labeled tracking issue (sliced later by /to-issues). Use for "/to-prd", "write a PRD", "turn this into a PRD issue".

Apply the latest kit release on this machine — updates the my-dotclaude marketplace entry and both plugins, then reminds you to restart Claude Code. Use for "/update-kit", "update the kit", "apply latest kit release".

Report whether a newer kit release exists on GitHub — compares the installed plugin version against the latest GitHub Release and prints either "up to date" or "vX.Y.Z available — run /update-kit". Use for "/check-updates", "check for updates", "is the kit up to date?".

Interrogate me about the task before any code — surface scope, constraints, edge cases, acceptance criteria, and unknowns through rounds of pointed questions until no material ambiguity remains. Use for "/grill-me", "grill me", "interrogate the requirements".

Search the repo for reusable or extendable code before writing new code — extracts search terms from the task, runs the dedup-search helper, and triages each candidate into reuse | extend | none. Emits a reuse-candidate list or an explicit "searched, nothing reusable" statement. Use before any implementation: "/dedup-search", "search for duplicates", "find reusable code".

Root-cause a bug through a disciplined 6-phase loop — build a feedback loop, reproduce, rank falsifiable hypotheses, instrument, fix with a regression test, then clean up and post-mortem. Use for "/diagnose", "debug this", "find the root cause".

Scaffold the working docs for a Python project — drops a filled CLAUDE.md, STYLEGUIDE.md, and a Python .gitignore into the target dir, wired for a uv + ruff + mypy + pytest toolchain. Minimal by design (no pyproject/venv). Use for "start a new python project", "initialize/scaffold a python repo", "set up python project docs".

Explain the whole codebase in plain English — architecture overview, major components, how they fit together, and where a newcomer should start. Maps the repo with the Explore agent first, then synthesizes on the session model.