agile-v-lifecycle
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.
소스 정보
- 저장소
- Agile-V/agile_v_skills
- 최근 소스 활동
- 2026년 9월 14일 04:24
- 감지된 SKILL.md 언어
- 영어
- 스타
- 54
- 포크
- 10
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- 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.5","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"]}
# Instructions
Multi-cycle lifecycle management for Agile V. Requires **agile-v-core** loaded first.
## Cycle ID
`C1`, `C2`, ... -- recorded in STATE.md, propagated to all artifact IDs.
## Document Versioning
| Document | Rule | Example |
|---|---|---|
| `.agile-v/REQUIREMENTS.md` | Revision header + per-REQ lifecycle state | `<!-- Revision: C2 -->` |
| BUILD_MANIFEST.md | ART-XXXX.N suffix | ART-0001.2 |
| TEST_SPEC.md | TC origin cycle | TC-0001 [C1] |
| `.agile-v/VERIFICATION_SUMMARY.md` | One per cycle; prior archived | `VERIFICATION_SUMMARY_C1.md` |
| DECISION_LOG.md | Cycle-tagged entries | [C2] DECISION: ... |
| ATM.md | Partitioned by cycle | See compliance-auditor |
## REQ Lifecycle States
Use canonical states `draft_persisted -> independent_findings -> architect_revisions -> gate_1 -> approved -> baselined`; changes create a new revision in `architect_revisions`, while retirement uses `retired`. Record cycle and change class (`new`, `modified`, `unchanged`) separately. Legacy values require the migration mapping in the canonical lifecycle contract.
## Change Requests
Append-only in `.agile-v/CHANGE_LOG.md`. Format: `CR-XXXX` with Cycle, affected `REQ-XXXX` revision/baseline, change, rationale, ART/TC impact, requester, and approval status. Flow: Requirement Architect creates a new draft revision -> Logic Gatekeeper records findings without editing -> Requirement Architect resolves findings -> Human decides at Gate 1 -> approved revision is captured in a new immutable baseline. A CR is the only mechanism that may change the frozen verification baseline of an active cycle (`docs/agile-v-runtime/07_EVIDENCE_ADMISSION_CONTRACT.md`); Evolve findings from the current cycle propose CRs, they do not apply directly.
## Cycle Triggers
(1) New feature request. (2) Verification failure requiring REQ change. (3) Approved CR invalidating artifacts. (4) Scheduled iteration. All require Human decision.
## Re-Entry Points
| 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 |
## Archival
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.
## Impact Analysis (per agent)
(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.
GitHub에서 보기