workflow-execute-plans
Execute written implementation plans: first read and critically review the plan, then implement in small batches (default 3 tasks), produce verification evidence per batch and pause for feedback; must stop immediately and ask for help when blocked/tests fail/plan unclear. Trigger words: execute plan, implement plan, batch execution, follow the plan.
How do I install this agent skill?
npx skills add https://github.com/heyvhuang/ship-faster --skill workflow-execute-plansIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill facilitates the batch execution of implementation plans. Its primary risk is indirect prompt injection, as it executes commands and verification scripts defined in external, potentially untrusted plan files. It includes manual review steps and human-in-the-loop checkpoints as mitigations.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerwarn
1/1 file flagged
What does this agent skill do?
Executing Plans (Batch Execution + Checkpoints)
Goal
Reliably turn a "written plan file" into implementation results, avoiding drift or accumulated risk from doing everything at once.
Core strategy: Batch execution + pause for feedback after each batch.
Input/Output (Recommended for Chaining)
Input (pass paths only):
plan_path: Plan file (usually inrun_dir/03-plans/)repo_rootrun_dir
Output (persisted):
- Plan execution status:
logs/state.json(or03-plans/<plan>-status.md) - Per-batch verification evidence: append to the corresponding plan file or
05-final/summary
Execution Flow
Step 1) Read and Review Plan (Critical Review First)
- Read
plan_path - Review if the plan has these issues:
- Missing dependencies (packages to install/env vars/external services)
- Task granularity too large (can't verify, hard to rollback)
- Missing acceptance criteria or verification commands
- Obviously wrong task ordering
- If critical issues found: Stop first, present concerns as 1-3 bullet points, let human confirm before starting execution.
Rule: Don't "guess while doing". Clarify when plan is unclear.
Step 2) Batch Execution (Default 3 Tasks per Batch)
Execute the first 3 tasks from the plan, then stop and report.
For each task:
- Mark as
in_progress - Execute strictly per plan (don't expand scope)
- Run verification per plan (tests / build / typecheck / lint / manual verification steps)
- Mark as
completed
Status recording (choose one, prefer structured):
- Update task status in
logs/state.json - Or maintain checklist in
plan_path([ ]→[x]), recording verification results alongside
Step 3) Batch Report (Must Pause for Feedback)
After each batch, report three things:
- What changed: Which files changed/what was implemented (brief)
- Verification: What verification was run, what were the results (key info only, no long logs)
- Next batch: Which 3 tasks are next
Optional but recommended:
- Use
review-merge-readinessfor a conclusive review on this batch (especially for cross-module changes, risky changes, or approaching merge)
Last line must be:
Ready for feedback.
Then wait for human feedback—don't automatically continue to next batch.
Step 4) Continue Based on Feedback
- If feedback requests changes: fix first, re-verify, then continue next batch
- If feedback is OK: continue to next batch (still default 3 tasks)
Step 5) Wrap Up (After All Complete)
When all tasks are complete and verified:
- Run full tests/build (per project conventions)
- Write
05-final/summary.md(what was done/how verified/risks & rollback/next steps) - Do a
skill-evolutionEvolution checkpoint (3 questions); if user chooses "want to optimize", runskill-improverbased on thisrun_dirto produce minimal patch suggestions - If
finishing-a-development-branchskill exists: follow that skill to complete merge/PR/cleanup options
When to Stop and Ask for Help (Hard Rules)
Encounter any of these, stop execution immediately and report the issue:
- Blocked mid-way (missing dependency, wrong environment, permission issues)
- Tests/verification failed and can't quickly identify the cause
- Plan step unclear (can't determine correct implementation approach)
- Action that could cause data loss or wide-ranging side effects appears but plan doesn't include confirmation point
Remember
- Review plan critically before starting
- Small batch execution (default 3 tasks)
- Every batch requires verification and reporting, then wait for feedback
- When blocked, stop—don't guess
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/heyvhuang/ship-faster/workflow-execute-plans">View workflow-execute-plans on skillZs</a>