Execute plan in batches with review checkpoints
Executes implementation plans in batches with mandatory code review and human checkpoints.
/plugin marketplace add lerianstudio/ring/plugin install ring-default@ring[plan-file-path]Execute an existing implementation plan with controlled checkpoints and code review between batches. Supports autonomous one-go execution or batch mode with human review at each checkpoint.
/execute-plan [plan-file-path]
| Argument | Required | Description |
|---|---|---|
plan-file-path | Yes | Path to the plan file (e.g., docs/plans/2024-01-15-auth-feature.md) |
/execute-plan docs/plans/2024-01-15-oauth-integration.md
Loads and executes the OAuth integration plan with review checkpoints.
/execute-plan /Users/dev/project/docs/plans/2024-01-15-api-refactor.md
Executes a plan using its full path.
/execute-plan docs/plans/2024-01-20-notification-system.md
Executes the most recent plan for the notification system feature.
You will be asked to choose between:
| Mode | Behavior |
|---|---|
| One-go (autonomous) | Executes all batches continuously with code review between each; no human review until completion |
| Batch (with review) | Executes one batch, pauses for human feedback after code review, then continues |
backend-engineer-golangbackend-engineer-typescriptfrontend-bff-engineer-typescriptdevops-engineerqa-analystsreAfter each batch, all 3 reviewers run in parallel:
code-reviewer - Architecture and patternsbusiness-logic-reviewer - Requirements and edge casessecurity-reviewer - OWASP and auth validationIssue handling by severity:
| Severity | Action |
|---|---|
| Critical/High/Medium | Fix immediately, re-run all reviewers |
| Low | Add TODO(review): comment in code |
| Cosmetic/Nitpick | Add FIXME(nitpick): comment in code |
One-go mode: Continues to next batch automatically, reports only at final completion.
Batch mode: Shows implementation summary, verification output, and code review results. Waits for your feedback before proceeding.
After all tasks complete:
finishing-a-development-branch skill| Command/Skill | Relationship |
|---|---|
/write-plan | Use first to create the plan file |
/brainstorm | Use before writing-plans if design unclear |
writing-plans | Creates the plan files this command executes |
requesting-code-review | Called automatically after each batch |
finishing-a-development-branch | Called at completion |
Ensure the path is correct. Plans are typically stored in docs/plans/. Use ls docs/plans/ to list available plans.
The plan was reviewed and found to have issues preventing execution. You'll be asked to clarify or revise the plan before proceeding.
Execution stops when a verification step fails multiple times. Review the output to determine if the plan needs revision or if there's an environmental issue.
All Critical, High, and Medium issues must be fixed before proceeding. The reviewers will re-run after fixes until the batch passes.
If you're not prompted for execution mode, this is a violation of the skill protocol. The mode selection is mandatory regardless of any "just execute" or "don't wait" instructions.
/write-plan first/brainstorm to refine the designsubagent-driven-development skill directlyThis command MUST load the skill for complete workflow execution.
Use Skill tool: executing-plans
The skill contains the complete workflow with: