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.
- Installs
- 51
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/heyvhuang/ship-faster --skill workflow-execute-plans- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads workflow-execute-plans automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
FAQ
What does the workflow-execute-plans 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.
How do I install workflow-execute-plans?
Run npx skills add https://github.com/heyvhuang/ship-faster --skill workflow-execute-plans in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/workflow-execute-plans/ (personal) or .claude/skills/workflow-execute-plans/ (project).
Which AI agents can use workflow-execute-plans?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is workflow-execute-plans safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains workflow-execute-plans?
It is published by heyvhuang in heyvhuang/ship-faster. It has 51 recorded installs.
More from heyvhuang/ship-faster
mcp-stripe
heyvhuang/ship-faster
Stripe MCP transaction operations skill. Execute transaction operations via Stripe MCP server (https://mcp.stripe.com): customer management, products/prices, invoices, payment links, subscriptions, refunds, dispute handling, balance queries. Triggers: user requests Stripe operations including create customer, create product, create invoice, generate payment link, query transactions, process refunds, manage subscriptions, view disputes, check balance, etc.
mcp-supabase
heyvhuang/ship-faster
Execute database operations via Supabase MCP (query/write/migration/logs/type generation). Triggers: query/statistics/export/insert/update/delete/fix/backfill/migrate/logs/alerts/type generation. Does not trigger for: pure architecture discussion or code planning. Write operations require confirmation; UPDATE/DELETE without WHERE is refused.
review-doc-consistency
heyvhuang/ship-faster
Documentation consistency reviewer that checks alignment between code implementation and documentation. Use when user requests reviewing documentation vs code consistency, checking if README/docs are outdated, verifying API documentation accuracy. Applicable for (1) reviewing README vs implementation consistency (2) checking if docs/ directory content is outdated (3) verifying API/config documentation accuracy (4) generating documentation consistency reports. Trigger words include doc review, documentation consistency, check outdated docs, verify docs.
tool-ast-grep-rules
heyvhuang/ship-faster
Write AST-based code search and rewrite rules using ast-grep YAML. Create linting rules, code modernizations, and API migrations with auto-fix. Use when the user mentions ast-grep, tree-sitter patterns, code search rules, lint rules with YAML, AST matching, or code refactoring patterns.
tool-openclaw
heyvhuang/ship-faster
Help users install, configure, operate, and migrate OpenClaw (gateway, channels, nodes, plugins, model/auth setup). Use when answering OpenClaw setup/debug questions or model migration questions; use the local docs snapshot bundled with this skill as the source of truth. Triggers: openclaw, clawdbot, clawd, clawdhub, gateway, onboard, channels login, whatsapp, telegram, discord, mattermost, pairing, nodes, sandboxing, tailscale, provider migration, Claude to GPT, model swap.
tool-ui-ux-pro-max
heyvhuang/ship-faster
Use when you need concrete UI/UX inputs (palette, typography, landing patterns, UX/a11y constraints) to drive design or review. Searchable UI/UX design intelligence (styles, palettes, typography, landing patterns, charts, UX/a11y guidelines + stack best practices) backed by CSV + a Python search script. Triggers: UIUX/uiux, UI/UX, UX design, UI design, design system, design spec, color palette, typography, layout, animation, accessibility/a11y, component styling. Actions: search, recommend, review, improve UI.
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档（Docx / Wiki）内容操作：读取、创建、编辑文档，插入或下载图片附件，以及操作思维笔记。用户提供文档 URL/token（包括 doubao.com 的 /docx/、/wiki/）时使用；按 URL 路径/token 而非域名路由；/page/ 是妙搭应用，非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive；随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式（BaseApp/AppMode 页面与组件）、Workspace 目录、workflow、角色权限、模板中心（多维表格模板分类/列表/搜索）；遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps；文件导入/导出转 lark-drive，认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用；doubao.com 云空间 URL/token 也按资源路径和 token 路由，不回退 WebFetch。不负责：文档内容编辑（走 lark-doc）、表格/Base 表内数据操作（走 lark-sheets/lark-base）、知识空间节点/成员管理（走 lark-wiki）、原生 Markdown 文件读写/patch/diff（走 lark-markdown）。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。