skills.rest
seanspiesman
seanspiesmanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

document-lifecycle

Standardize agent document statuses, numbering, and closure workflows.

Updated Jan 12, 2026
Search Tags:#workflow#traceability#version-control#lifecycle-management#orphan-detection#document-lifecycle#closure-procedure
One-click install
npx skills add https://github.com/seanspiesman/Agents-and-Workflows --skill document-lifecycle-seanspiesman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: document-lifecycle
Source: https://github.com/seanspiesman/Agents-and-Workflows/tree/main/custom-agents/skills/document-lifecycle
Command: npx skills add https://github.com/seanspiesman/Agents-and-Workflows --skill document-lifecycle-seanspiesman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Unified document lifecycle management across all agents by standardizing statuses, numbering, and transitions to keep traceability and reduce orphaned work.

Core Features & Use Cases

  • Terminal statuses define and drive automated closure, ensuring completed work moves to a closed archive.
  • Unified numbering enables a single ID stream via the .next-id mechanism and propagates IDs downstream for full traceability.
  • Orphan-detection routines sweep domains to close or archive stale, terminal-status documents and prevent loose artifacts.
  • Cross-domain closure ensures end-to-end lifecycle consistency across planning, implementation, QA, UAT, critiques, and retrospectives.

Quick Start

Initialize the lifecycle system by creating the first analysis document to seed the .next-id counter and begin traceable workflows.

Frequently Asked Questions about document-lifecycle

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

FAQPage Schema
How do I manage document lifecycle traceability across multiple agents?▼

Document lifecycle traceability is managed by standardizing document IDs, statuses, and closure workflows across all agents. A shared .next-id counter propagates identifiers downstream to ensure full lineage from planning through retrospectives.

What is the best way to detect and close orphaned work artifacts in agent output directories?▼

Orphan-detection routines sweep agent-output directories to identify stale artifacts with terminal statuses. These cross-domain closure procedures automatically close or archive loose documents to prevent orphaned work from accumulating.

How do I enforce terminal statuses and automated closure for completed workflow documents?▼

Terminal statuses drive automated closure by enforcing completed analysis, QA, or UAT documents to move into a closed archive. This lifecycle management ensures no active work is left lingering outside the designated terminal state.

Can I use a unified document numbering system across planning, implementation, and QA domains?▼

A unified numbering system enables a single ID stream across planning, implementation, and QA domains. The .next-id mechanism seeds and propagates these identifiers to maintain traceable document lineage throughout the entire workflow.

How do I initialize a document lifecycle system to begin traceable workflows?▼

To initialize the document lifecycle system, create the first analysis document. This action seeds the .next-id counter and establishes the baseline for standardized statuses and cross-domain traceable workflows.

Why does my workflow produce loose artifacts despite having version control?▼

Loose artifacts occur without standardized cross-domain closure procedures. Implementing orphan-detection routines and terminal statuses ensures completed work moves to a closed archive, maintaining lifecycle consistency across all agent outputs.

Related Skills

Explore More Software Engineering Skills→
groupzer0groupzer0
284

document-lifecycle

Orchestrate document lifecycle with global IDs and terminal closures.

Community
Advanced
Venkateshvenki404224Venkateshvenki404224
25

frappe-workflow-generator

Generate Frappe workflow JSON definitions for document approvals and state transitions.

Community
Intermediate
amanhsnamanhsn

quality-documentation-manager

Manage document control systems for ISO 13485 and 21 CFR Part 11 compliance.

Community
Advanced
unfinishablemapunfinishablemap
3

validate-all

Validate Hugo and Obsidian site content for frontmatter, links, orphans, drafts, and lengths.

Community
Basic