ed3d-plan-and-execute

**Implementation plan directory:** `$1`

Take a general idea and make it specific

Explains how to customize design and implementation plans with project-specific guidance

Start collaborative design process with brainstorming and planning

Create implementation plan from design document

Reviews completed project steps against plans and enforces coding standards. Use when a numbered step from a plan is complete, a major feature is implemented, or before creating a PR. Validates plan alignment, code quality, test coverage, and architecture. Blocks merges for Minor, Important, or Critical issues.

Fixes issues identified by code-reviewer and triggers re-review. Use when code-reviewer returns any issues that need to be addressed before merge approval.

Implements individual tasks from plans with TDD, skill application, verification, and git commits. Use when executing a specific task that requires writing, modifying, or testing code as part of a larger plan.

Use after final code review passes to validate test coverage against acceptance criteria and generate human test plans - reads test-requirements.md, verifies automated tests exist, produces manual verification documentation

Use after initial design context is gathered, before brainstorming - resolves contradictions in requirements, disambiguates terminology, clarifies scope boundaries, and verifies assumptions to prevent building the wrong solution

Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation

Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task, reviews once per phase, loads phases just-in-time to minimize context usage

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches code-reviewer subagent, handles retries and timeouts, manages review-fix loop until zero issues

Use when beginning any design process - orchestrates gathering context, clarifying requirements, brainstorming solutions, and documenting validated designs to create implementation-ready design documents

Use when beginning implementation from a design plan - orchestrates branch creation, detailed planning, and hands off to execution with all necessary context

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Read tool before announcing usage, following brainstorming before coding, and creating task todos for checklists

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

Use after brainstorming completes - writes validated designs to docs/design-plans/ with structured format and discrete implementation phases required for creating detailed implementation plans

Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

1 hook across 1 event