logic-gatekeeper

Validate hardware requirements for ambiguity, feasibility, and traceability before synthesis.

50|9|Updated Feb 5, 2026

Search Tags:#requirements #validation #verification #ambiguity #traceability #multi-cycle #hardware-constraints

Ready to run

npx skills add https://github.com/Agile-V/agile_v_skills --skill logic-gatekeeper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: logic-gatekeeper
Source: https://github.com/Agile-V/agile_v_skills/tree/main/logic-gatekeeper
Command: npx skills add https://github.com/Agile-V/agile_v_skills --skill logic-gatekeeper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates requirements to remove ambiguity and ensure hardware timing and physical constraints are feasible before synthesis.

Core Features & Use Cases

Ambiguity Audit: flags subjective terms, demands quantitative metrics, and ensures testable acceptance criteria.
Physical Constraint Check: cross-references hardware specs and verifies timing and resource limits against available hardware.
Traceability Check: ensures every requirement has a testable path and traceable verification plan.
Conflict Resolution: detects mutually exclusive requirements and halts with human review when conflicts arise.
Multi-Cycle Re-Validation: supports full validation for new, modified, or unchanged requirements with rationale and impact assessment.

Quick Start

Provide REQUIREMENTS.md and let the skill perform ambiguity audit, hardware constraint checks, and traceability validation.

Frequently Asked Questions about logic-gatekeeper

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

FAQPage Schema

How do I validate hardware requirements for ambiguity before synthesis?▼

To validate hardware requirements for ambiguity before synthesis, you provide REQUIREMENTS.md to trigger an audit that flags subjective terms, demands quantitative metrics, and ensures testable acceptance criteria.

What is requirements traceability and how does it ensure hardware feasibility?▼

Requirements traceability ensures hardware feasibility by cross-referencing hardware specs and verifying timing and physical constraints, mapping every requirement to a testable path and traceable verification plan.

How do I detect mutually exclusive requirements and halt for conflict resolution?▼

To detect mutually exclusive requirements and halt for conflict resolution, the validation workflow identifies mutually exclusive constraints during the audit and pauses execution to demand human review.

Can I re-validate modified requirements across multiple agile engineering cycles?▼

Yes, you can re-validate modified requirements across multiple agile engineering cycles using multi-cycle re-validation, which assesses rationale and impact for new, modified, or unchanged requirements.

What is the best way to check physical constraints against available hardware specs?▼

The best way to check physical constraints against available hardware specs is through a physical constraint check that cross-references hardware specs and verifies timing and resource limits against available hardware.

Why does my requirements validation halt on subjective terms?▼

Requirements validation halts on subjective terms because the ambiguity audit flags them, demanding quantitative metrics and testable acceptance criteria to ensure clear hardware requirements before synthesis.