faffter-dark-spec-review

Runs independent adversarial review lenses against a spec and aggregates refutations into a verdict.

3|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/shftwst/faff --skill faffter-dark-spec-review-shftwst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: faffter-dark-spec-review
Source: https://github.com/shftwst/faff/tree/main/plugin/skills/faffter-dark-spec-review
Command: npx skills add https://github.com/shftwst/faff --skill faffter-dark-spec-review-shftwst

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? A single-pass spec review inherits one model's correlated blind spots, which is unsafe in unattended (L4) delivery pipelines. This Skill runs each enabled review lens as an independent adversarial pass prompted to break the spec, then deterministically aggregates the refutations into one founded verdict. ## Core Features & Use Cases - Independent lens refutation: Runs architectural, infosec, methodology, and QA lenses as separate model calls, each with its own refutation prompt, dispatched concurrently via a fan-out helper. - Deterministic aggregation: Maps per-lens outcomes onto the spec-review-verdict contract using a majority/severity gate (critical veto, strict-majority reject, minority revise, clean approve), with fail-safe handling of unavailable lenses. - Ratified-scope deference: Design lenses defer objections that merely restate settled non-goals, goals, or thread resolutions as cited observations, while never deferring a critical finding. - Use Case: In an unattended delivery loop, after a spec is produced and before build admission, this occupant challenges the spec from four independent angles and emits a verdict the orchestrator routes on. ## Quick Start Configure the L4 recipe with slots.spec_review set to faffter-dark-spec-review so the prep pipeline invokes it at the spec-to-build seam.

Frequently Asked Questions about faffter-dark-spec-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does adversarial spec review work in an unattended pipeline?▼

Each enabled lens (architectural, infosec, methodology, QA) runs as a separate model invocation prompted to break the spec. The refutations are parsed deterministically and aggregated by a majority/severity gate into one verdict: approve, revise, reject-approach, needs-human, or unavailable.

What review lenses does the spec reviewer support?▼

Four lenses: architectural (soundness, fit, coupling), infosec (authn/authz, secrets, input surface, fail-open paths), methodology (slice sizing, sequencing, worth), and QA (born-verifiability, scenario coverage, oracle problems). The enabled subset is resolved upstream per issue.

What happens when a review backend is down or misconfigured?▼

A down refuter never silently approves. A config fault floors the verdict to needs-human, while a swing-capable infrastructure outage yields an unavailable verdict that the orchestrator can hold and retry.

How does the reviewer avoid re-litigating settled decisions?▼

When a ratified-scope block is supplied, design lenses defer objections that only restate settled non-goals, goals, or thread resolutions as cited observations. A critical finding is never deferred by any lens.

Can the lenses be collapsed into one review pass to save tokens?▼

No. Collapsing the lenses into one pass re-correlates the blind spots through a single context and reduces the reviewer to the single-pass default. Independence of the per-lens passes is the mechanism that decorrelates them.