Intent Driven Development

Turns vague feature requests into testable acceptance criteria before you write code. It inspects your repo first, asks minimal questions about things it can't infer, then produces observable criteria with verification methods. Choose Quick Capture for straightforward changes or Full Brief for anything touching auth, data migrations, or external APIs. It won't block you on trivial stuff, but it will flag when you're about to do something destructive without thinking it through. The real value is in how it separates technical facts it can discover from business constraints it can't, so you're not guessing what "done" means halfway through implementation.

skills.sh installs: 4.8K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill intent-driven-development --agent claude-code

Installs into .claude/skills of the current project.

Files

Intent-Driven Development

Produce useful acceptance criteria without turning specification into ceremony. Inspect available context first, expose genuine ambiguity, and choose verification methods that fit the work and its risk.

When to Activate

User asks to clarify a feature, define acceptance criteria, or de-risk a change before implementation
Request touches security, authentication, persistent data, migrations, external APIs, or compliance
User wants to prepare a handoff artifact for another agent or team
Request is ambiguous enough that the expected outcome is not yet observable or testable
User explicitly invokes this skill with /intent-driven-development

Do not activate for trivial edits, straightforward one-line fixes, active debugging sessions, code review requests, or implementation requests whose acceptance conditions are already clear.