{"id":17936,"plugin_id":"plugins_6a806c0ea80c8191baf8ddda2285e1e8","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:14:30.973Z","digest":"2fbdcf5ca2fd15f4d29fc68045f941abfbd9b46788b703931aa682fab9ada5ff","against":null,"payload":{"description":"Executes a written implementation plan inline, task by task, stopping only on blockers. Use when a plan exists and subagent dispatch is unavailable, or the user wants the plan executed in a separate session.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":219}],"name":"executing-plans","skill_md_contents":"---\nname: executing-plans\ndescription: Executes a written implementation plan inline, task by task, stopping only on blockers. Use when a plan exists and subagent dispatch is unavailable, or the user wants the plan executed in a separate session.\n---\n\n# Executing Plans\n\n## Overview\n\nLoad plan, review critically, execute all tasks, report when complete.\n\n**Announce at start:** \"I'm using the executing-plans skill to implement this plan.\"\n\n**Routing:** Use this skill when subagent dispatch is unavailable OR the user wants a separate execution session; otherwise use subagent-driven-development.\n\n## The Process\n\n### Step 1: Load and Review Plan\n1. Ensure an isolated workspace: use using-git-worktrees to create one or verify the existing one\n2. Read plan file\n3. Review critically - identify any questions or concerns about the plan\n4. If concerns: Raise them with the user before starting\n5. If no concerns: Create todos for the plan items and proceed\n\n### Step 2: Execute Tasks\n\nFor each task:\n1. Mark as in_progress\n2. Follow each step exactly (plan has bite-sized steps)\n3. Run verifications as specified\n4. Mark as completed\n\nTrack completed tasks in a ledger file (reuse subagent-driven-development's convention: `<workspace>/progress.md`, first line naming the plan file, one `Task <N>: complete` line per finished task) so a compacted session can resume where it stopped.\n\n### Step 3: Complete Development\n\nAfter all tasks complete and verified:\n- Before claiming the work is done, apply verification-before-completion: run the verification commands and confirm their output first\n- Announce: \"I'm using the finishing-a-development-branch skill to complete this work.\"\n- **REQUIRED SUB-SKILL:** Use finishing-a-development-branch\n- Follow that skill to verify tests, present options, execute choice\n\n## When to Stop and Ask for Help\n\n**STOP executing immediately when:**\n- Hit a blocker (missing dependency, test fails, instruction unclear)\n- Plan has critical gaps preventing starting\n- You don't understand an instruction\n- Verification fails repeatedly\n\n**Ask for clarification rather than guessing.**\n\n## When to Revisit Earlier Steps\n\n**Return to Review (Step 1) when:**\n- The user updates the plan based on your feedback\n- Fundamental approach needs rethinking\n\n**Don't force through blockers** - stop and ask.\n\n## Remember\n- Review plan critically first\n- Follow plan steps exactly\n- Don't skip verifications\n- Reference skills when plan says to\n- Stop when blocked, don't guess\n- Never start implementation on main/master branch without explicit user consent\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}