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
- none. No account, no API key, no payment — this skill is a single guidance file.
- Level
- Beginner
- 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:
Quick answer
Intent-Driven Development is a free Muse skill and process for producing useful acceptance criteria without turning specification into ceremony. When a request is ambiguous or high-impact, covering security, authentication, persistent data, migrations, external APIs or compliance, it inspects available context first, then turns changes into scoped, verifiable acceptance criteria before implementation.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: none. No account, no API key, no payment — this skill is a single guidance file. Install "Intent-Driven Development" for me. It turns ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation, so a complex request becomes testable before work starts. Once it is installed, I use it by bringing an unclear or risky change to my agent and asking it to frame the acceptance criteria. Repository: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/intent-driven-development/SKILL.md Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file from the repository path into a temporary folder and look inside. It is the only file this skill needs. 2. Integrity check: Skill Harbor reviewed this listing on 2026-10-10 and recorded the fingerprint below. I want you to compute the SHA-256 of the downloaded file and compare: - SKILL.md: SHA-256 e34045f7b3bf6a6fbd364f85c7bc81d8208e18bb929ceff80bbc987f78aadea8 If a fingerprint does not match, I want you to stop before installing and tell me the files changed since Skill Harbor's review, so the new version is unverified. Show me your safety findings and give me three choices: (a) wait for Skill Harbor to re-review the listing (recommended), (b) analyze the new files in detail first and then decide, (c) install anyway knowing the risk. Then wait for my answer before doing anything else. 3. Safety check: I want to see your findings explicitly, in short separate items: - every network address the code contacts (expected: none, this file is guidance text only) - every shell command it runs (expected: none) - every place credentials, API keys or personal data are read, stored or sent (expected: none) - any obfuscated or encoded code (expected: none, plain markdown guidance) If anything looks suspicious, stop and explain it to me before continuing. 4. Confirmation: before installing, give me a short summary of what the skill does plus your safety findings, and wait for my explicit "yes, install". 5. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "intent-driven-development". 6. Verify with no network calls: frontmatter valid, skill name is intent-driven-development, and the file is in place. 7. Report what was installed, where, and what I still need to do myself. Nothing else is required: to use the skill afterwards, I bring an ambiguous or high-impact change to my agent and ask it to produce scoped, verifiable acceptance criteria. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.