edd

Archive a completed, deferred, or dropped EDD feature

Refine and iterate on evals for a Draft-phase EDD feature

Copy EDD commands, agents, and skill into the local project for portability

Implement a feature from its spec using parallel sub-agents where possible

Bootstrap the EDD (Eval-Driven Development) system into the current repo

Adversarial requirements reviewer for EDD features. Spawned during /edd-new to suggest edge cases, error scenarios, and constraints the user may have missed. Use this agent when creating a new EDD feature or when the user wants help brainstorming acceptance criteria. <example> Context: User just created a new EDD feature user: "I created EDD feature 003 for user tagging. Can you brainstorm edge cases?" assistant: "I'll use the eval-brainstormer agent to review your feature for gaps." <commentary> User explicitly asks for requirements brainstorming on an EDD feature. </commentary> </example> <example> Context: User is writing evals and wants adversarial review user: "What could go wrong with this feature? Review my evals." assistant: "I'll use the eval-brainstormer agent to do an adversarial review." <commentary> User wants someone to poke holes in their acceptance criteria. </commentary> </example>

Implements a single task or batch of related tasks from an EDD feature's task list. Spawned by /edd-impl with a clean context scoped to specific tasks. Use this agent when executing implementation tasks for an EDD feature. <example> Context: Orchestrator is dispatching implementation tasks user: "Implement Task 1 and Task 2 for EDD feature 003" assistant: "I'll use the implementer agent to implement these tasks." <commentary> Parallel-safe tasks dispatched to an implementer with scoped context. </commentary> </example> <example> Context: Sequential task needs implementation after prerequisites user: "Task 3 for EDD-003 is ready, its dependencies are complete" assistant: "I'll use the implementer agent to implement Task 3." <commentary> Dependent task dispatched after its prerequisites are verified complete. </commentary> </example>

Derives a product spec and implementation task list from frozen EDD evals. Spawned by /edd-spec with a clean context. Use this agent when an EDD feature's evals are ready and a spec needs to be generated. <example> Context: User has frozen evals and wants a spec generated user: "/edd-spec 003" assistant: "I'll use the spec-writer agent to derive a spec from the frozen evals." <commentary> The /edd-spec command triggers spec-writer to produce spec.md and tasks.md. </commentary> </example> <example> Context: User wants to regenerate a spec after reverting to Draft user: "I updated the evals, regenerate the spec for feature 003" assistant: "I'll use the spec-writer agent to derive a fresh spec from the updated evals." <commentary> Evals were modified after a revert to Draft; spec needs regeneration. </commentary> </example> <example> Context: User reviewed spec and wants targeted changes user: "/edd-spec 003 split task 4 into smaller steps and add error handling to the API section" assistant: "I'll use the spec-writer agent to refine the existing spec based on your feedback." <commentary> Existing spec/tasks get refined rather than regenerated from scratch. </commentary> </example>

Strict, skeptical QA verifier for EDD features. Checks implementation against the evals with fresh eyes — does NOT receive the spec or task list. Spawned by /edd-verify with a clean context. <example> Context: Implementation is complete and needs verification user: "/edd-verify 003" assistant: "I'll use the verifier agent to check the implementation against the evals." <commentary> Feature implementation complete, verifier checks against evals only. </commentary> </example> <example> Context: User wants verification with browser testing user: "/edd-verify 003 http://localhost:5173" assistant: "I'll use the verifier agent to verify against evals, including browser testing." <commentary> URL provided for runtime verification of UI criteria. </commentary> </example>

Use when the user explicitly references the EDD workflow: "edd", "eval-driven development", "write evals", "feature evals", "edd-spec", "edd-impl", "edd-verify", or when working within an existing EDD feature directory (docs/features/NNN-*/). Also use when the user asks to refine or continue work on evals.md, spec.md, or tasks.md files that follow the EDD structure. Do NOT trigger for general feature requests unless the user specifically asks to use the EDD workflow.