チームを編成し、それを監査するシニアアーキテクトにクロードコードを実行します。

Wizard v1 は、高速コーダから Claude コードを慎重に 1 つに変えました: 書き込み前に読みます, 実行する前にテスト, コミットする前に、独自のコードを攻撃. v2 は、PR 全体のコホートを操る専門家のエージェントの orchestrator を並行してマージするのに注目しました。 v3は、生産コードベースでそのチームを実行する3ヶ月以上が私たちを教えたものです: 単なるguidanceのルールは、勢いが拾う瞬間の瞬間に反します。 そのため、問題のv3では、アーティファクトを生成しなければならないオーダーされたステップになったすべての規則で、ファイルされた計画、実際に実行されたミューテーション、PRボディのブロック、レジャーエントリー、およびオーケストレーションループが独自のオーディオターになりました:耐久性のあるレジャーを記述する安価なチェックインエージェント、ジョブのみが最初の監査、および推測の代わりに測定するキャパシティゲート。

v1 が “コードの前に考える” と v2 が “設計されていた場合、delegate は、並列で — を検証します。” v3 は “アーティファクトのないルールは歯を持っていません。**”

あなたの役割: 導体、タスク ギバーではなく

タスクのブレイクダウンやコードを書くには、ここに** ではありません.

Wizard v3: discipline with teeth

Turn Claude Code into a senior architect that orchestrates a team — and audits itself.

Wizard v1 turned Claude Code from a fast coder into a careful one: read before writing, test before implementing, attack your own code before committing. v2 made the careful thread the orchestrator of a team of specialist agents driving a whole cohort of PRs to merge-ready in parallel. v3 is what three more months of running that team on a production codebase taught us: a rule that is merely guidance gets violated the moment momentum picks up. So in v3 every rule that mattered became an ordered step that must produce an artifact — a filed plan, a mutation that was actually run, a block in the PR body, a ledger entry — and the orchestration loop got auditors of its own: a cheap check-in agent that writes a durable ledger, a second lead whose only job is to audit the first, and a capacity gate that measures instead of guesses.

If v1 was “think before you code” and v2 was “design, then delegate, then verify — in parallel,” v3 is “a rule with no artifact has no teeth.”

Your role: conductor, not task-giver

You are not here to write task breakdowns or code. The agents do that. Your job is to keep the flow moving from idea → issue → PR → production — and nothing below that altitude.

• Set direction. You bring the idea — not the task list. Turning it into a structured issue with acceptance criteria is the issue-maintainer agent’s first step.
• Make the product and judgment calls. When an agent hits an ambiguous requirement or a “which behavior is correct?” fork, that’s yours. The ensemble builds the thing right and defers deciding what’s right to you.
• Unblock. When the orchestrator notifies you it’s gated on a decision, a credential, or a merge, you clear it — then it resumes the whole cohort. v3 never silent-waits on you; a block fires a notification.
• Merge. The orchestrator drives every PR to merge-ready and declares it exactly once, at a named SHA; you press the button. The merge is the one piece of the cycle that stays human.

What it is

/wizard is a Claude Code skill — a markdown playbook that changes how Claude operates for the duration of a task — plus a roster of specialist subagents it dispatches. It runs in two modes:

• Direct mode — a single thread runs the whole 8-phase lifecycle itself (v1’s behavior, intact).
• Delegated mode — the thread you talk to becomes an orchestrator: it decomposes and files the plan, dispatches specialists to build and verify each phase in its own worktree, and owns the pull-request review cycle. Workers commit locally and hand back; the orchestrator pushes, opens the PR, and drives every reviewer finding to resolution.