hs:critique

Fans independent review lenses at an artifact and consolidates findings into one ranked verdict.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/Dozyboy/VSF --skill hs-critique-dozyboy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hs:critique
Source: https://github.com/Dozyboy/VSF/tree/main/Day2_VSF/Demo1/harness/plugins/hs/skills/critique
Command: npx skills add https://github.com/Dozyboy/VSF --skill hs-critique-dozyboy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? A single reviewer or single-pass critique often misses failure modes because one perspective anchors the analysis. This Skill challenges a plan, decision, design, or code diff with several independent lenses that never see each other's reasoning, then merges their findings into one deduplicated, severity-ranked verdict. ## Core Features & Use Cases - Multi-lens fan-out: Runs independent read-only lenses (red-teamer, code-reviewer, independent-revalidator, brainstormer) chosen per artifact type from a config file, each returning a normalized JSON finding contract with anchor, severity, and fix. - Consolidated verdict: A consolidator dedups cross-lens findings, ranks by severity, attaches repeat-offense metadata, and proposes a PASS, PASS_WITH_RISK, or BLOCKED verdict written to a markdown report. - Gate and loop modes: Optional --gate writes a machine-readable critique-consensus.json verdict artifact for downstream stage gating, and --loop runs a bounded critique-refute cycle for contested verdicts. - Use Case: Before committing to an architecture decision, run the critique on the design document so adversarial, validation, and product lenses independently attack it, then review one ranked report of blockers and DEC-worthy items. ## Quick Start Ask the AI to critique the plan at plans/my-design.md using the critique skill and report the consolidated verdict.

Frequently Asked Questions about hs:critique

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

FAQPage Schema
How do I run a multi-perspective critique on a design document?▼

Invoke the critique skill with the artifact path, for example the design doc or plan file. It classifies the artifact type, picks a lens set from critique.yaml, fans out independent lenses, and writes a consolidated report to plans/reports/.

What is the difference between advisory mode and gate mode in a critique?▼

Advisory mode is the default: it produces a report and never blocks anything. Gate mode additionally writes a critique-consensus.json verdict artifact (PASS, PASS_WITH_RISK, or BLOCKED) that a downstream stage policy can require before proceeding.

When should I use the --loop refute cycle?▼

Use --loop when the consolidated verdict is contested, such as a blocker the author could plausibly rebut or a suspected finding carrying the verdict. It runs bounded critique-refute rounds until the surviving blocker set converges or max_rounds is reached.

Can I override which review lenses run on an artifact?▼

Yes, pass --lenses a,b,c to override the lens set that critique.yaml defines for the artifact type. This is useful for unusual artifacts or when a specific set of perspectives is wanted.

Does the critique skill modify code or plans it reviews?▼

No. All lenses and the consolidator are read-only advisory agents that only report findings. The skill controller writes only the critique report and, in gate mode, the verdict artifact; fixes are never implemented.