skills.rest
Agile-V
Agile-VOFFICIAL
Explore all skills by this author ā†’
Websiteš•@AgileVFrameworkGitHub

agile-v-lifecycle

Coordinate multi-cycle iterations and artifact versioning across Agile V programs.

50|9|Updated Feb 5, 2026
Search Tags:#versioning#audit#governance#traceability#lifecycle#cycle-management
One-click install
npx skills add https://github.com/Agile-V/agile_v_skills --skill agile-v-lifecycle
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: agile-v-lifecycle
Source: https://github.com/Agile-V/agile_v_skills/tree/main/agile-v-lifecycle
Command: npx skills add https://github.com/Agile-V/agile_v_skills --skill agile-v-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates multi-cycle iteration management and artifact versioning to ensure traceability, compliance, and smooth progression through Agile V cycles.

Core Features & Use Cases

  • Cross-cycle traceability and lifecycle governance across REQ, ART, TC, and ATM artifacts.
  • Document versioning guidance and automated archiving for cycle transitions.
  • Support for re-entry points and processing of change requests.
  • Audit-ready outputs and cycle tagging to enable validation and reviews.

Quick Start

Load agile-v-core, start a new cycle (C2+), and begin tracking requirements, builds, tests, and validation as you archive completed cycles.

Frequently Asked Questions about agile-v-lifecycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage artifact versioning across multiple Agile V cycles?ā–¼

Artifact versioning across Agile V cycles is managed by applying tagging and archival rules to REQUIREMENTS.md, BUILD_MANIFEST.md, TEST_SPEC.md, VALIDATION_SUMMARY.md, and DECISION_LOG.md. This preserves cross-cycle traceability during new cycle initiation and change-request processing.

What is cross-cycle traceability and when do I need it during lifecycle governance?ā–¼

Cross-cycle traceability links requirements, build artifacts, test cases, and validation outputs across sequential iterations. You need it during C2+ cycle initiation and change-request processing to maintain audit-ready compliance and smooth progression.

How do I process change requests without breaking traceability in a multi-cycle iteration?ā–¼

Change requests are processed using defined re-entry points that update artifact versions while maintaining cross-cycle traceability. The lifecycle governance applies cycle-tagging to ensure validation records remain continuous and audit-ready.

Do I need to start at cycle one to use lifecycle governance, or can I begin tracking at C2+?ā–¼

You can begin tracking at C2+ because the lifecycle governance applies during the initiation of new cycles following the initial one. Loading the core framework and starting a new cycle enables immediate requirements and build tracking.

Which documents need cycle-tagging for audit-ready validation reviews?ā–¼

Cycle-tagging is required for REQUIREMENTS.md, BUILD_MANIFEST.md, TEST_SPEC.md, VALIDATION_SUMMARY.md, and DECISION_LOG.md. Applying versioning rules and automated archiving to these files generates audit-ready outputs for validation reviews.

Related Skills

Explore More Product & Management Skillsā†’
Agile-VAgile-V
50

build-agent-dart

Automate Dart/Flutter build workflows with domain-specific conventions and platform compliance.

Official
Intermediate
Agile-VAgile-V
50

red-team-verifier

Execute independent tests against Build Agent artifacts to validate requirements compliance.

Official
Advanced
accelerate-dataaccelerate-data
3

test-invariants

Enforce stable invariants across test-generation and test-review workflows for migrated dbt unit tests.

Official
Intermediate
Agile-VAgile-V
50

agile-v-core

Automates foundational governance and context engineering for Agile V agents.

Official
Intermediate