document-lifecycle

What problem does it solve?

This skill centralizes the lifecycle of documents across domains by enforcing a single global ID, terminal statuses, and automated closure, enabling end-to-end traceability and consistent governance.

Core Features & Use Cases

• Unified numbering with the .next-id protocol to generate and propagate IDs across Analysts, Planners, Implementers, QA, UAT, and Critics.
• Lifecycle governance with predefined terminal statuses that automatically move completed work to closed/ directories and preserve an audit trail.
• Orphan detection and periodic sweeps to keep domains clean, ensure no terminal documents remain in active folders, and maintain cross-domain references.
• Cross-reference handling to ensure links between active and closed documents stay valid as documents transition states.

Quick Start

Create a new document by reading agent-output/.next-id, incrementing it, and using the ID in the document header. When a document reaches a terminal status, update its frontmatter, add a changelog entry, create a closed/ folder if needed, and move the file into closed/. Run the self-check to move any orphaned documents to closed/ at session start.