document-lifecycle

Orchestrate document state transitions, numbering, and closure across domains.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jfriisj/real-time-speech-translation-mvp --skill document-lifecycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document-lifecycle
Source: https://github.com/jfriisj/real-time-speech-translation-mvp/tree/main/.github/skills/document-lifecycle
Command: npx skills add https://github.com/jfriisj/real-time-speech-translation-mvp --skill document-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about document-lifecycle

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

FAQPage Schema
How do I automate document numbering and tracking across multiple workflow domains?

Document lifecycle governance enforces predefined terminal statuses that automatically move completed files into closed/ directories, preserving an audit trail while keeping active working folders clear of finished records.

What is the best way to keep cross-references valid when moving documents to a closed folder?

Cross-reference handling maintains link validity during state transitions by enforcing documented close procedures, ensuring references between active and closed documents remain intact as files move into closed/ directories.

How do I detect and clean up orphaned documents in a collaborative lifecycle workflow?

Orphan detection runs periodic sweeps at session start to identify terminal documents remaining in active folders, automatically moving them to closed/ directories to keep domains clean and maintain cross-domain references.

Can I use a single document ID chain for analysts, planners, implementers, QA, and UAT simultaneously?

A single global ID chain is enforced across all working domains, enabling analysts, planners, implementers, QA, UAT, and critics to share unified numbering and automated closure rules for consistent governance.

What are the limitations of using automated terminal statuses for document closure?

Automated terminal statuses require strict adherence to the .next-id protocol and frontmatter updates; without proper changelog entries and closed/ folder creation, the audit trail and cross-reference integrity may break during transitions.