logic-gatekeeper

$npx mdskill add Agile-V/agile_v_skills/logic-gatekeeper

Validates requirements for ambiguity and hardware constraints before synthesis.

  • Prevents garbage-in by auditing requirements for ambiguity and physical limits.
  • Reads from and writes to REQUIREMENTS.md as the single source of truth.
  • Flags subjective terms, checks hardware timing, and detects conflicts.
  • Halts on unresolved conflicts and presents recommendations to the human.

SKILL.md

.github/skills/logic-gatekeeperView on GitHub ↗
---
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
metadata:
  version: "1.3"
  standard: "Agile V"
  author: agile-v.org
  sections_index:
    - Requirements Source & Procedures
    - Multi-Cycle Re-Validation
    - Halt Conditions
---

# 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

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.

More from Agile-V/agile_v_skills

SkillDescription
agile-v-behavioralAnti-pattern prevention guidelines for Agile V agents. Prevents common LLM coding mistakes while maintaining Agile V traceability. Use when implementing requirements to avoid overcomplication, silent assumptions, scope creep, and verification failures.
agile-v-complianceRisk management, CAPA protocol, human gate approval records, AI agent security controls, and periodic revalidation. Load when running gates, handling CAPAs, or auditing compliance and security posture.
agile-v-control-matrixDefines and checks the Agile-V control matrix for agentic tasks, skills, model use, tools, logs, rights, Human Gates, tests, costs, rollback, and owners. Load when creating, reviewing, or enforcing `.agile-v/CONTROL_MATRIX.yaml` or runtime governance for agentic execution.
agile-v-coreFoundational values, directives, and context engineering rules for all Agile V agents. Load first in every Agile V session.
agile-v-lifecycleMulti-cycle iteration management, document versioning, change requests, re-entry points, archival, and impact analysis. Load when starting a new cycle (C2+), processing change requests, or managing cross-cycle traceability.
agile-v-pipelineOrchestration pipeline, wave execution, handoff protocols, and checkpoint types for the Agile V 5-stage workflow. Load when orchestrating multi-agent pipelines or managing stage transitions.
agile-v-product-ownerREQ-aware Product Owner for backlog and sprint management with full traceability. Use for sprint planning, backlog prioritization, or converting REQs to INVEST stories.
agile-v-quality-gatesQuality validation gates for Agile V agents. Adds interface validation, test quality checks, data type awareness, and time allocation guidance to prevent common failure patterns identified in comprehensive testing.
build-agentGenerates code, firmware, HDL, or other technical artifacts strictly derived from approved requirements. Language-agnostic. Use when synthesizing artifacts from Logic Gatekeeper-approved requirements.
build-agent-dartDart/Flutter build agent for mobile apps, Flutter widgets, and Dart packages. Extends build-agent with Dart-specific conventions. Use when building Flutter apps, Dart packages, or mobile (iOS/Android) features.