---

name: "ring:executing-plans" description: | Controlled plan execution with human review checkpoints - loads plan, executes in batches, pauses for feedback. Supports one-go (autonomous) or batch modes. license: MIT compatibility: opencode metadata: trigger: "Have a plan file ready to execute, want human review between batches" skip_when: "Same session with independent tasks, no plan exists, plan needs revision" sequence_after: "ring:writing-plans, ring:pre-dev-task-breakdown"

Executing Plans

---

Overview

Load plan, review critically, choose execution mode, execute tasks with code review.

Core principle: User chooses between autonomous execution or batch execution with human review checkpoints.

Two execution modes:

• One-go (autonomous): Execute all batches continuously with code review, report only at completion
• Batch (with review): Execute one batch, code review, pause for human feedback, repeat

Announce at start: "I'm using the ring:executing-plans skill to implement this plan."

The Process

Step 1: Load and Review Plan

1. Read plan file
2. Review critically - identify any questions or concerns about the plan
3. If concerns: Raise them with your human partner before starting
4. If no concerns: Create todowrite tool and proceed to Step 2

Step 2: Choose Execution Mode (MANDATORY)

THIS STEP IS NON-NEGOTIABLE. You MUST use question tool before executing ANY tasks.

Ask: "How would you like to execute this plan?" Options: (1) One-go (autonomous) - all batches with code review, no human review until completion (2) Batch (with review) - pause for human review after each batch

Based on response: One-go -> Steps 3-4 loop until done | Batch -> Steps 3-5 loop

Why question tool is Mandatory (Not "Contextual Guidance")

This is a structural checkpoint, not optional UX polish.

User saying "don't wait", "don't ask questions", or "just execute" does NOT skip this step because:

1. Execution mode affects architecture - One-go vs batch determines review checkpoints, error recovery paths, and rollback points
2. Implicit intent != explicit choice - "Don't wait" might mean "use one-go" OR "ask quickly and proceed"
3. question tool takes 3 seconds - It's not an interruption, it's a confirmation
4. Emergency pressure is exactly when mistakes happen - Structural gates exist FOR high-pressure moments

Common Rationalizations That Mean You're About to Violate This Rule:

If you catch yourself thinking any of these -> STOP -> Use question tool anyway.

Step 3: Execute Batch

Default: First 3 tasks

Agent Selection: Backend Go -> ring:backend-engineer-golang | Backend TS -> ring:backend-engineer-typescript | Frontend -> ring:frontend-engineer | Infra -> ring:devops-engineer | Testing -> ring:qa-analyst | Reliability -> ring:sre

For each task: Mark in_progress -> Dispatch to agent -> Follow plan steps exactly -> Run verifications -> Mark completed

Step 4: Run Code Review

After each batch, REQUIRED: Use ring:requesting-code-review (all 5 reviewers in parallel)

Handle by severity:

• Critical/High/Medium: Fix immediately (no TODO) -> re-run all 5 reviewers -> repeat until resolved
• Low: Add TODO(review): [Issue] ([reviewer], [date], Low)
• Cosmetic: Add FIXME(nitpick): [Issue] ([reviewer], [date], Cosmetic)

Proceed when: Zero Critical/High/Medium remain + all Low/Cosmetic have comments

Step 5: Report and Continue

One-go mode: Log internally -> proceed to next batch -> report only at completion Batch mode: Show implementation + verification + review results -> "Ready for feedback." -> wait -> apply changes -> proceed

Step 6: Complete Development

Verify all tests pass and present completion options to the user.

When to Stop

STOP immediately: Blocker mid-batch | Critical gaps | Unclear instruction | Verification fails repeatedly. Ask rather than guess.

Remember

• MANDATORY: question tool for execution mode - NO exceptions
• Use * agents over general-purpose when available
• Run code review after each batch (all 5 parallel)
• Fix Critical/High/Medium immediately (no TODO)
• Low -> TODO, Cosmetic -> FIXME
• Stop when blocked, don't guess
• If rationalizing why to skip question tool -> You're wrong -> Ask anyway