القائمة
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.
التثبيت باستخدام 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.
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.
Validates requirements for ambiguity and physical hardware constraints. Use this after requirements are generated but before code/hardware synthesis begins.
| name | agile-v-pipeline |
| description | 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. |
| license | CC-BY-SA-4.0 |
| metadata | {"version":"1.4","standard":"Agile V","author":"agile-v.org","sections_index":["Pipeline","Handoffs","Wave Execution","Checkpoint Types"],"adapted_from":[{"name":"Get Shit Done (GSD)","url":"https://github.com/gsd-build/get-shit-done","license":"MIT","copyright":"Copyright (c) 2025 Lex Christopherson","sections":"Orchestration Pipeline"}]} |
Orchestration pipeline for Agile V. Requires agile-v-core loaded first.
Stage 1: Requirements -> Stage 2: Validation -> [Human Gate 1] -> Stage 3: Synthesis (Build Agent || Test Designer) -> Stage 4: Verification -> [Human Gate 2] -> Stage 5: Acceptance
Compliance Auditor observes all stages.
Gate 2 prereqs (Phase 1): EVAL_RESULTS.md + VALIDATION_SUMMARY.md EvalGate line. Gate pause (Phase 2): append CHECKPOINTS.md (PENDING + resume_token); resume only with matching APPROVALS.md entry (see agile-v-core).
If a stage fails (e.g., Logic Gatekeeper rejects requirements, Red Team finds CRITICAL issues), the pipeline stops at that stage. Do not proceed to the next stage.
| Failure | Action |
|---|---|
| Gate 1 rejected | Return to Stage 1; Req Architect updates REQUIREMENTS.md |
| Build Agent HALT | Human resolves blocker; Build Agent resumes; do not skip to Stage 4 |
| Red Team FAIL | Return to Stage 3; Builder addresses findings; re-verify affected only |
| Gate 2 blocked | Do not proceed to Stage 5; resolve EVAL gate or get WAIVED approval |
Never advance to Stage 5 with open CRITICAL or MAJOR findings.
Dependency analysis -> Wave assignment (no-deps = Wave 1) -> Parallel within waves (fresh context each) -> Sequential across waves -> Prefer vertical slices (feature > layer).
| Type | Action |
|---|---|
| Auto | Proceed |
| Human-Verify | Confirm output |
| Human-Decision | Choose alternative |
| Human-Action | Physical/external step |
All except Auto require Human Gate protocol.