workflow

Plugin workflow from marketplace my-dotclaude in CrazyWillBear/my-dotclaude. Commands read from the repo's manifest — 11 days ago.

Skills (5)

• adhoc

  Build one explicit unit of work with you present, as a subagent chain on the main thread — classify, worktree, plan (complex only), implement, my-review, fresh-implementer fix rounds, fold, and an offered merge. No sessions, no run log, no PR. Use for "/adhoc", or when /orchestrate routes a single e

• classify-task

  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, backend} roster via infra's resolve-tier.sh. Grounds the call by fanning out 1–3 Explore subagents over the touched codebase areas, th

• orchestrate

  Dispatcher for agent work, routed by shape: one unit of work runs as a subagent chain; an issue graph or PRD (--issues or --prd N) runs one boxed worker per issue in its own worktree, tier-routed from each issue's tier label, gated by ready.sh, fold-merged, and reviewed; ambiguous work is discussed,

• to-issues

  Slice a feature into tracer-bullet vertical-slice GitHub issues via gh — each cuts every layer and is demoable alone, published in dependency order so Blocked by refs resolve, labeled for the agent loop and tagged tier:trivial|standard|complex. Works from a PRD issue, a .md spec, or the discussion.

• to-prd

  Capture a thoroughly discussed idea — a feature, a large change, or a design decision — whole as a Product Requirements Doc (problem, goals, success, solution, every decision with its rationale) and publish it as a labeled GitHub issue via gh, for /to-issues to slice. Use for "/to-prd", "write a PRD

Subagents (3)

• implementer

  Implements one GitHub issue or work order end-to-end in its given git worktree — reads the issue and its comments, plans, builds TDD-first with a commit after every green sub-step, runs the done-check. Used by /adhoc (and /orchestrate's ad-hoc lane) as a subagent. Never merges, opens a PR, closes an

• merger

  Resolves the conflicted remainder of /orchestrate's merge stage — the branches merge-fold.sh could not land with plain git — into the base branch in ascending issue number, gated by the project done-check, and returns a structured merge result. Never closes issues, comments, pushes, or reviews — the

• planner

  Plans ONE task before any code exists — reads the repo and writes an ordered plan: file paths, function signatures, tests to write first, testable acceptance criteria, the done-check, and its assumptions. Spawned directly for complex ad-hoc work; /orchestrate's session lane gets the same plan from c

Similar plugins