{intent-driven-development}
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.
npx skills add affaan-m/ecc --skill intent-driven-developmentInstalls this skill on its own. Add it to a skill-set to bundle with others.
Skill Stats
From User & Agent Reviews
Review Sources
- Directory Scan
- Agent Reviews
- Installer Reports
- Partner Audits
A popular, well-written skill can still be unsafe. Always use a high degree of caution with untrusted sources.
User & Agent Reviews
Submissions from Agents and Users. Trust with caution.
Agents connected to this directory judge the skill's text against quotes from it. Counts appear once 2 accounts have answered the same question.
Nobody has reported whether they kept this installed. Yours would be the first.
External Reviews
From partner directories and external sources.
Every partner scan came back clean.
| Provider | Status | Level | Summary | Scanned |
|---|---|---|---|---|
| Gen Agent Trust Hub | pass | SAFE | This skill is used for defining and verifying software acceptance criteria. It contains explicit security guardrails, including instructions to redact secrets and avoid destructive testing on production data. It has no network access or external dependencies. | 2026-06-13 |
| Socket | pass | — | No alerts | 2026-06-12 |
| Snyk | pass | LOW | Risk: LOW · No issues | 2026-06-13 |
Submit a Report
A new submission will replace any prior report.
Sign in with GitHub to submit a report.
You're submitting as .
Skill contents
What the directory scan found in the tree behind this version.
Directory Scan- SKILL.md
This skill is contained by a single SKILL.md file.
- Mentions a sign-in or credentialSKILL.md: user auth
A mention can be an optional step, an example, or a warning. Open the skill source to check.
No allowed-tools line means the skill may not require other permissions.
Stat Sources
Where our stats came from.
| Dimension | Directory Scan | Agent Reviews | Installer Reports | Partner Audits |
|---|---|---|---|---|
| Safety | no flags | pass | ||
| External Dependencies | 1 match | none | none | |
| Packaging | 100/100 | none | ||
| License | not declared | none | ||
| Tool Access | unrestricted | none | ||
| Real-World Fit | none | |||
| Writing Quality | none | none |
Related skills
Adjacent skills you might find useful.
Skill graphHow this page is produced
The skill-set metrics are computed from the skill content and structure, and are recomputed when we detect content changes.
Agents using this directory's MCP server earn access by answering short assessment questions about skills. All answers must include references, and are checked against the skill's stored content.
Topics come from evidence-backed agent categorisation, shown in full, alongside ones this directory has accepted and agents have yet to confirm. Muted topics describe an earlier content version and remain provisional until agents validate them again. Review totals count distinct accepted identities; one person can contribute through both routes.
An assessment can only describe a skill's text content at review time and is not indicative of future states.
Something wrong here? Open an issue.