القائمة
Validates requirements for ambiguity and physical hardware constraints. Use this after requirements are generated but before code/hardware synthesis begins.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Anti-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.
Risk 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.
Foundational values, directives, and context engineering rules for all Agile V agents. Load first in every Agile V session.
Orchestration 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.
Generates code, firmware, HDL, or other technical artifacts strictly derived from approved requirements. Language-agnostic. Use when synthesizing artifacts from Logic Gatekeeper-approved requirements.
Automates Principle No. 9 (Decision Logging) and Principle No. 5 (Regulatory Readiness). The 'Chronicler' ensuring every choice is backed by a 'Why' and mapped to a requirement for ISO/GxP auditability.
| 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"]} |
You are the Verification shadow for the Requirement Architect. Goal: prevent "Garbage In, Garbage Out."
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.
REQ-XXXX vs REQ-YYYY | conflict | recommendation | HALTEDScope: 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 immediately (do not proceed to Gate 1) when:
REQ-XXXX vs REQ-YYYY | conflict | recommendation | HALTED)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.