Multi AI

Multi-AI Pipeline Command

You are starting the multi-AI pipeline. Follow this process exactly.

Note: Scripts are located at ${CLAUDE_PLUGIN_ROOT}/scripts/. The .task/ directory is created in your project at ${CLAUDE_PROJECT_DIR}/.task/.

Step 1: Prepare task state

Inspect the existing .task/ state. Resume an active run; do not reset it merely because the skill was invoked again. For an explicitly requested new run, archive the previous .task/ directory to a unique sibling path and verify the archive before resetting the working state:

"${CLAUDE_PLUGIN_ROOT}/scripts/orchestrator.sh" reset

The reset may remove old working files, so run it only after that preservation step. Keep the archived reports available for review.

Step 2: Create User Request

Write the user's request to .task/user-request.txt:

mkdir -p "${CLAUDE_PROJECT_DIR:-.}/.task"

Then write the request content to .task/user-request.txt.

Step 3: Set Initial State

"${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.sh" set plan_drafting ""

Step 4: Create Initial Plan

Create .task/plan.json with:

• id: "plan-YYYYMMDD-HHMMSS"
• title: Short descriptive title
• description: What the user wants
• requirements: List of requirements
• created_at: ISO8601 timestamp
• created_by: "claude"

Step 5: Transition to Refining

"${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.sh" set plan_refining "$(bun ${CLAUDE_PLUGIN_ROOT}/scripts/json-tool.ts get .task/plan.json .id)"

Step 6: Refine Plan

Create .task/plan-refined.json with technical details:

• Research the codebase
• Add technical_approach
• Add files_to_modify and files_to_create
• Add potential_challenges

Step 7: Sequential Plan Reviews

Run reviews in order. Fix issues after each before continuing:

1. Invoke /review-sonnet → If issues, fix them
2. Invoke /review-codex → If issues, fix and restart from step 1

When all approve, continue.

Step 8: Implement

Invoke /implement-sonnet to implement the approved plan.

This skill will:

• Write the code following the approved plan
• Add tests
• Output to .task/impl-result.json

Step 9: Sequential Code Reviews

Run reviews in order. Fix issues after each before continuing:

1. Invoke /review-sonnet → If issues, fix them
2. Invoke /review-codex → If issues, fix and restart from step 1

When all approve, continue.

Step 10: Complete

"${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.sh" set complete "$(bun ${CLAUDE_PLUGIN_ROOT}/scripts/json-tool.ts get .task/plan-refined.json .id)"

Report success to the user.

Important Rules

• Follow this process exactly - no shortcuts
• Resolve review findings before continuing. If reviewers disagree or a cycle repeats without new evidence or a relevant change, report the unresolved blocker; do not loop indefinitely or mark the task complete.
• If codex rejects, restart the review cycle from sonnet
• Keep the user informed of progress at each major step