document-lifecycle

Orchestrate document lifecycle with global IDs and terminal closures.

284|47|Updated Dec 13, 2025

Search Tags:#workflow #archiving #audit-trail #terminal-status #document-lifecycle #id-management

Ready to run

npx skills add https://github.com/groupzer0/vs-code-agents --skill document-lifecycle-groupzer0

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: document-lifecycle
Source: https://github.com/groupzer0/vs-code-agents/tree/main/vs-code-agents/skills/document-lifecycle
Command: npx skills add https://github.com/groupzer0/vs-code-agents --skill document-lifecycle-groupzer0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Unified document lifecycle management across agent-output work chains ensures consistent IDs, traceability, and orderly closure from analysis to critique and release. It enforces a single global identifier, moves completed work to closed folders, and provides orphan-detection safeguards to maintain an auditable history.

Core Features & Use Cases

Unified numbering with a central .next-id file and ID inheritance across related documents.
Terminal-status handling that moves closed work to a dedicated closed/ subfolder and logs the lifecycle.
Orphan detection and periodic sweeps to keep active work visible and auditable across planning, implementation, QA, UAT, and critiques.

Quick Start

Load this skill at session start to enable unified IDs, terminal-status handling, and automated closure across the document lifecycle.

Frequently Asked Questions about document-lifecycle

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

FAQPage Schema

What is a document lifecycle workflow with unified ID management?▼

A document lifecycle workflow enforces a single global identifier across related documents and manages terminal closures from analysis to release, ensuring traceability and orderly archiving across agent-output work chains.

How do I maintain an audit trail across planning, implementation, and QA documents?▼

You can maintain an audit trail by applying a centralized agent-output/.next-id counter that propagates a unified ID across analyst, planner, implementer, QA, UAT, and DevOps domains to coordinate traceability.

How do I move completed documents to a closed folder structure?▼

Terminal-status handling moves closed work to a dedicated closed/archived directory and logs the lifecycle, relocating completed documents out of active directories to maintain an auditable history.

What is the best way to detect orphaned documents in a workflow archiving system?▼

Periodic sweeps provide orphan detection to keep active work visible and auditable across planning, implementation, QA, UAT, and critiques by identifying documents lacking proper ID inheritance or terminal status.

Can I use YAML frontmatter to manage terminal statuses in SKILL.md files?▼

Yes, the lifecycle management implements technical rules utilizing YAML frontmatter with name and description fields in SKILL.md files to coordinate terminal statuses and archive directory structures.

Do I need to load the document lifecycle skill at session start for ID propagation?▼

Loading this skill at session start enables unified IDs, terminal-status handling, and automated closure across the document lifecycle, ensuring ID propagation from the beginning of agent-output work chains.