quoin

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, close, or modify tickets or repositories.

Verify a targeted plan is complete and validated — every task done, the Test Matrix backed by real tracking tags in tests, and code fully traced to spec (flagging underspecified code with no owning requirement). Optional semantic review checks that intent↔test↔code actually agree. Emits a quire-validated SpecReview artifact to reviews/YY-MM-DD-<slug>.md.

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

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.

Turn classified acceptance criteria into runnable property tests. Consumes `quire properties --json` per-criterion records, grounds each criterion's domain, precondition and oracle in the spec and the code, and emits property tests in the repo's own harness (proptest / fast-check / hypothesis) keyed on `row_id`. Emits a validated SpecReview recording every criterion it could not ground and why.

Analyze dependencies and separate enablement from feature work.

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

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

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

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 / fast-check) keyed on the obligation id. Writes nothing where the tooling is absent or the entry point cannot be grounded — a finding instead. Emits a validated SpecReview recording every obligation it could not serve.

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

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

Build and maintain the requirements Test Matrix ensuring 100% coverage.

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

Review requirements for quality, consistency, and completeness.

Identify technical risks and volatility in requirements before tasking.

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

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

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 + log).

Create or update spec artifacts from a design or change request. Orchestrates authoring each requested requirement type (StR/US/FR/NFR/IT) as a discrete file using quoin catalog templates and Quire validation.