executing-plans

Executes written implementation plans in batches with review checkpoints between batches.

Updated Jan 12, 2025
One-click install
npx skills add https://github.com/rinbarpen/NeuroTrain --skill executing-plans-rinbarpen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/rinbarpen/NeuroTrain/tree/main/.cursor/commands/executing-plans
Command: npx skills add https://github.com/rinbarpen/NeuroTrain --skill executing-plans-rinbarpen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a written implementation plan in a fresh session often leads to skipped steps, unverified changes, and no opportunity for human review until everything is done. This Skill enforces a disciplined batch-execution workflow with checkpoints so plans are followed exactly and reviewed incrementally. ## Core Features & Use Cases - Critical Plan Review: Loads the plan file and raises questions or concerns with the human partner before writing any code. - Batch Execution with Checkpoints: Executes tasks in batches (default three tasks), runs specified verifications, then pauses and reports for feedback. - Blocker Handling: Stops immediately and asks for clarification when hitting missing dependencies, failing tests, or unclear instructions instead of guessing. - Use Case: You have a detailed implementation plan from a prior planning session. Use this Skill to execute it task-by-task, verifying each batch and getting architect sign-off before continuing, then finishing with the development-branch completion workflow. ## Quick Start Use the executing-plans skill to implement the plan in docs/plans/feature-x.md, executing three tasks at a time and reporting back for review between batches.

Frequently Asked Questions about executing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute an implementation plan with an AI coding assistant?▼

Load the plan file, review it critically for gaps or concerns, then execute tasks in small batches while running each task's verification steps. Pause after each batch to report results and wait for feedback before continuing.

How many tasks should be executed before a review checkpoint?▼

The default batch size is the first three tasks. After completing a batch with all verifications passing, report what was implemented and wait for feedback before starting the next batch.

What should I do when a plan step fails or is unclear?▼

Stop executing immediately and ask for clarification rather than guessing. Blockers include missing dependencies, failing tests, unclear instructions, or repeated verification failures.

When should the plan be reviewed again during execution?▼

Return to the review step when the human partner updates the plan based on feedback or when the fundamental approach needs rethinking. Do not force through blockers.

What happens after all plan tasks are completed?▼

After all tasks are complete and verified, the workflow hands off to the finishing-a-development-branch skill, which verifies tests, presents completion options, and executes the chosen action.