logic-gatekeeper
/logic-gatekeeper
Sprawdza wymagania pod kątem niejednoznaczności i ograniczeń sprzętowych, zanim zacznie się kod albo synteza sprzętu.
- Autor
- Agile-V ↗
- Repozytorium
- agile_v_skills ↗
- Licencja
- CC-BY-SA-4.0
- Ostatnia zmiana repozytorium
- 06.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 06.10.2026, bez odwołań do wycofanych modeli i API.
CC-BY-SA-4.0, otwarta.
Co robi i kiedy
Sprawdza wymagania pod kątem niejednoznaczności i ograniczeń sprzętowych, zanim zacznie się kod albo synteza sprzętu.
Oryginalny opis (EN)
Validates requirements for ambiguity and physical hardware constraints. Use this after requirements are generated but before code/hardware synthesis begins.
Jak działa
- Requirements Source
- Procedures
- Multi-Cycle Re-Validation (C2+)
- Halt Conditions
- Human-Origin Evidence Preservation
- Qualification Boundary
Podgląd 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
metadata:
version: "1.7"
standard: "Agile V"
author: agile-v.org
sections_index:
- Requirements Source & Procedures
- Multi-Cycle Re-Validation
- Halt Conditions
- Human-Origin Evidence Preservation
---
# Instructions
You are the **Verification shadow** for the Requirement Architect. Goal: prevent "Garbage In, Garbage Out."
## Requirements Source
**Input:** Read `draft_persisted` requirements from `REQUIREMENTS.md` (not chat). **Output:** append independent findings with IDs, evidence, and recommendations; never edit requirements, revisions, approvals, or a baseline. The Requirement Architect performs all revisions.
## 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:** lifecycle state remains canonical; cycle change class is separate. `new` = full review; `modified` = full review plus CR rationale/impact completeness; `unchanged` = skip unless a 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:** `Findings: [FND IDs] | Reviewed: [REQ list] | Skipped: [unchanged] | Baseline edited: no`
## 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 a `FND-XXXX` finding in the independent findings record, present it to the Requirement Architect and Human, and wait for an architect revision before re-validating. Do not edit a baseline.
## Human-Origin Evidence Preservation
Never rewrite, soften, or "clean up" a human's blind precommit, concern, or `unable_to_assess` statement recorded for `agile-v-human-oversight`. If a human concern exposes a requirement problem, route it to a change request (do not silently fold it into a test expectation). Preserve discrepancies between expected, predicted, and actual — do not force early consensus.
## Qualification Boundary
Logic Gatekeeper performs independent requirement-quality review. It does not complete DQ because DQ evaluates a proposed design.
Add findings (`FND-XXXX`) when any of these are present:
| Finding Type | Trigger |
|--------------|---------|
| Missing qualification path | Regulated/high-assurance intent without an identified DQ/IQ/OQ/PQ evidence route |
| Intended-use ambiguity | Approved intended use is undefined, vague, or contradictory |
| Untestable critical functions | Functions critical to quality, safety, or data integrity lack a testable verification path |
| Missing representative conditions | No representative conditions specified for later PQ/validation |
Wersje
W bazie nie ma innych skilli o nazwie logic-gatekeeper.
Migawka bazy z 13.11.2026 · wersja paczki 1fd7776bf0a6 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95writing-plans
Tworzy plan wieloetapowego zadania na podstawie specyfikacji, zanim zacznie się zmieniać kod. - 90requirements-review
Przegląda wymagania przed wdrożeniem, zamienia niejasne intencje w decyzje, ograniczenia, ryzyka i pierwszy krok. - 100prd-gatekeeper
Waliduje PRD pod kątem gotowości inżynierskiej: pięć bramek jakości, od ukrytych decyzji produktowych po ocenę ryzyka. - 100sr-writing-plans
Pomaga spisać plan wieloetapowego zadania na podstawie specyfikacji, zanim zacznie się zmieniać kod. - 100define
Definiuje wymagania nowej funkcji, zgłoszenia błędu lub zlecenia pracy, zanim zacznie się implementacja. - 10010-requirements-metrics
Mierzy jakość wymagań i egzekwuje ilościowe bramki dla niejednoznaczności, kompletności, śledzenia, zmienności i testowalności.