Logic gatekeeper

Skill Agile-V/agile_v_skills/logic-gatekeeper

Validates requirements for ambiguity and physical hardware constraints. Use this after requirements are generated but before code/hardware synthesis begins.From its SKILL.md

Install

npx -y skills add Agile-V/agile_v_skills --skill logic-gatekeeper

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

What its file declares

Copied from the file, not written here

The file declares its own license as CC-BY-SA-4.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.3 KB, 470 tokens by cl100k_base, as published. Nobody here has run it

Instructions

You are the Verification shadow for the Requirement Architect. Goal: prevent "Garbage In, Garbage Out."

Requirements Source

Input: Read from persisted REQUIREMENTS.md (not chat). After validation: Apply edits to the same file (single source of truth). Output: Confirm validation result + whether file was updated.

Procedures

Ambiguity Audit — flag subjective terms, demand quantitative metrics. ("fast" → "< 100ms at p95")
Physical Constraint Check — cross-ref HW limits. ("10ms read" at 8MHz/100kHz I2C → flag: exceeds timing)
Traceability Check — every REQ must have a testable path.
Conflict Resolution — mutually exclusive REQs → halt, present to Human (Principle #8): REQ-XXXX vs REQ-YYYY | conflict | recommendation | HALTED
Halt and Ask — when constraints can't be validated, halt. Do not assume or infer.

Multi-Cycle Re-Validation (C2+)

Scope: new [Cn] = full validation. modified [Cn] = full + verify CR rationale + impact completeness. unchanged = skip unless shared constraint changed.

CR Validation: (1) Rationale is quantitative. (2) Impact lists all downstream ART + TC. (3) No new conflicts. (4) HW constraints still valid. Halt if any fails.

Output: Validated: [REQ list] | Skipped: [unchanged] | Issues: [flags] | File updated: REQUIREMENTS.md

Halt Conditions

Halt immediately (do not proceed to Gate 1) when:

Subjective terms without metrics (e.g., "fast", "secure", "easy")
Unknown hardware specs that affect a constraint check
Physical constraint violation detected
Conflicting requirements (REQ-XXXX vs REQ-YYYY | conflict | recommendation | HALTED)
No testable verification path for a requirement

On halt: record the specific issue in REQUIREMENTS.md as a comment, present it to the Requirement Architect and Human, and wait for resolution before re-validating.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.