Affaan MustafaTrading lead at Jump Trading; ECC 290k+ stars5,300 installs on skills.sh

Intent Driven Development

Turn ambiguous or high-impact product and engineering changes into scoped.

Use in my agent
Use Edge to load the skill intent-driven-development from affaan-m/ecc for my task. If Edge is not set up, read getedge.cc/SKILL.md and ask me first.
Works in any agentClaude CodeCodexCursorClaude appChatGPT+ any other agent
affaan-m/ecc
Security state: reviewed

2 static scans, 0 counted findings.

Edge checks it again each time your agent loads it.

SKILL.md1 file · 16.8 KB

From the affaan-m public repository. Edge did not write or edit this skill.

What it does

  • 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.
AM

Why Affaan Mustafa

Compute Trading Lead at Jump Trading. Each fact links its public source.

  • Role at Jump Trading

    His GitHub bio says Compute Trading Lead at Jump Trading, previously founding The Agentic Desk.

    GitHub profile
  • Hugely starred agent harness repo

    ECC has 290k+ GitHub stars.

    GitHub repo
  • Security tool with traction

    agentshield has 1.3k+ GitHub stars.

    GitHub repo

Public sources, checked Oct 26, 2026.

How it works

  1. 1
    Copy

    Try for free gives you one prompt.

  2. 2
    Paste

    Paste it into Claude Code, Codex or Cursor.

  3. 3
    Ask

    Ask for the outcome. Your agent loads Intent Driven Development.

Related skills

JA
Requirements Engineering
jasonkneen

Transform vague feature ideas into clear, testable requirements using EARS format. Capture user stories, define acceptance criteria, identify edge cases, and validate completeness before moving to design.

DO
Story Readiness
donchitos

Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.

NA
Requirements Analyst
nahisaho

Copilot agent that assists with requirements analysis, user story creation, specification definition, and acceptance criteria definition Trigger terms: requirements, EARS format, user stories, functional requirements, no

PH
User Stories
phuryn

Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog

HU
Visual PR
humanlayer

Only use when the user explicitly invokes this skill by name.

+538 installs this week
OB
Test Driven Development
obra

Use when implementing any feature or bugfix, before writing implementation code

+7.7K installs this week
Evidence

No evidence record yet

No measured run with and without this skill yet, so this page makes no performance claim. 2 static scans, 0 counted findings. Security state at 2026-11-17: reviewed. Static scans check the code, not how well the skill works.

State definitions
SKILL.md17,199 bytes · Open on GitHub

Skill details

Security scansReviewed

2 static scans, 0 counted findings. Security state at 2026-11-17: reviewed. Edge checks it again each time your agent loads it.

Edge static checks (Edge-run): edge-static/1.0.2. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: not supplied.

Edge committed-secret checks (Edge-run): edge-secrets/1.0.0. Scope: Credentials committed in the skill's files (values never shown). Raw findings: not supplied.

Socket (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.

Snyk (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.

Edge static checks
Pass · 0 counted findings · 2026-11-17
Edge committed-secret checks
Pass · 0 counted findings · 2026-11-17
Creator, source & licenceaffaan-m

From the affaan-m public repository. Edge did not write or edit this skill.

Repository
affaan-m/ecc
Revision
d3b8a3e908904e242ed2dbe66af62cca71131419
Package hash
sha256:ff808e2d224041d79c4d965bd1a841bd2e6ad8a34be24795e956881694714568
Licence
MIT
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.
Quoted from the skill’s own description
Read skill files1 file

1 file, 16.8 KB at revision d3b8a3e90890.

Questions about Intent Driven Development

What does Intent Driven Development do?

Turn ambiguous or high-impact product and engineering changes into scoped. Published by Affaan Mustafa (affaan-m/ecc).

Is Intent Driven Development safe to use?

Edge security state: Reviewed (2 Edge-run static scans, scanned Nov 17, 2026). The Evidence tab shows the scan.

How do I use Intent Driven Development in Claude Code, Codex or Cursor?

Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.