pharaoh-lifecycle-check

Validate lifecycle transitions against workflows.yaml state machines.

24|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/useblocks/pharaoh --skill pharaoh-lifecycle-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pharaoh-lifecycle-check
Source: https://github.com/useblocks/pharaoh/tree/main/skills/pharaoh-lifecycle-check
Command: npx skills add https://github.com/useblocks/pharaoh --skill pharaoh-lifecycle-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill validates whether a proposed lifecycle transition for a sphinx-needs artefact is legally permitted by the project's workflows.yaml state machine, ensuring governance and compliance across changes.

Core Features & Use Cases

  • Validates current lifecycle state against declared states in workflows.yaml.
  • Computes a shortest transition path to a target state when provided and reports any missing prerequisites or invalid transitions.
  • Integrates with needs.json and artefact metadata to resolve the artefact type and current status for automated checks.

Quick Start

Inspect a need's current state and available transitions with a dry-run audit.

Frequently Asked Questions about pharaoh-lifecycle-check

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

FAQPage Schema
How do I validate a sphinx-needs lifecycle state transition?

This Skill validates a proposed lifecycle transition by comparing the artefact's current status against the workflows.yaml state machine and reporting missing prerequisites or undeclared states.

What is a workflows.yaml state machine used for in needs validation?

A workflows.yaml state machine declares allowed states and transition prerequisites, governing lifecycle validation to ensure compliance and prevent illegal status updates for sphinx-needs artefacts.

How do I find the shortest transition path to a target lifecycle state?

Provide a target state, and the Skill computes the shortest transition path through the workflows.yaml state machine while reporting any missing prerequisites or unreachable transitions blocking that route.

Can I check sphinx-needs artefact transitions using needs.json metadata?

Yes, the Skill loads needs.json alongside workflows.yaml to resolve the need type, current status, and transition prerequisites, enabling automated audits of sphinx-needs artefacts.

Why does my lifecycle state transition report an undeclared state?

A lifecycle transition reports an undeclared state when the artefact's current status or target state does not match any state defined in the workflows.yaml state machine, rendering the transition illegal.