OpenParable
Skip to content
← Back to skills

Agile V Lifecycle

Productivity
agile-v-lifecycle

Agile V Lifecycle is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/workflow/agile-v-lifecycle/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/agile-v-lifecycle, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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

DocumentRuleExample
REQUIREMENTS.mdRevision header + per-REQ status<!-- Revision: C2 -->
BUILD_MANIFEST.mdART-XXXX.N suffixART-0001.2
TEST_SPEC.mdTC origin cycleTC-0001 [C1]
VALIDATION_SUMMARY.mdOne per cycle; prior archivedVALIDATION_SUMMARY_C1.md
DECISION_LOG.mdCycle-tagged entries[C2] DECISION: ...
ATM.mdPartitioned by cycleSee compliance-auditor

REQ Status Tags

approved [Cn] | modified [Cn] (was/now + CR ref) | new [Cn] | deprecated [Cn] | superseded [Cn]

Change Requests

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.

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

TriggerRe-EntryScope
New featureStage 1Full pipeline new REQs; regression unchanged
REQ change from verificationStage 1CR -> Gate 1 -> full affected; regression others
Bug fix (no REQ change)Stage 3Build fixes; re-verify affected only
ScheduledStage 1Review 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.