Lifecycle

Orchestrate documentation lifecycle transitions with conflict-aware handling and auditable logging.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/murillodutt/cellm --skill lifecycle-murillodutt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Lifecycle
Source: https://github.com/murillodutt/cellm/tree/main/docops/skills/lifecycle
Command: npx skills add https://github.com/murillodutt/cellm --skill lifecycle-murillodutt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage the complete documentation lifecycle across states (draft, active, deprecated, archived) with conflict-aware transitions and a comprehensive audit trail.

Core Features & Use Cases

  • Orchestrates state transitions with guardrails and logging
  • Resolves conflicts when restoring to occupied paths and preserves history
  • Archives content in a structured, time-stamped repository and records outcomes

Quick Start

Transition a draft document to active and log the outcome

Frequently Asked Questions about Lifecycle

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

FAQPage Schema
How do I manage documentation lifecycle transitions from draft to archived?

You manage documentation lifecycle transitions by orchestrating state changes with preflight checks, conflict-aware handling, and auditable logging to ensure safe content evolution.

What is the best way to handle conflict resolution when restoring archived documents?

Conflict resolution when restoring archived documents is handled by resolving path collisions and preserving history, ensuring restored content does not overwrite existing files without proper safeguards.

How do I audit and log deprecated documentation in my workflow?

Deprecated documentation is audited and logged by recording lifecycle outcomes to a designated deprecations log file, providing a comprehensive trail of all state transitions and archival actions.

Can I apply documentation lifecycle guardrails to active workflows without losing history?

Documentation lifecycle guardrails can be applied to active workflows without losing history because the system enforces preflight checks and preserves historical records during restorations to occupied paths.

Does documentation archiving support structured, time-stamped repositories?

Documentation archiving supports structured, time-stamped repositories by organizing archived content chronologically and recording transition outcomes to maintain a clear audit trail.

When should I use preflight checks for document state transitions?

Preflight checks for document state transitions should be used whenever documents evolve across states like draft, active, deprecated, and archived to prevent data loss and ensure safe lifecycle management.