Agent skill
logic-gatekeeper
Validates requirements for ambiguity and physical hardware constraints. Use this after requirements are generated but before code/hardware synthesis begins.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/logic-gatekeeper
Metadata
Additional technical details for this skill
- author
- agile-v.org
- version
- 1.3
- standard
- Agile V
- sections index
-
[ "Requirements Source & Procedures", "Multi-Cycle Re-Validation", "Halt Conditions" ]
SKILL.md
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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?