MAIN CHAT MUST NOT WRITE CODE. This is not negotiable.

Main chat orchestrates. Subagents implement. If you catch yourself about to use Write or Edit on a code file, STOP.

If you're about to edit code directly, STOP and spawn a Task agent instead.

Rationalization Prevention

These thoughts mean STOP—you're rationalizing:

The Meta-Rationalization

If you're treating these rules as "guidelines for complex work" rather than "invariants for ALL work", you've already failed.

Simple work is EXACTLY when discipline matters most—because that's when you're most tempted to skip it.

The Process

For each task N in PLAN.md:
    1. Start ralph loop for task N
       → Skill(skill="workflows:dev-ralph-loop")

    2. Inside loop: spawn Task agent
       → Skill(skill="workflows:dev-delegate")

    3. Task agent follows TDD (dev-tdd) using testing tools (dev-test)

    4. Verify tests pass, output promise

    5. Move to task N+1, start NEW ralph loop

Step 1: Start Ralph Loop for Each Task

REQUIRED SUB-SKILL:

Skill(skill="workflows:dev-ralph-loop")

Key points from dev-ralph-loop:

• ONE loop PER TASK (not one loop for feature)
• Each task gets its own completion promise
• Don't move to task N+1 until task N's loop completes

Step 2: Inside Loop - Spawn Task Agent

REQUIRED SUB-SKILL:

Skill(skill="workflows:dev-delegate")

Key points from dev-delegate:

• Implementer → Spec reviewer → Quality reviewer
• Task agent follows dev-tdd protocol
• Task agent uses dev-test tools

Step 3: Verify and Complete

After Task agent returns, verify:

• Tests EXECUTE code (not grep)
• Tests PASS (SKIP ≠ PASS)
• LEARNINGS.md has actual output
• Build succeeds

If ALL pass → output the promise. If ANY fail → iterate.

Sub-Skills Reference

Failure Recovery Protocol

Pattern from oh-my-opencode: After 3 consecutive implementation failures, escalate.

3-Failure Trigger

If you attempt 3 implementations and ALL fail tests:

Iteration 1: Implement approach A → tests fail
Iteration 2: Implement approach B → tests fail
Iteration 3: Implement approach C → tests fail
→ TRIGGER RECOVERY PROTOCOL

Recovery Steps

1. STOP all further implementation attempts

   • No more "let me try a different approach"
   • No guessing or throwing code at the problem

2. REVERT to last known working state

   • git checkout <last-passing-commit>
   • Or revert specific files
   • Document what was attempted in .claude/RECOVERY.md

3. DOCUMENT what was attempted

   • All 3 approaches tried
   • Test failures for each
   • Why each approach failed
   • What this reveals about the problem

4. CONSULT with user BEFORE continuing

   • "I've tried 3 approaches. All fail tests. Here's what I've learned..."
   • Present test failure patterns
   • Request: requirements clarification, design input, or different strategy

5. ASK USER for direction

   • Option A: Re-examine requirements (may need /dev-clarify)
   • Option B: Try completely different design (may need /dev-design)
   • Option C: Investigate why tests fail (may need /dev-debug)
   • Option D: User provides domain knowledge

NO PASSING TESTS = NOT COMPLETE (hard rule)

Recovery Checklist

Before continuing after multiple failures:

• All 3 approaches documented with test failures
• Pattern in failures identified (same tests? different errors?)
• Current code reverted to clean state
• User consulted with specific question
• Clear direction from user before proceeding

Anti-Patterns After Failures

DON'T:

• Keep trying "just one more thing"
• Make larger and larger changes
• Skip TDD "to get it working first"
• Suppress test failures ("I'll fix them later")
• Blame the tests ("tests are wrong")

DO:

• Stop and analyze the failure pattern
• Revert to clean state
• Document what each approach revealed
• Consult user with specific findings
• Get clear direction before continuing

Example Recovery Flow

Loop 1: Implement with synchronous approach → Tests timeout
Loop 2: Implement with async/await → Tests hang
Loop 3: Implement with promises → Tests fail assertion

→ RECOVERY PROTOCOL:
1. STOP (no loop 4)
2. REVERT: git checkout HEAD -- src/feature.ts tests/
3. DOCUMENT in .claude/RECOVERY.md:
   - Pattern: All async implementations cause timing issues
   - Tests expect synchronous behavior
   - Hypothesis: Requirements may need async, tests don't handle it
4. ASK USER:
   "I've tried 3 async implementations. All cause timing issues.
    Tests expect synchronous behavior.

    This suggests either:
    A) Feature should actually be synchronous (simpler)
    B) Tests need updating for async behavior

    Which direction should I take?"

When to Trigger Recovery

Trigger after 3 failures when:

• Same test keeps failing despite different approaches
• Different tests fail in pattern (suggests wrong approach)
• Tests pass locally but fail in CI
• Implementation works but breaks unrelated tests

Don't wait for max iterations - trigger early when pattern emerges.

If Max Iterations Reached

Ralph exits after max iterations. Still do NOT ask user to manually test.

Main chat should:

1. Summarize what's failing (from LEARNINGS.md)
2. Report which automated tests fail and why
3. Ask user for direction:
   • A) Start new loop with different approach
   • B) Add more logging to debug
   • C) User provides guidance
   • D) User explicitly requests manual testing

Never default to "please test manually". Always exhaust automation first.

No Pause Between Tasks

Skill(skill="workflows:dev-review")