メニュー
Multi-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.
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 | agile-v-lifecycle |
| description | Multi-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. |
| license | CC-BY-SA-4.0 |
| metadata | {"version":"1.3","standard":"Agile V","author":"agile-v.org","sections_index":["Cycle ID","Document Versioning","REQ Status Tags","Change Requests","Cycle Triggers","Re-Entry Points","Archival","Impact Analysis"]} |
Multi-cycle lifecycle management for Agile V. Requires agile-v-core loaded first.
C1, C2, ... -- recorded in STATE.md, propagated to all artifact IDs.
| Document | Rule | Example |
|---|---|---|
| REQUIREMENTS.md | Revision header + per-REQ status | <!-- Revision: C2 --> |
| BUILD_MANIFEST.md | ART-XXXX.N suffix | ART-0001.2 |
| TEST_SPEC.md | TC origin cycle | TC-0001 [C1] |
| VALIDATION_SUMMARY.md | One per cycle; prior archived | VALIDATION_SUMMARY_C1.md |
| DECISION_LOG.md | Cycle-tagged entries | [C2] DECISION: ... |
| ATM.md | Partitioned by cycle | See compliance-auditor |
approved [Cn] | modified [Cn] (was/now + CR ref) | new [Cn] | deprecated [Cn] | superseded [Cn]
Append-only in CHANGE_LOG.md. Format: CR-XXXX with Cycle, Affected REQ, Change, Rationale, Impact (ART + TC), Requested by, Approved status. Flow: Req Architect creates -> Logic Gatekeeper validates -> Human approves at Gate 1.
(1) New feature request. (2) Verification failure requiring REQ change. (3) Approved CR invalidating artifacts. (4) Scheduled iteration. All require Human decision.
| Trigger | Re-Entry | Scope |
|---|---|---|
| New feature | Stage 1 | Full pipeline new REQs; regression unchanged |
| REQ change from verification | Stage 1 | CR -> Gate 1 -> full affected; regression others |
| Bug fix (no REQ change) | Stage 3 | Build fixes; re-verify affected only |
| Scheduled | Stage 1 | Review all; full for changes; regression stable |
On Gate 2 acceptance: snapshot living docs -> .agile-v/cycles/CN/ (frozen). Never modify archives. DECISION_LOG and CHANGE_LOG never archived -- append-only timeline.
(1) Req Architect: tag REQs new/modified/deprecated/unchanged. (2) Logic Gatekeeper: re-validate new+modified only. (3) Build Agent: rebuild modified only; carry forward unchanged. (4) Test Designer: delta tests for new/modified; regression baseline for unchanged. (5) Red Team: execute delta + regression separately. (6) Compliance Auditor: cycle-tag ATM; flag unupdated links.
