executing-plans

Executes written implementation plans in batches with beads task tracking and review checkpoints.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/johnstegeman/pi-packages --skill executing-plans-johnstegeman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/johnstegeman/pi-packages/tree/main/packages/pi-superpowers-plus/skills/executing-plans
Command: npx skills add https://github.com/johnstegeman/pi-packages --skill executing-plans-johnstegeman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns an approved implementation plan into disciplined execution by loading task beads, working them in small batches, and pausing for human review between batches instead of running an entire plan unchecked. ## Core Features & Use Cases - Batch execution with checkpoints: Executes the first 3 tasks by default, then reports results and waits for feedback before continuing. - Beads-driven task tracking: Claims, closes, and blocks task beads via beads_update, beads_close, and beads_mol_ready so dependencies unblock automatically. - Critical plan review and stop conditions: Reviews the plan before starting, verifies the plan-approved gate, and stops to ask when blocked or when the plan is wrong. - Use Case: After a planning session produces an approved multi-task implementation plan, use this Skill in a fresh session to claim each task bead, implement with TDD, run verifications, and hand off to the finishing-a-development-branch workflow. ## Quick Start Ask the AI to execute the approved implementation plan for the current branch using the executing-plans skill, working tasks in batches and reporting after each batch.

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's implement step via beads_mol_current, review each task bead critically, then claim and complete tasks in batches of three. Report results after each batch and wait for feedback before continuing.

How to track multi-step coding tasks with beads?

Use beads_mol_ready to see unblocked tasks, beads_update with claim to start a task, and beads_close with a reason when done. Closing a task automatically unblocks whatever depended on it.

What should I do when a task gets blocked mid-execution?

Stop executing immediately and mark the task bead blocked with beads_update, adding a beads_comment explaining the blocker. Ask your human partner for clarification rather than guessing, and re-claim the task on resume.

Can I run plan execution on the main branch?

No, the skill requires an active non-main branch or explicit user consent to work on main. It recommends setting up an isolated git worktree before starting, with small changes on a branch acceptable with human approval.

When should I stop executing a plan instead of continuing?

Stop when you hit a blocker, when verification fails repeatedly, or when you learn something that makes the remaining plan unworkable. Report what you learned and propose a revised approach rather than forcing through.