클래드 코드는 팀의 관현을 관현하고 감사한다.

Wizard v1는 빠른 코퍼에서 시선 코드가 조심해야 합니다. 쓰기 전에 테스트, 구현하기 전에 테스트, 커밋하기 전에 자신의 코드를 공격합니다. v2는 PR의 전체적인 코호트를 구동하는 전문 에이전트 팀의 orchestrator를 사용하여 병렬에 병합하는 데 도움을줍니다. ** v3는 생산 코드베이스에 팀이 우리를 가르쳤다는 것을 실행하는 3 개월 이상입니다. ** 단순히 *guidance *는 순간의 소모를 얻게됩니다. 그래서 v3에 문제가있는 모든 규칙은 ** artifact**를 생산해야하는 주문 단계가되었다 - 파일 계획, 실제로 실행 된 돌연변이, PR 몸의 블록, 원장 입구 - 및 관현 루프는 ** : 내구성 ledger를 작성하는 저렴한 체크 인 에이전트, 작업이 먼저 감사하는 두 번째 리드, 추측 대신 측정 용량 게이트.

v1이 "코드 전에 스핑"과 v2는 “설계, 그 후 delegate, 그 후 - 병렬에서,” v3는 “a 규칙은 아무 식도 없다.”

너의 역할: 지휘자, 일 면제

당신은 ** 여기에 작업 내역이나 코드를 작성합니다.

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.