execute-plan
The execute-plan command guides developers through feature implementation by breaking down a planning document into ordered tasks, executing them interactively one at a time, and tracking progress. Use this when implementing a feature that has a corresponding markdown planning document, starting work on a defined feature branch, or resuming work on a partially completed feature to maintain context and ensure tasks are addressed systematically rather than ad-hoc.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/codeaholicguy/ai-devkit/HEAD/commands/execute-plan.md -o ~/.claude/commands/execute-plan.mdexecute-plan.md
Help me work through a feature plan one task at a time.
1. **Gather Context** — If not already provided, ask for: feature name (kebab-case, e.g., `user-authentication`), brief feature/branch description, planning doc path (default: latest matching `docs/ai/planning/YYYY-MM-DD-feature-{name}.md`; fallback `docs/ai/planning/feature-{name}.md`), and any supporting docs (design, requirements, implementation).
2. **Use Memory for Context** — Search for prior implementation notes/patterns before starting: `npx ai-devkit@latest memory search --query "<feature implementation plan>"`.
3. **Load & Present Plan** — Read the planning doc and parse task lists (headings + checkboxes). Present an ordered task queue grouped by section, with status: `todo`, `in-progress`, `done`, `blocked`.
4. **Interactive Task Execution** — For each task in order: display context and full bullet text, reference relevant design/requirements docs, offer to outline sub-steps before starting, prompt for status update (`done`, `in-progress`, `blocked`, `skipped`) with short notes after work, and if blocked record blocker and move to a "Blocked" list.
- **Reuse before writing** — grep for existing utilities/functions before adding new ones. Reuse only if it fits cleanly; don't force-fit a near-match (a small duplicate beats a wrong abstraction).
- **Breaking changes** — if all callers live in this repo and can be updated atomically, modify in place and update callers in the same change. If callers are external, public, or cross-service, add a new function and deprecate the old one (parallel change) rather than mutating the existing signature.
5. **Update Planning Doc** — After each completed or status-changed task, run `/update-planning` to keep the selected planning doc accurate.
6. **Store Reusable Knowledge** — Save reusable implementation guidance/decisions with `npx ai-devkit@latest memory store ...`.
7. **Session Summary** — Produce a summary: Completed, In Progress (with next steps), Blocked (with blockers), Skipped/Deferred, and New Tasks.
8. **Next Command Guidance** — Continue `/execute-plan` until plan completion; then run `/check-implementation`.AI DevKit · Exchange information with active Codex, Claude Code, and other AI agents using ai-devkit agent list, detail, and send. Use when an agent needs to find another active agent, read its recent context, send it information, or request information back.
AI DevKit · Manage running AI agents with ai-devkit agent commands. Use when an agent needs to identify itself, list agents, start workers, inspect agent detail, assign work, group agents, resume sessions, stop agents, or delegate work to other agents.
AI DevKit · Supervise multi-agent workflows over repeated passes: poll progress, unblock waiting agents, coordinate dependencies, relay outputs, resolve conflicts, and verify completion. Use only for ongoing multi-agent coordination, not one-off list/detail/send/start/kill actions.
AI DevKit · Use when the user asks to brainstorm, ideate, generate ideas, expand options, challenge ideas, pressure-test ideas, compare concepts, narrow choices, name something, plan content angles, explore strategy, evaluate product ideas, technical approaches, experiments, or decisions.
AI DevKit · Compare implementation with design and requirements docs to ensure alignment.
AI DevKit · Pre-push code review against design docs.
AI DevKit · Safe git commit workflow for AI coding agents. Use when the user asks to commit, prepare a commit, stage changes, create a PR-ready checkpoint, or finish work with a conventional commit while avoiding unrelated user changes.
AI DevKit · Design phase guidance for reviewing feature design against requirements. Use when the user wants to validate architecture, review design docs, resolve design trade-offs, or run dev-lifecycle phase 3.