Composable agent skills for Intent-Driven Development (IDD): humans own product intent, ambiguous decisions, and acceptance; agents own planning, implementation, verification, review, evidence, and documentation reconciliation.
Core invariant:
Implementation must not silently redefine intent.
The plugin turns a feature request into a gated chain:
Intent -> Spec -> Domain Knowledge -> Decisions -> Implementation -> Evidence -> Human Acceptance
| Group | Skills | Purpose |
|---|---|---|
| Intent | intentdriven, map-authority, grill-feature, write-spec, prototype-ui |
Discover which local or external artifact owns each truth type, clarify product intent, write business contract, branch into UI prototypes when interaction choices matter. |
| Decisions / Bridge | reconcile-domain, record-decision, plan-implementation |
Keep vocabulary/domain/ADRs aligned and translate business intent into a technical plan. |
| Execution / Evidence | implement-feature, verify-feature, review-change, prepare-acceptance |
Execute the approved plan, prove acceptance criteria, adversarially review, package evidence. |
| Consistency | detect-drift, resolve-conflict, reconcile-docs |
Detect semantic divergence, surface human decision packets, update docs only after confirmed intent. |
Install the whole skill pack:
npx skills add dmltdev/intentdrivenInstall only the root workflow skill:
npx skills add dmltdev/intentdriven --skill intentdrivenReplace intentdriven with any skill from the table above to install a narrower phase skill.
Install from GitHub as a Claude Code plugin marketplace:
/plugin marketplace add dmltdev/intentdriven
/plugin install intentdriven@intentdriven
For local development, pass the path to your local clone:
/plugin marketplace add /path/to/intentdriven
/plugin install intentdriven@intentdriven
Install from GitHub with pi's package installer:
pi install git:github.com/dmltdev/intentdrivenInstall project-locally, writing the package entry to .pi/settings.json:
pi install -l git:github.com/dmltdev/intentdrivenRun a one-off pi session with the package loaded:
pi -e git:github.com/dmltdev/intentdrivenInstall from GitHub as an omp plugin marketplace. See https://omp.sh/docs/plugins for omp's plugin marketplace workflow.
omp plugin marketplace add dmltdev/intentdriven
omp plugin install intentdriven@intentdrivenFor local development, pass the path to your local clone:
omp plugin marketplace add /path/to/intentdriven
omp plugin install intentdriven@intentdriven --forceInstall from GitHub as a Codex plugin marketplace:
codex plugin marketplace add dmltdev/intentdriven --ref main
codex plugin add intentdriven@intentdrivenFor local development, pass the path to your local clone:
codex plugin marketplace add /path/to/intentdriven
codex plugin add intentdriven@intentdrivenInvoke /intentdriven for an end-to-end feature lifecycle, or invoke a narrower skill directly when entering a known phase.
The expected state artifact is described in skills/intentdriven/references/feature-state.md.
- Platform-agnostic by default. Linear, Jira, Confluence, Notion, local Markdown, ADRs, tests, schemas, and code are possible authorities for different truths.
- Local project docs or agent instructions should define the source-of-truth boundary: truth type -> authority -> location/link -> write policy -> conflict policy.
- The plugin recommends a minimum authority map when none exists, but does not enforce a file name, schema, docs platform, or product-management tool.
- Drift between documented intent and implemented behavior is information. Agents must classify and surface it; they must not silently choose a winner.