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.
Best use case
workflow-execute-plans is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using workflow-execute-plans should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/workflow-execute-plans/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How workflow-execute-plans Compares
| Feature / Agent | workflow-execute-plans | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# 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 in `run_dir/03-plans/`) - `repo_root` - `run_dir` Output (persisted): - Plan execution status: `logs/state.json` (or `03-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) 1. Read `plan_path` 2. 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 3. 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: 1. Mark as `in_progress` 2. Execute strictly per plan (don't expand scope) 3. Run verification per plan (tests / build / typecheck / lint / manual verification steps) 4. 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-readiness` for 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-evolution` **Evolution checkpoint** (3 questions); if user chooses "want to optimize", run `skill-improver` based on this `run_dir` to produce minimal patch suggestions - If `finishing-a-development-branch` skill 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
Related Skills
workflow-ship-faster
Ship Faster end-to-end workflow for small web apps (default: Next.js 16.1.1): idea/prototype → foundation gate → design-system.md → lightweight guardrails + docs → feature iteration → optional Supabase + Stripe → optional GitHub + Vercel deploy → optional AI-era SEO (sitemap/robots/llms.txt). Resumable, artifact-first under runs/ship-faster/ (or OpenSpec changes/). Trigger: ship/launch/deploy/production-ready MVP.
workflow-project-intake
Use when you need to clarify requirements and route to the right workflow (idea → executable input). Project intake + routing: help the user brainstorm and clarify intent, persist goal/context artifacts, then dispatch to the right workflow or step skill. Default route is workflow-ship-faster (Next.js 16.1.1) for idea/prototype→launch. Triggers: project kickoff, requirements clarification, brainstorm, ideas, discovery, intake.
workflow-feature-shipper
Use when you need to ship a single PR-sized feature end-to-end (plan -> implement -> verify) with artifacts. Ship core product features quickly in a Next.js codebase: turn a feature idea into an executable plan, implement in PR-sized slices, and keep artifacts under runs/ (or OpenSpec changes/ when available). Supports plan-only mode for early scoping. For prototype UI work, include a demo-ready wow moment (animation/micro-interaction) by default unless user opts out.
workflow-creator
Create workflow-* skills by composing existing skills into end-to-end chains. Turns a user idea into a workflow_spec.md SSOT (via workflow-brainstorm), discovers available skills locally + from skills.sh, and generates a new workflow-<slug>/ skill package. Use when you want to design a new workflow, chain multiple skills into a flow, or turn scattered atomic skills into a resumable plan-then-confirm workflow.
workflow-brainstorm
Use when you need to turn a vague idea into a confirmed design spec before implementation (new feature/component/behavior change). First check project context, then ask one question at a time, provide 2-3 options with trade-offs, finally output design in segments (~200-300 words each) with confirmation after each. Triggers: brainstorm, clarify idea, design spec, refine concept, requirement clarification.
workflow-template-seeder
Seed a new runnable template under templates/NNN-slug/ from a short spec by chaining existing skills (intake → ship-faster stages) while keeping it clean and shareable (no secrets, minimal scope). Use when creating a new template quickly.
workflow-template-extractor
Extract a shareable runnable template under templates/NNN-slug/ from a real project: copy + de-brand + remove secrets + add env examples + docs, with minimal refactors. Use when you have a working project and want to turn it into a template.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
turbo-sdk
Complete Arweave Turbo ecosystem including client SDKs, core upload infrastructure, payment service backend, and CLI tools for permanent decentralized storage
terraform-best-practices
Comprehensive best practices for Terraform infrastructure as code from Anton Babenko's community guide
sveltekit-svelte5-tailwind-skill
Comprehensive integration skill for building sites with SvelteKit 2, Svelte 5, and Tailwind CSS v4