Intent-Driven Development
Turn ambiguous or high-impact changes into scoped, verifiable acceptance criteria before implementation: de-risk security, data, and migration work.
- What
- Turn ambiguous or high-impact changes into scoped, verifiable acceptance criteria before implementation: de-risk security, data, and migration work.
- Cost
- Free
- Needs
- Use "Intent-Driven Development" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a process skill for producing useful acceptance criteria without turning specification into ceremony. When a request is ambiguous or high-impact (security, authentication, persistent data, migrations, external APIs, compliance), it inspects available context first (repo, docs, schemas, test infrastructure), exposes the genuine ambiguity, and chooses verification methods that fit the work and its risk, before or alongside implementation. It also prepares handoff artifacts for another agent or team, making complex requests testable. Explicitly not for trivial edits, one-line fixes, active debugging, code review, or requests whose acceptance conditions are already clear. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: produces documents and criteria, not code; the value depends on answering its questions honestly; overuse on trivial tasks adds ceremony for nothing. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Intent-Driven Development" with your Muse. Prerequisites: an ambiguous or high-impact change to scope (feature, migration, security-sensitive work). Produces criteria documents, not code. Pure guidance skill, nothing to install. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/intent-driven-development/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Before we implement: turn this change into scoped, verifiable acceptance criteria. Inspect the repo context first, then surface the genuine ambiguities." 3. For a handoff, ask: "Package the acceptance criteria as a handoff artifact another agent can implement and verify independently." Tip: don't invoke it for trivial edits or clear-cut fixes; the skill says so itself. Safety: a skill is plain-text instructions; it runs nothing by itself. Criteria are only as good as the context you give it, so point it at the real docs and schemas.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.