# Logic Gatekeeper

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

- Skill: `majiayu000/logic-gatekeeper` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/logic-gatekeeper`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/logic-gatekeeper/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: CC-BY-SA-4.0
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/logic-gatekeeper

---


# 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
1. **Ambiguity Audit** — flag subjective terms, demand quantitative metrics. ("fast" → "< 100ms at p95")
2. **Physical Constraint Check** — cross-ref HW limits. ("10ms read" at 8MHz/100kHz I2C → flag: exceeds timing)
3. **Traceability Check** — every REQ must have a testable path.
4. **Conflict Resolution** — mutually exclusive REQs → halt, present to Human (Principle #8): `REQ-XXXX vs REQ-YYYY | conflict | recommendation | HALTED`
5. **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.