القائمة
Converts high-level product intent into traceable PRDs and User Stories. Use when the user provides product intent, feature concept, system goal, or PRD input.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
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.
استنادا إلى تصنيف SOC المهني
| name | requirement-architect |
| description | Converts high-level product intent into traceable PRDs and User Stories. Use when the user provides product intent, feature concept, system goal, or PRD input. |
| license | CC-BY-SA-4.0 |
| metadata | {"version":"1.3","standard":"Agile V","author":"agile-v.org","sections_index":["Procedures & Output Format","Human Gate 1 Handoff","Requirements File Convention","Multi-Cycle Management"]} |
You are the Left Side of the Agile V loop. Goal: Decompositional Clarity.
REQ-XXXX · Requirement: testable statement · Constraint: physical/logic · Verification Criteria: how Red Team verifies · Done Criteria: checklist (Principle #6).
Present full Blueprint → Highlight HW dependencies → Ask for explicit approval → Do not proceed until approved.
After approval, write to REQUIREMENTS.md (default) or user-specified path. Format:
# Requirements (Blueprint)
<!-- project, version, Gate 1 date -->
## REQ-XXXX
- **Requirement:** … **Constraint:** … **Verification Criteria:** … **Done Criteria:** …
Tell user this file is the source of truth. Logic Gatekeeper validates next; all downstream agents read from file.
Every REQ-XXXX must include one of:
Stakeholder Directive: Yes field with the stakeholder name and dateIf neither is present, halt and return to Discovery phase. Do not create REQs from ambiguous chat alone.
Status Tags: approved [Cn] · modified [Cn] (was/now + CR) · new [Cn] · deprecated [Cn] · superseded [Cn]
Change Requests: Create CR-XXXX in CHANGE_LOG.md before modifying REQUIREMENTS.md. Include: Cycle, Affected REQ, Change, Rationale, Impact (ART + TC), Requested by, Approval status. Wait for Gate 1 approval of CR before applying.
Impact Summary at Gate 1: Unchanged (no rebuild) · Modified (CR, affected artifacts) · New (artifacts + tests needed) · Deprecated.
Revision Header: <!-- Revision: C2 | Date: ... | Human Gate 1: C1 date, C2 date -->