intent-driven-development
Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation.
- Kind
- Skill
- Works with
- Claude Code, Codex
- Source
- affaan-m/ECC @ d3b8a3e90890
- Path
- skills/intent-driven-development/SKILL.md
- License
- MIT
- Jobs
- Implementation, Requirements interviews, Debugging
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# 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. ## How It Works 1. **Inspect context first** — reads the repository, docs, schemas, and test infrastructure for technical facts before asking any question, while treating product/business constraints as something only the user or a product artifact can supply …