review-lifecycle

Reviews resource lifecycle documents for completeness, consistency, and state transition correctness.

11|1|Updated Jul 25, 2025

Search Tags:#specification #sdlc #state machine #invariants #state transitions #document audit #lifecycle review

Ready to run

npx skills add https://github.com/tomzx/agents --skill review-lifecycle-tomzx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-lifecycle
Source: https://github.com/tomzx/agents/tree/main/skills/review-lifecycle
Command: npx skills add https://github.com/tomzx/agents --skill review-lifecycle-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Lifecycle documents often contain unreachable states, missing transitions, unsound invariants, or gaps against the specification, and catching these issues manually is slow and inconsistent. This Skill audits a lifecycle document against a structured six-category checklist and produces a findings report with a clear verdict. ## Core Features & Use Cases - Six-Category Audit: Checks completeness, consistency, spec alignment, transition correctness, invariant soundness, and retention soundness. - Cross-Referencing: Validates states and transitions against the feature's specification and requirements documents. - Structured Verdict Output: Writes findings to review-lifecycle.md with frontmatter verdict of approved, changes-requested, or rejected. - Use Case: After drafting a lifecycle document for an order management feature, run this review to detect that the archived state is unreachable and that revoked API keys lack a retention policy before implementation begins. ## Quick Start Ask the agent to review the lifecycle document for the current feature and report any findings across the six review categories.

Frequently Asked Questions about review-lifecycle

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

FAQPage Schema

How do I review a resource lifecycle document?▼

Run the review-lifecycle skill with an issue number or a lifecycle document path. It audits the document across six categories and writes findings with a verdict to review-lifecycle.md in the feature directory.

What does a lifecycle review check for?▼

It checks completeness, consistency, spec alignment, transition correctness, invariant soundness, and retention soundness. This includes unreachable states, missing transitions, invariants that do not hold in every state, and undocumented retention policies.

How are unreachable states detected in a state machine review?▼

The review checks whether every state has at least one incoming transition and whether dead-end states lack required exit transitions. A state like archived with no documented incoming transition is reported under Transition Correctness.

What verdicts can a lifecycle review produce?▼

The review emits approved when there are no blocking findings, changes-requested when the author must address findings, and rejected for fundamental flaws. The verdict is written to the findings file frontmatter and optionally to an outcome YAML file.

Does the lifecycle review require a specification document?▼

A specification document is used for cross-referencing data models, API contracts, and sequences, and a requirements document is optional. The review can still run on a lifecycle document alone but produces stronger spec alignment findings when both are present.