quoin

Plugin quoin from marketplace agent-ix in agent-ix/agent-plugins. Commands read from the repo's manifest — 3 days ago.

Skills (22)

• rust-style

  The Rust idioms quoin's `rust/` workspace is built on — the boundary contract (exit taxonomy, canonical JSON, stream discipline), error envelopes with stable codes, the workspace lint policy, untrusted-input hardening on stdin, the `#[trace(...)]` criterion-tag test convention, and the gates that mu

• assurance-status-report

  Produce an evidence-backed status report for a Quoin/Quire epic, phase, or assurance campaign. Use when asked for progress, percent complete, before/after metrics, completed-ticket inventory, open-work classification, or readiness for the next phase. The workflow is read-only and does not comment on

• gap-analysis

  Audit a repository end to end — spec requirements, the computed Test Matrix, tagged tests, and source code. Planless by default; it reads `quoin matrix` / `quire matrix` to find criteria no test is tagged with, finds code with no owning requirement, and catches stubs and coverage inflation, reportin

• spec-app-review

  Review an application-type spec for completeness against UI rendering requirements and golden-path structure.

• spec-architecture-evaluation

  Evaluate a repository's implemented architecture against its stated boundaries, quality goals, and operating scenarios, producing an evidence-backed SpecReview. Use for architecture reviews; do not use for general test-gap or code-style review.

• spec-correctness

  Turn classified acceptance criteria into runnable property tests. Consumes

• spec-criterion-strength-analysis

  Judge whether each acceptance criterion can actually fail, using Jev (typesafe.ai System One) for calibrated semantic judgment over spec text only. Emits a validated SpecReview recording weakness_kind per AC and adverse_case_coverage per FR.

• spec-dependency-analysis

  Analyze dependencies and separate enablement from feature work.

• spec-ears-analysis

  Analyze requirement statements (FR/NFR/StR) for EARS requirement-grammar conformance and author a SpecReview of the findings.

• spec-evidence-analysis

  Recommend verification methods per obligation from the declared catalog, and flag mismatches with what was authored.

• spec-failure-domain-analysis

  Identify unstated failure modes, identity confusion, purity gaps, and topological edge cases in ISO-style specifications.

• spec-fuzz

  Turn Fuzz-kind obligations into runnable fuzz targets. Consumes `quoin advise --json`, selects the obligations whose verification method carries `evidence_kind: Fuzz`, grounds each one's entry-point symbol in the repository's source, and emits targets in the repo's own harness (cargo-fuzz / atheris

• spec-ideation

  Use for loose, exploratory specification drafting before formal authoring, review, matrix, or planning work.

• spec-integrity-analysis

  Perform quality gate analysis on ISO-style specifications to ensure completeness, consistency, and atomicity.

• spec-matrix

  Read the computed Test Matrix (`quire matrix` / `quoin matrix`) and close its gaps by adding criterion-id trace tags to the tests that assert each untagged criterion. Never hand-writes a matrix.

• spec-object-review

  Audit spec domain objects, cross-references, and entity completeness across single or multi-repo ecosystems.

• spec-review

  Review requirements for quality, consistency, and completeness.

• spec-risk-complexity-analysis

  Identify technical risks and volatility in requirements before tasking.

• spec-scope-boundary-analysis

  Define system boundaries and allocate responsibilities for ISO-style specifications.

• spec-security-analysis

  Analyze specifications and implementations to identify applicable security standards and generate compliance traceability documentation.

• spec-to-plan

  Convert ISO spec requirements (StR, FR, NFR) into a TDD-based project plan with dependency analysis, parallel execution tracks, quality gates, and task decomposition. Selects or starts a plan and writes a frontmatter-typed plan bundle under plan/<Plan-id>-<slug>/ (Plan + Task + index).

• specify

  Create or update spec artifacts from a design or change request. Authors requested requirements and, when explicitly needed, installed assurance artifacts as discrete files using quoin catalog templates and Quire validation.

Similar plugins