document-lifecycle

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.

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.

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.

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.

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.

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.