graph-controls-designer

Design falsifiable acceptance controls with observable methods for graphs and test harnesses.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/JaviMontano/claude-plugins --skill graph-controls-designer-javimontano
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: graph-controls-designer
Source: https://github.com/JaviMontano/claude-plugins/tree/main/plugins/claude-native-toolkit/skills/graph-controls-designer
Command: npx skills add https://github.com/JaviMontano/claude-plugins --skill graph-controls-designer-javimontano

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Acceptance criteria often degrade into decorative green checks: scores without measurement methods, gates that never proved they can fail, and validators that fire on the desired state until they become ignored noise. This Skill designs controls that are observable, falsifiable, and satisfiable from birth. ## Core Features & Use Cases - METHOD and signal per criterion: Every control declares an observable procedure and a countable signal, with honest proxies (e.g., "acronyms used before definition: 3") instead of invented scores like "Clarity: 8/10". - Falsification testing: Each control's falsification_test is exercised before "Passed" means anything; until then the state is "Not executed", never a decorative green. - Birth satisfiability: New controls must pass the current corpus, be a regression against a recorded baseline, or carry an explicit debt budget that only decreases. - Deterministic validation: The control set is validated with validate_graph_spec.py --controls from graph-spec-compiler until zero findings. - Use Case: When defining acceptance gates for a graph pipeline, convert vague quality judgments into measurable controls, prove each gate can fail, and validate the whole set with the checker. ## Quick Start Ask the assistant to design falsifiable acceptance controls for your graph or harness, with an observable method and failure test for each criterion and no invented scores.

Frequently Asked Questions about graph-controls-designer

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

FAQPage Schema
How do I design acceptance criteria that can actually fail?▼

Give each criterion an observable METHOD and a countable signal, then exercise a falsification test by inducing the failure and confirming the control catches it. Until that test runs, the control's state is 'Not executed', never 'Passed'.

How to replace subjective quality scores with measurable metrics?▼

Convert judgments like 'Clarity: 8/10' into honest proxies that report what they measure, such as 'acronyms used before their definition: 3'. Mark proxy=true and name exactly what the proxy counts.

What is a falsification test for a quality gate?▼

A falsification test deliberately induces the failure condition and observes that the control fails. A gate that never demonstrated it can fail provides no information, so its passing state is meaningless until the test is exercised.

When should I not use graph-controls-designer?▼

Do not use it for software testing strategy such as unit and integration test pyramids, which belongs to testing-strategy, or for BDD Gherkin scenarios, which belongs to bdd-full-spectrum. It only designs falsifiable controls for graphs and harnesses.

Why does a new control that fails on existing content get ignored?▼

A control born unsatisfiable fires on the desired state, accumulates warnings, becomes noise, and is eventually deleted. It must instead pass the current corpus, be a regression against a recorded baseline, or carry a debt budget that only decreases.