intent-driven-developmentcommit ff1bfa1SKILL.md · Requirements
Intent-Driven Development
Turns ambiguous or high-impact changes into scoped, verifiable acceptance criteria before or alongside implementation.
npx skills add affaan-m/ECC --skill intent-driven-developmentCommand selected. Copy it manually.
- Permissions
- read-repo
- write-files
- shell
- network
- Compatible with
- Claude Code, Codex, Cursor, Copilot, OpenCode
- GitHub
- 294.3k
- Source
- Community · Affaan Mustafa
- Status
- Scan passed
- License
- MIT
- Category
- Requirements
Core rule
Inspect the repository before asking; take business constraints only from the user or product artifacts, never from code.
Execution Phases
Phase 01Inspect context first
Read the repo, docs, schemas and test setup for technical facts; ask only questions that cannot be inferred and change scope.
Phase 02Choose the depth
Use Quick Capture (3–7 criteria) for low or moderate risk, and a Full Acceptance Brief for security, data, migration or cross-system changes.
Phase 03Write observable criteria
Each AC states a starting condition, trigger, expected outcome, prohibited side effect, verification method and priority, without vague words like 'correctly'.
Phase 04Proceed or wait
For clear requests with no blocking risk, record the criteria and continue; for risky changes, present blockers and wait for confirmation.
Phase 05Revise criteria
If an AC cannot be met mid-implementation, mark it [revised], update scope or verification, and re-present only the changed criteria.
Permissions (summarised from SKILL.md)
| Capability | Needed | Details |
|---|---|---|
| File writes | Limited | Does not write an acceptance document into the repo, alter project files or create a branch unless the user asks. |
| Command execution | Limited | Does not run destructive tests, migrations, security probes, load tests or paid external calls without explicit authorization. |
| Network outbound | Not required | The skill does not call for network access. |
SKILL.md frontmatter (YAML)
---
name: intent-driven-development
description: Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security/data/migration/integration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straightforward fixes, active debugging, code review, or implementation requests whose acceptance conditions are already clear unless the user explicitly invokes this skill.
---