executing-plans
Executing Plans
You are executing an approved plan by delegating each task to a fresh subagent. The key insight: context is your fundamental constraint — each task gets a clean context with only what it needs, preventing accumulated noise from degrading quality.
When to Activate
- After a plan is approved (from
writing-plansskill or manual planning) - When a plan file exists at
docs/plans/[issue-id]-plan.md - NOT for ad-hoc changes without a plan
Preconditions
Before executing, validate inputs exist:
- Plan file: Read
docs/plans/<issue-id>-plan.mdusing the Read tool. If the file does not exist, stop with: "No plan file found. Run planning first." - Clean working state: Run
git status --porcelain. If output is non-empty, stop with: "Working directory is dirty. Commit or stash changes before executing the plan."
After preconditions pass, print the activation banner (see _shared/observability.md):
More from brite-nites/britenites-claude-plugins
verification-before-completion
Ensures tasks are genuinely resolved before marking them done. Activates at task checkpoints during plan execution — validates that fixes actually work, tests genuinely pass, and acceptance criteria are met. Prevents premature completion declarations.
16writing-plans
Breaks work into bite-sized tasks before coding. Activates when a multi-step task needs planning — creates tasks small enough for a junior developer to follow (2-5 minutes each), with exact file paths, complete implementation details, and verification steps. References Linear issue context and project-specific test commands from CLAUDE.md.
14systematic-debugging
Four-phase root cause analysis for bug investigation. Activates when debugging unexpected behavior, failing tests, or production issues — follows reproduce, isolate, analyze, fix with defense-in-depth. Uses condition-based waiting instead of arbitrary delays. Available anytime, not tied to the inner loop sequence.
14refine-plan
Refines a v1 project plan into agent-ready tasks with clear context, implementation steps, and validation criteria. Use after /plan-project has produced a v1 plan.
13setup-claude-md
Generates a best-practices CLAUDE.md file for the project. Analyzes the codebase and applies Claude Code best practices for optimal agent performance. Use at project setup or after /create-issues.
13git-worktrees
Creates an isolated git worktree for task execution. Activates when starting work on a planned issue — sets up a new branch with Linear issue ID, runs project setup, and verifies a clean test baseline before coding begins.
12