Spec-driven development for Claude Code — author validated, ISO/IEC/IEEE 29148-aligned specs, then plan and build against them.
Rust
18
321 commits
updated Sep 17, 2026
quoin is a bundle of Quire modules, agent skills, and workflows for
authoring ISO/IEC/IEEE 29148-aligned software specifications and other technical
documents. It includes prepackaged modules for the spec vocabulary and ideation/authoring/review/planning
workflows agents need to write and validate specs directly as Markdown.
quoin is built on the Quire document standard and validation engine by Agent-IX.
Why: AI agents write code fast but drift from vague intent. Quoin makes the spec the source of truth — your agent authors a validated, traceable spec first, then plans and builds against it.
In Claude Code, Codex, or the coding agent of your choice:
Ideate, then pass your idea to /specify. A specification containing user stories, functional requirements,
stakeholder requirements, non-functional requirements, and other artifacts will be created.
> /specify an electron app for tracking spice production
Use /spec-review for agent-assisted review. Multiple analysis tasks will run in parallel and output Reviews
with Findings and suggested fixes.
> /spec-review review the specs for the spice production tracker.
Build the test traceability matrix and plan. These skills will break the work down into a plan
with multiple tasks.
> /spec-matrix /spec-to-plan prep the spice tracking app for coding
Call /implement-plan to trigger your coding agent to begin work on the plan.
> /implement-plan build the spice tracking app
/gap-analysis audits the repository: UserStory and Functional Requirements implemented and tested,
using the traceability matrix as the guide, plus the reverse gap — code with no owning requirement — and
stubs standing behind a covered row. It is planless by default, so a repository whose work predates
planning can still be audited; the review it emits records Plan completion: not assessed.
/gap-analysis will optionally perform a semantic comparison of spec, code, and tests.
> /gap-analysis
Pass a plan to add completion bookkeeping — every Task done, done tasks in dependency order, and
plan.md checkboxes matching task status. The repository audit is unchanged by it: a plan never narrows
the scope or suppresses a finding outside its tasks.
> /gap-analysis --plan Plan-001
The default module set defines the spec archetypes and domain-object vocabulary.
Artifact archetypes — the document types you author:
| Module | Archetypes |
|---|---|
| spec-artifacts-iso | StR, FR, NFR, US, IT, TC, Spec, master-requirements |
| spec-artifacts-app | ApplicationSpec, MasterRequirements |
| spec-artifacts-process | ADR, Plan, Task, Review, Finding, TestMatrix, Standard |
Domain objects — prefab templates for common objects
| Module | Objects |
|---|---|
| spec-objects-business | domain, entity, value_object, aggregate_root, nested_entity, repository, event, state_machine, process, enumeration |
| spec-objects-architecture | api_endpoint, data_schema, queue, action, ui_component, interface, external_contract, extension_point, binary_format, rate_limit |
| spec-objects-enterprise | capability, business_function, value_stream, decision, objective, principle, kpi |
| spec-objects-operational | configuration, migration, sli, slo, alert, runbook, incident, deployment |
| spec-objects-security | auth_flow, permission, scope, role, secret, encryption_key, session_config, data_classification, trust_boundary, audit_event, threat, control, risk, vulnerability, asset, attack_surface, policy, … |
specify — create or edit spec files using catalog authoring packs + Quire validationspec-review — review specification for quality, consistency, and completenessspec-matrix — build/maintain the requirements Test Matrix at 100% coveragespec-to-plan — convert StR/FR/NFR into a TDD project planspec-ideation — loose, exploratory drafting before formal authoringspec-app-review / spec-object-review — application-spec and domain-object auditsspec-integrity-analysis — completeness, consistency, and atomicity quality gatesspec-scope-boundary-analysis — system boundaries and responsibility allocationspec-dependency-analysis — separates enablement work from feature workspec-evidence-analysis — verification methods and evidence artifacts per requirementspec-failure-domain-analysis — unstated failure modes, identity confusion, edge casesspec-risk-complexity-analysis — technical risk and volatility before taskingspec-security-analysis — applicable security standards and compliance traceabilityInstalling quoin is two steps: the native CLI (from a GitHub Release) and a plugin that adds the skills and workflows to your coding agent. The same skill bundle installs into Claude Code, OpenAI Codex, opencode, and GitHub Copilot — pick your agent below. No Anthropic API key is required — your existing agent subscription is used.
1. Install the CLIs (quoin plus ix-flow, which runs the workflow lifecycle commands):
# Download the archive for your host from the stable GitHub Release, verify it
# with quoin-update-manifest.json, extract `quoin`, then place it on PATH.
npm install -g @agent-ix/ix-flow@latest
Supported native targets and archive names are listed in the native release contract.
2. Add the plugin to your coding agent:
Run these inside Claude Code:
/plugin marketplace add agent-ix/quoin
/plugin install quoin@quoin
codex plugin marketplace add agent-ix/quoin
codex plugin add quoin
Or browse and install quoin from the /plugins menu inside the Codex TUI.
Install the skills with the GitHub CLI (requires gh ≥ 2.90.0). --all installs
the whole bundle; --scope user makes it available in every repo:
gh skill install agent-ix/quoin --all --scope user --agent opencode
With the Copilot CLI:
copilot plugin marketplace add agent-ix/quoin
copilot plugin install quoin@quoin
Or install the skills with the GitHub CLI (requires gh ≥ 2.90.0):
gh skill install agent-ix/quoin --all --scope user --agent github-copilot
Either way, that registers quoin's spec-authoring skills and workflows so you can drive them by asking the agent.
The primary way users author specs is by asking an agent, which invokes the bundled skills and workflows.
Inspect the spec vocabulary and manage installed modules:
quoin catalog list
quoin catalog show FR
quoin catalog validate
quoin plugin install path:../spec-objects-business
quoin plugin list
Quoin also provides rights-safe, project-owned assurance workflows: evaluate a generic ClauseSet with Quire, account for discharge without a score, render an authored argument with explicit sufficiency decisions, and publish immutable experiment or operational evidence:
quire clauses evaluate --module ./modules/widget --authority example.invalid \
--set widget-rules --version 1.0.0 \
--context product=widget --format json > binding.json
quoin discharge --binding binding.json --facts discharge-facts.json \
--as-of 2026-08-28T00:00:00Z --json
quoin assurance --argument AA-001 --decisions sufficiency-decisions.json \
--as-of 2026-08-28T00:00:00Z
quoin evidence record-experiment --repo . --input experiment.json
quoin evidence record-operational --repo . --input operational.json
See Assurance workflows for the record shapes, expiry behavior, and the boundary that leaves existing run records unchanged.
make rust-build
make rust-test
make rust-lint
The technical specification for this library was itself authored with the spec-artifacts-iso module — see
spec/spec.md.
quoin is part of the Agent-IX ecosystem built on these core libraries:
Rust
98.1%
Spec-driven development for Claude Code — author validated, ISO/IEC/IEEE 29148-aligned specs, then plan and build against them.
Rust
18
321 commits
updated Sep 17, 2026
quoin is a bundle of Quire modules, agent skills, and workflows for
authoring ISO/IEC/IEEE 29148-aligned software specifications and other technical
documents. It includes prepackaged modules for the spec vocabulary and ideation/authoring/review/planning
workflows agents need to write and validate specs directly as Markdown.
quoin is built on the Quire document standard and validation engine by Agent-IX.
Why: AI agents write code fast but drift from vague intent. Quoin makes the spec the source of truth — your agent authors a validated, traceable spec first, then plans and builds against it.
In Claude Code, Codex, or the coding agent of your choice:
Ideate, then pass your idea to /specify. A specification containing user stories, functional requirements,
stakeholder requirements, non-functional requirements, and other artifacts will be created.
> /specify an electron app for tracking spice production
Use /spec-review for agent-assisted review. Multiple analysis tasks will run in parallel and output Reviews
with Findings and suggested fixes.
> /spec-review review the specs for the spice production tracker.
Build the test traceability matrix and plan. These skills will break the work down into a plan
with multiple tasks.
> /spec-matrix /spec-to-plan prep the spice tracking app for coding
Call /implement-plan to trigger your coding agent to begin work on the plan.
> /implement-plan build the spice tracking app
/gap-analysis audits the repository: UserStory and Functional Requirements implemented and tested,
using the traceability matrix as the guide, plus the reverse gap — code with no owning requirement — and
stubs standing behind a covered row. It is planless by default, so a repository whose work predates
planning can still be audited; the review it emits records Plan completion: not assessed.
/gap-analysis will optionally perform a semantic comparison of spec, code, and tests.
> /gap-analysis
Pass a plan to add completion bookkeeping — every Task done, done tasks in dependency order, and
plan.md checkboxes matching task status. The repository audit is unchanged by it: a plan never narrows
the scope or suppresses a finding outside its tasks.
> /gap-analysis --plan Plan-001
The default module set defines the spec archetypes and domain-object vocabulary.
Artifact archetypes — the document types you author:
| Module | Archetypes |
|---|---|
| spec-artifacts-iso | StR, FR, NFR, US, IT, TC, Spec, master-requirements |
| spec-artifacts-app | ApplicationSpec, MasterRequirements |
| spec-artifacts-process | ADR, Plan, Task, Review, Finding, TestMatrix, Standard |
Domain objects — prefab templates for common objects
| Module | Objects |
|---|---|
| spec-objects-business | domain, entity, value_object, aggregate_root, nested_entity, repository, event, state_machine, process, enumeration |
| spec-objects-architecture | api_endpoint, data_schema, queue, action, ui_component, interface, external_contract, extension_point, binary_format, rate_limit |
| spec-objects-enterprise | capability, business_function, value_stream, decision, objective, principle, kpi |
| spec-objects-operational | configuration, migration, sli, slo, alert, runbook, incident, deployment |
| spec-objects-security | auth_flow, permission, scope, role, secret, encryption_key, session_config, data_classification, trust_boundary, audit_event, threat, control, risk, vulnerability, asset, attack_surface, policy, … |
specify — create or edit spec files using catalog authoring packs + Quire validationspec-review — review specification for quality, consistency, and completenessspec-matrix — build/maintain the requirements Test Matrix at 100% coveragespec-to-plan — convert StR/FR/NFR into a TDD project planspec-ideation — loose, exploratory drafting before formal authoringspec-app-review / spec-object-review — application-spec and domain-object auditsspec-integrity-analysis — completeness, consistency, and atomicity quality gatesspec-scope-boundary-analysis — system boundaries and responsibility allocationspec-dependency-analysis — separates enablement work from feature workspec-evidence-analysis — verification methods and evidence artifacts per requirementspec-failure-domain-analysis — unstated failure modes, identity confusion, edge casesspec-risk-complexity-analysis — technical risk and volatility before taskingspec-security-analysis — applicable security standards and compliance traceabilityInstalling quoin is two steps: the native CLI (from a GitHub Release) and a plugin that adds the skills and workflows to your coding agent. The same skill bundle installs into Claude Code, OpenAI Codex, opencode, and GitHub Copilot — pick your agent below. No Anthropic API key is required — your existing agent subscription is used.
1. Install the CLIs (quoin plus ix-flow, which runs the workflow lifecycle commands):
# Download the archive for your host from the stable GitHub Release, verify it
# with quoin-update-manifest.json, extract `quoin`, then place it on PATH.
npm install -g @agent-ix/ix-flow@latest
Supported native targets and archive names are listed in the native release contract.
2. Add the plugin to your coding agent:
Run these inside Claude Code:
/plugin marketplace add agent-ix/quoin
/plugin install quoin@quoin
codex plugin marketplace add agent-ix/quoin
codex plugin add quoin
Or browse and install quoin from the /plugins menu inside the Codex TUI.
Install the skills with the GitHub CLI (requires gh ≥ 2.90.0). --all installs
the whole bundle; --scope user makes it available in every repo:
gh skill install agent-ix/quoin --all --scope user --agent opencode
With the Copilot CLI:
copilot plugin marketplace add agent-ix/quoin
copilot plugin install quoin@quoin
Or install the skills with the GitHub CLI (requires gh ≥ 2.90.0):
gh skill install agent-ix/quoin --all --scope user --agent github-copilot
Either way, that registers quoin's spec-authoring skills and workflows so you can drive them by asking the agent.
The primary way users author specs is by asking an agent, which invokes the bundled skills and workflows.
Inspect the spec vocabulary and manage installed modules:
quoin catalog list
quoin catalog show FR
quoin catalog validate
quoin plugin install path:../spec-objects-business
quoin plugin list
Quoin also provides rights-safe, project-owned assurance workflows: evaluate a generic ClauseSet with Quire, account for discharge without a score, render an authored argument with explicit sufficiency decisions, and publish immutable experiment or operational evidence:
quire clauses evaluate --module ./modules/widget --authority example.invalid \
--set widget-rules --version 1.0.0 \
--context product=widget --format json > binding.json
quoin discharge --binding binding.json --facts discharge-facts.json \
--as-of 2026-08-28T00:00:00Z --json
quoin assurance --argument AA-001 --decisions sufficiency-decisions.json \
--as-of 2026-08-28T00:00:00Z
quoin evidence record-experiment --repo . --input experiment.json
quoin evidence record-operational --repo . --input operational.json
See Assurance workflows for the record shapes, expiry behavior, and the boundary that leaves existing run records unchanged.
make rust-build
make rust-test
make rust-lint
The technical specification for this library was itself authored with the spec-artifacts-iso module — see
spec/spec.md.
quoin is part of the Agent-IX ecosystem built on these core libraries:
Rust
98.1%