executing-plans
starsforks
How to install executing-plans?
mvschwarz/openrig/executing-plans
$npx -y skills add mvschwarz/openrig --skill executing-plansUse when you have a written implementation plan to execute in a separate session with review checkpoints
SKILL.md
| 1 | # Executing Plans |
| 2 | |
| 3 | ## Overview |
| 4 | |
| 5 | Load plan, review critically, execute tasks in batches, report for review between batches. |
| 6 | |
| 7 | **Core principle:** Batch execution with checkpoints for architect review. |
| 8 | |
| 9 | **Announce at start:** "I'm using the executing-plans skill to implement this plan." |
| 10 | |
| 11 | ## The Process |
| 12 | |
| 13 | ### Step 1: Load and Review Plan |
| 14 | 1. Read plan file |
| 15 | 2. Review critically - identify any questions or concerns about the plan |
| 16 | 3. If concerns: Raise them with your human partner before starting |
| 17 | 4. If no concerns: Create TodoWrite and proceed |
| 18 | |
| 19 | ### Step 2: Execute Batch |
| 20 | **Default: First 3 tasks** |
| 21 | |
| 22 | For each task: |
| 23 | 1. Mark as in_progress |
| 24 | 2. Follow each step exactly (plan has bite-sized steps) |
| 25 | 3. Run verifications as specified |
| 26 | 4. Mark as completed |
| 27 | |
| 28 | ### Step 3: Report |
| 29 | When batch complete: |
| 30 | - Show what was implemented |
| 31 | - Show verification output |
| 32 | - Say: "Ready for feedback." |
| 33 | |
| 34 | ### Step 4: Continue |
| 35 | Based on feedback: |
| 36 | - Apply changes if needed |
| 37 | - Execute next batch |
| 38 | - Repeat until complete |
| 39 | |
| 40 | ### Step 5: Complete Development |
| 41 | |
| 42 | After all tasks complete and verified: |
| 43 | - Announce: "I'm using the finishing-a-development-branch skill to complete this work." |
| 44 | - **REQUIRED SUB-SKILL:** Use superpowers:finishing-a-development-branch |
| 45 | - Follow that skill to verify tests, present options, execute choice |
| 46 | |
| 47 | ## When to Stop and Ask for Help |
| 48 | |
| 49 | **STOP executing immediately when:** |
| 50 | - Hit a blocker mid-batch (missing dependency, test fails, instruction unclear) |
| 51 | - Plan has critical gaps preventing starting |
| 52 | - You don't understand an instruction |
| 53 | - Verification fails repeatedly |
| 54 | |
| 55 | **Ask for clarification rather than guessing.** |
| 56 | |
| 57 | ## When to Revisit Earlier Steps |
| 58 | |
| 59 | **Return to Review (Step 1) when:** |
| 60 | - Partner updates the plan based on your feedback |
| 61 | - Fundamental approach needs rethinking |
| 62 | |
| 63 | **Don't force through blockers** - stop and ask. |
| 64 | |
| 65 | ## Remember |
| 66 | - Review plan critically first |
| 67 | - Follow plan steps exactly |
| 68 | - Don't skip verifications |
| 69 | - Reference skills when plan says to |
| 70 | - Between batches: just report and wait |
| 71 | - Stop when blocked, don't guess |
| 72 | - Never start implementation on main/master branch without explicit user consent |
| 73 | |
| 74 | ## Integration |
| 75 | |
| 76 | **Required workflow skills:** |
| 77 | - **superpowers:using-git-worktrees** - REQUIRED: Set up isolated workspace before starting |
| 78 | - **superpowers:writing-plans** - Creates the plan this skill executes |
| 79 | - **superpowers:finishing-a-development-branch** - Complete development after all tasks |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
