agile-v/logic-gatekeeper
logic-gatekeeper/SKILL.md
Validates requirements for ambiguity and physical hardware constraints. Use this after requirements are generated but before code/hardware synthesis begins.
$ install --global
skillsauthnpx skillsauth add agile-v/agile_v_skills logic-gatekeeperInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 30, 2026, 5:22 PM56.5s1 file scanned
SKILL.md
- name:
- logic-gatekeeper
- description:
- Validates requirements for ambiguity and physical hardware constraints. Use this after requirements are generated but before code/hardware synthesis begins.
- license:
- CC-BY-SA-4.0
- version:
- 1.3
- standard:
- Agile V
- author:
- agile-v.org
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
Subjective terms without metrics · Unknown HW specs · Physical constraint violation · REQ conflict · No testable path.
Related Skills
agile-v/skills/system-understanding-agent
development
VerifiedTrustedCommunity
# Skill: system-understanding-agent ## Purpose Use this skill when Agile V is applied to an existing codebase, documentation set, or knowledge base. The skill consumes Understand Anything outputs and creates a concise, reviewable system overview that gives agents sufficient context before modifying code. This is **Gate 0** of the integrated Agile V lifecycle. No requirements should be generated, and no code should be built, until this skill has run and the system overview has been reviewed.
39SKILL.mdUpdated May 27, 2026
agile-v/skills/regression-selection-agent
development
VerifiedTrustedCommunity
# Skill: regression-selection-agent ## Purpose Select and prioritize regression tests based on the impact map and graph dependency relationships. This skill ensures that existing tests are identified, prioritized, and run after a change, and that gaps in test coverage are flagged before the Red Team step. --- ## Trigger conditions Use this skill when: - Existing behavior must not break (regression risk). - An impact map is available. - The change affects shared modules, services, or APIs.
39SKILL.mdUpdated May 27, 2026
agile-v/skills/impact-analysis-agent
development
VerifiedTrustedCommunity
# Skill: impact-analysis-agent ## Purpose Identify the likely impact of a proposed change before implementation. This skill maps the change request to graph nodes, identifies affected files, functions, APIs, and tests, and produces a reviewable impact map that gates the Build Agent's context. --- ## Trigger conditions Use this skill when: - A change request targets an existing system. - The change could affect multiple files or modules. - Regression risk exists (the change touches shared c
39SKILL.mdUpdated May 27, 2026
agile-v/skills/graph-traceability-agent
testing
VerifiedTrustedCommunity
# Skill: graph-traceability-agent ## Purpose Create traceability from Agile V requirements to Understand Anything graph nodes, changed files, and tests. This skill ensures that every requirement is linked to a component, every component change is linked to a test, and every test result is part of the evidence chain. --- ## Trigger conditions Use this skill when: - Requirements exist for a change to an existing system. - A knowledge graph is available. - The evidence bundle needs component-
39SKILL.mdUpdated May 27, 2026