A dev team, in Claude Code.

Shadow Clone supplies that structure. It is not one assistant trying harder. It is planning, building and review kept as separate jobs, the way a team would run them.

Every mode runs the same shape. You type one command; this is what happens behind it.

1. 01

   It researches before it writes

   The first pass does not touch your code. It reads what is already there (how the project is laid out, what it depends on, and what the existing work looks like) so that what follows fits the codebase instead of fighting it.

   Wave 1 of 3 · output written to .waves/wave-1/deliverables/

2. 02

   It plans before it builds

   The work is broken into pieces the size of a single pull request, with the order worked out: what has to come first, what can run alongside it, and which pieces everything else is waiting on.

   Wave 2 of 3 · dependency-ordered, never a week-by-week schedule

3. 03

   It builds in focused passes

   Specialists take one piece each rather than one model attempting everything at once. The number working at the same time is capped, because past a certain point parallel agents start colliding with each other.

   Wave 3 of 3 · hard cap of 5 concurrent specialists

4. 04

   A second model reviews it before you hear it is done

   Finished work is handed to a different AI model, which reads the changes, the full text of every file touched, and your project standards. It returns one of four verdicts. Anything short of approval goes back to be fixed and re-reviewed.

   Up to 3 rounds · APPROVE / REVISE / BLOCK / ERROR

5. 05

   Nothing ships silently

   If three rounds pass without approval, the outstanding problems are written to your project issue tracker and reported to you. The work is never quietly declared finished because the review ran out of attempts.

   Open findings logged to docs/audit/ISSUE_TRACKER.md

Commands

19

Engineering protocols

15

Waves per mode

3

License

MIT

Each of these is a real journey through the toolkit. The commands shown are the ones you would chain together, in order.

• “I know what I want to build, but not how to build it”

  Start at the top and let the planning modes do the architecture. You describe the end state; it works out the phases, the order, and what depends on what, then builds it in reviewed passes.

  1. /sc
  2. →/sc-plan
  3. →/sc-feature

• “Something is broken and I cannot work out why”

  The debugging mode forms a theory, tests it, and only then proposes a fix, rather than changing things until the symptom disappears. A finding without a reproduction is treated as a question, not a bug.

  1. /sc-debug

• “This code works, but I am afraid to touch it”

  The refactor mode restructures with behaviour preservation as its prime directive, and the review pass checks the behaviour did not drift. Tests can be generated first if the surface is not covered.

  1. /sc-test-audit
  2. →/sc-tests
  3. →/sc-refactor

• “I need to know whether this is safe to ship”

  The audit mode produces a blueprint of what to examine, then runs the security checklist against it. Every finding has to be backed by a reproduction or a failing test before it counts.

  1. /sc-audit
  2. →/sc-echo

• “It is slow and I do not know where the time goes”

  The optimisation mode measures before it changes anything, so improvements are demonstrated against a baseline rather than assumed from a rewrite.

  1. /sc-optimize

• “I am one person and there is nobody to check my work”

  Paired review is the whole point. Turn it on and every finished unit of work is judged by a second model against your project standards before you are told it is done.

  1. /sc-echo

• “I have inherited a codebase I do not understand”

  The research mode investigates and reports with cited evidence, and the docs mode writes the documentation the project should have had, aimed at whoever reads it next, not at a marketing page.

  1. /sc-research
  2. →/sc-docs

• “I need to sequence months of work, not one task”

  Roadmap mode lays out multiple milestones as a pipeline with prerequisites, parallel branches, and the nodes everything else is waiting on. Shaped by dependencies, never by dates.

  1. /sc-roadmap
  2. →/sc-sprint

A slash command is a short text shortcut you type into Claude Code (like /sc-plan) that puts the assistant into one focused mode. Shadow Clone ships one umbrella command and eighteen mode commands, grouped by what they are for.