Define and execute eval workflows across DEFINE, IMPLEMENT, and VERIFY phases.
npx skills add https://github.com/alfredolopez80/multi-agent-ralph-loop --skill edd
Please help me install this Agent Skill. Skill: edd Source: https://github.com/alfredolopez80/multi-agent-ralph-loop/tree/main/.claude/skills/edd Command: npx skills add https://github.com/alfredolopez80/multi-agent-ralph-loop --skill edd
Eval-Driven Development (EDD) provides a disciplined pattern that enforces a define-before-implement workflow with structured evaluations to improve software quality and reduce rework.
Invoke the EDD workflow to define, implement, and verify a feature using the CLI.
High-intent search queries and answers about installing and using this skill.
Eval-driven development (EDD) is a define-before-implement workflow that enforces quality-first development through structured evaluations. It requires defining clear eval criteria before implementation to improve software quality and reduce rework.
You can structure feature specifications using a TEMPLATE.md file to define clear evaluation criteria, categorizing checks into CC-, BC-, and NFC- formats to establish a unified define, implement, and verify workflow.
Yes, running eval-driven development workflows requires an edd.sh CLI, a local ~/.claude/evals directory to manage eval definitions and results, and a TEMPLATE.md system to operate properly.
Yes, you can use Swarm Mode integration to deploy parallel evaluation teams that assess checks across CC-, BC-, and NFC- criteria, enabling rapid validation and faster software delivery.
The best way to reduce software rework is adopting a define-before-implement evaluation workflow, which scopes and executes structured evals across DEFINE, IMPLEMENT, and VERIFY phases to catch issues early.
ldk-hubAutomate eval-driven development workflows for Claude Code sessions.
nnexaiAudit completed AI development phases against defined evaluation specifications.
rahmatullahbossRun validation checks in MAX-PARALLEL mode against workflows.
iDako7Implement test-driven development with 80% coverage across unit, integration, and end-to-end tests.
