executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Best use case
executing-plans is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Teams using executing-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/executing-plans/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How executing-plans Compares
| Feature / Agent | executing-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?
Use when you have a written implementation plan to execute in a separate session with review checkpoints
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.
SKILL.md Source
# Executing Plans ## Overview Load plan, review critically, execute tasks in batches, report for review between batches. **Core principle:** Batch execution with checkpoints for architect review. **Announce at start:** "I'm using the executing-plans skill to implement this plan." ## The Process ### Step 1: Load and Review Plan 1. Read plan file 2. Review critically - identify any questions or concerns about the plan 3. If concerns: Raise them with your human partner before starting 4. If no concerns: Create TodoWrite and proceed ### Step 2: Execute Batch **Default: First 3 tasks** For each task: 1. Mark as in_progress 2. Follow each step exactly (plan has bite-sized steps) 3. Run verifications as specified 4. Mark as completed ### Step 3: Report When batch complete: - Show what was implemented - Show verification output - Say: "Ready for feedback." ### Step 4: Continue Based on feedback: - Apply changes if needed - Execute next batch - Repeat until complete ### Step 5: Complete Development After all tasks complete and verified: - Announce: "I'm using the finishing-a-development-branch skill to complete this work." - **REQUIRED SUB-SKILL:** Use superpowers:finishing-a-development-branch - Follow that skill to verify tests, present options, execute choice ## When to Stop and Ask for Help **STOP executing immediately when:** - Hit a blocker mid-batch (missing dependency, test fails, instruction unclear) - Plan has critical gaps preventing starting - You don't understand an instruction - Verification fails repeatedly **Ask for clarification rather than guessing.** ## When to Revisit Earlier Steps **Return to Review (Step 1) when:** - Partner updates the plan based on your feedback - Fundamental approach needs rethinking **Don't force through blockers** - stop and ask. ## Remember - Review plan critically first - Follow plan steps exactly - Don't skip verifications - Reference skills when plan says to - Between batches: just report and wait - Stop when blocked, don't guess
Related Skills
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
writing-wechat-tech-posts
Writes complete WeChat tech posts (hook, TOC, body, checklists, image placement, layout notes, summaries). Use when the user asks to draft a WeChat tech article, generate reusable prompts for writing, or turn a topic/outline into a publish-ready post.
titling-wechat-tech-posts
Crafts and rewrites WeChat tech post titles across multiple patterns (list, contrast, outcome, scenario, anti-myth, template). Use when the user needs headline brainstorming or “restrained but clickable” title rewrites for tech/engineering WeChat公众号.
planning-wechat-tech-account
Defines WeChat tech public-account positioning, audience segmentation, content pillars, and long-term columns. Use when the user asks about account positioning, reader personas, content strategy, or column planning for a tech/engineering WeChat公众号.
outlining-wechat-tech-posts
Builds WeChat-friendly outlines for tech posts, including multi-level TOC, reader-benefit lines per section, pitfalls and action checklists, and 30-second skim summaries. Use when the user asks for outlines, structures, or tutorial-style blueprints for tech/engineering WeChat公众号.
iterating-wechat-tech-posts
Generates endings/CTAs, pre-publish editorial QA, sentence sharpening, and post-performance retrospectives for WeChat tech posts. Use when the user needs a strong ending, final edit pass, or analytics-driven iteration plan for tech/engineering WeChat公众号.
ideating-wechat-tech-topics
Generates WeChat tech article topics, series, and angles with difficulty and “hit potential” scoring. Use when the user asks for topic ideas, content calendars, anti-myth angles, or serialized planning for tech/engineering WeChat公众号.
formatting-wechat-tech-posts
Designs image plans and rewrites formatting for WeChat-friendly readability (short paragraphs, bolding, separators, restrained emoji). Use when the user asks for illustration ideas, layout guidance, or to convert a draft into publish-ready WeChat formatting.
evidencing-wechat-tech-posts
Produces credible case-study writeups, non-hallucinated data handling, and fact-check lists for WeChat tech posts. Use when the user needs a project recap, results narrative, citations guidance, or “what to verify” checklists in tech/engineering WeChat公众号.
tech-explainer-writer
Use when drafting, rewriting, or polishing public-facing tech explainers for general readers. Trigger on requests to explain complex technical concepts, AI products, system mechanisms, industry trends, or jargon-heavy material in plain language; to turn notes, links, transcripts, slides, or drafts into popular-science articles,公众号内容, scripts, summaries, or “一看就懂” explanations.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always