agentsclimarketplace

Spec review

Skill agent-ix/quoin/skills/spec-review

Review requirements for quality, consistency, and completeness.From its SKILL.md

Install
npx -y skills add agent-ix/quoin --skill spec-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 20 stars20 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.1 KB, as published. Nobody here has run it

Review Requirements

Use this skill to validate requirements artefacts before implementation.

Checklist

See references/checklist.md for the detailed quality gates.

Choose the review set

Before reviewing, present these options to the user and let them choose:

  • base — the Checklist only: ID formats, US/FR/TC quality, and the six coverage rules. No analysis skills.
  • all — base plus all seven analyses below.
  • subset — base plus the analyses the user picks from the seven below.

The seven analyses:

AnalysisSkill
failure-domainspec-failure-domain-analysis
integrityspec-integrity-analysis
dependencyspec-dependency-analysis
evidencespec-evidence-analysis
risk-complexityspec-risk-complexity-analysis
scope-boundaryspec-scope-boundary-analysis
ears-conformancespec-ears-analysis

Process

  1. Automated Checks (always — part of base):
    • Validate ID formats (US/FR/TC/AC/CON).
    • Detect duplicates or gaps.
    • Validation link integrity.
  2. Base Review (always):
    • Read each artifact.
    • Verify against the Checklist.
    • Verify Test Coverage (6 Rules).
  3. Selected Analyses:
    • Run each analysis the user chose. Prefer running them in parallel.
    • Fetch the template from quoin once with quoin write --types SpecReview — use its skeleton + schema as the contract (do not invent the format).
    • Write one SpecReview document per analysis to spec/reviews/<analysis>.md (plus spec/reviews/base.md for the base checklist). Findings go in a validated ## Findings table (| ID | Severity | Summary | Refs |, FND-NNN ids, Severity ∈ low/medium/high).
  4. Validate + record:
    • Run quire validate --scope <repo> "spec/**/*.md" and fix any errors.

--scope is the repository root, and must be passed explicitly. Since quire-cli v0.16.0 (quire-rs CR-045) the command derives two roots from it and never interchanges them: spec documents are read from <repo>/spec only, trace tags from the source tree at <repo> excluding spec/. A repo with no spec/ exits with a diagnostic naming the missing document root rather than scanning the whole tree, and a matrix outside spec/ (a fixture, a plan/ copy) mints nothing. A relative glob resolves under --scope only in scoped mode (no --module); with --module it resolves against the process working directory, and an omitted --scope defaults to . — so a run launched from a parent directory validates the wrong tree and exits 0 for whatever it matched. Check quire --version ≥ 0.16.0 before relying on any of this; ≤ 0.15.0 has the pre-split traversal semantics.

-   The docs sync into filament-core as `SpecReview` artifacts; do not proceed to
    implementation until reviewed.

Enforced runs (workflow mode)

quoin review drives this through ix-flow, which records the chosen set and hard-blocks acceptance until every selected analysis has produced a validated SpecReview doc (the selected_analyses_covered gate). Use it when you want the choice enforced rather than trusted to discipline. The per-analysis SpecReview structure + the findings table are defined in the workflow skill (workflow-assets/skills/review/SKILL.md).

Common Issues

  • Vague Criteria: "Fast", "User-friendly". -> Make measurable.
  • Missing Errors: Only happy path. -> Add error modes.
  • No Coverage: AC without TC. -> Add tests.
  • Inconsistent IDs: US-1 instead of US-001. -> Fix formatting.

Output contract

The SpecReview this skill emits carries analysis: base — the generic review value — this skill runs the analysis lenses and writes one document per lens, so it is the default rather than a lens of its own.

Stated here because nothing checked it (quoin#202): a skill and its declared output were unlinked, so drift between them was invisible until a document failed validation in an unrelated session.

Keep looking

Skills are one crate of 611,919. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.