pharaoh-release

Generates release artifacts and changelogs from sphinx-needs changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the generation of release artifacts from sphinx-needs changes, creating structured changelogs, release notes, and traceability metrics to support safety-critical audits.

Core Features & Use Cases

  • Identify changed requirements, specifications, implementations, and test cases between releases.
  • Produce a consolidated changelog and formal release notes, plus traceability coverage metrics.
  • Gate release steps in enforcing mode (verification and optional MECE) and provide flexible output options.

Quick Start

Trigger the release workflow with pharaoh:release to generate release artifacts from your changes.

Frequently Asked Questions about pharaoh-release

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

FAQPage Schema
How do I generate structured changelogs and release notes from sphinx-needs changes?

Generate structured changelogs and release notes from sphinx-needs changes by triggering the pharaoh:release workflow, which reads session state and pharaoh.toml to identify changed requirements, specifications, implementations, and test cases.

Can I enforce traceability coverage metrics for safety-critical audit documentation?

Enforce traceability coverage metrics for safety-critical audit documentation by applying verification and optional MECE checks in the release preparation workflow, ensuring changed needs meet strictness gating.

What is the best way to identify changed requirements between releases?

Identify changed requirements between releases by running a release workflow that reads session state to automate change-impact analysis across needs, specifications, implementations, and test cases.

Does pharaoh-release support configurable workflows for release preparation?

Configurable workflows for release preparation are supported by reading pharaoh.toml configurations, allowing you to gate release steps in enforcing mode with verification and optional MECE checks.

How do I produce consolidated release artifacts from sphinx-needs?

Produce consolidated release artifacts from sphinx-needs by triggering the release workflow, which generates formal release notes, structured changelogs, and traceability metrics from identified changes.

Why use MECE checks during release preparation?

Use MECE checks during release preparation to ensure changed needs are mutually exclusive and collectively exhaustive, satisfying strictness gating requirements for audit-ready documentation.