edd

Plugin edd in jimeh/agentic. Commands read from the repo's manifest — 10 days ago.

Skills (1)

• edd

  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

Slash commands (9)

• /edd:edd-close

  Archive a completed, deferred, or dropped EDD feature

• /edd:edd-draft

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

• /edd:edd-embed

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

• /edd:edd-impl

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

• /edd:edd-init

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

• /edd:edd-new

  Create a new EDD feature with scaffolded evals

• /edd:edd-spec

  Freeze evals and generate (or refine) product spec + task list

• /edd:edd-status

  Show EDD feature index with status summary and actionable prompts

• /edd:edd-verify

  Verify implementation against evals with a strict, independent QA agent

Subagents (4)

• eval-brainstormer

  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 cre

• implementer

  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: "Im

• spec-writer

  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" assis

• verifier

  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