pharaoh-plan

Break requirement changes into structured, ordered tasks for sphinx-needs projects.

24|Updated Feb 12, 2026

Search Tags:#workflow #planning #requirements #traceability #change-management #planning-tool #pharaoh

Ready to run

npx skills add https://github.com/patdhlk/pharaoh --skill pharaoh-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pharaoh-plan
Source: https://github.com/patdhlk/pharaoh/tree/main/skills/pharaoh-plan
Command: npx skills add https://github.com/patdhlk/pharaoh --skill pharaoh-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break down complex requirement changes into a concrete, executable plan that ensures traceability and workflow compliance.

Core Features & Use Cases

Top-down task planning: automatically decomposes changes into requirements, specifications, implementations, and tests.
Workflow enforcement: respects gates like change-analysis, verification, and MECE checks.
Dependency-aware sequencing: orders tasks to preserve hierarchy and traceability across the project.

Quick Start

Describe your change and run pharaoh-plan to generate a structured execution plan.

Frequently Asked Questions about pharaoh-plan

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

FAQPage Schema

How do I break requirement changes into ordered tasks for sphinx-needs projects?▼

To break requirement changes into ordered tasks, you describe the change and run the planning tool to automatically decompose it into requirements, specifications, implementations, and tests while respecting project workflow constraints.

How does dependency-aware sequencing work for requirement traceability?▼

Dependency-aware sequencing for requirement traceability works by ordering decomposed tasks hierarchically, ensuring that specifications, implementations, and tests align with the project's established workflow gates and structural dependencies.

Can I enforce MECE checks and verification gates during change analysis?▼

Yes, you can enforce MECE checks and verification gates during change analysis by configuring the workflow constraints, ensuring that requirement changes meet hierarchical authoring and mandatory verification standards before execution.

What is the best way to plan changes across needs, specifications, and tests?▼

The best way to plan changes across needs, specifications, and tests is to use a top-down planning approach that automatically decomposes changes into structured, executable tasks while preserving hierarchy and traceability.

Do I need a specific configuration file to apply workflow constraints to change planning?▼

Yes, you need the pharaoh.toml configuration file to apply hierarchical authoring, gating requirements, and optional MECE checks, ensuring structured execution plans fully comply with project workflow constraints.