pharaoh-verify

Verify child needs substantively satisfy parent needs in sphinx-needs projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

pharaoh-verify performs content-level verification to ensure that child needs substantively satisfy their parent needs by assessing the actual text of linked directives, not just structural completeness.

Core Features & Use Cases

  • Content-level verification of parent-child pairs across sphinx-needs projects.
  • Generates a structured verification report, with PASS, PARTIAL, FAIL, and SKIP classifications, and optional schema validation when ubc is available.
  • Integrates with pharaoh workflows (pharaoh.toml gating and session-state updates) to support release decisions.

Quick Start

Execute a verification run with a single instruction: validate all linked needs or scope to a subset using pharaoh:verify.

Frequently Asked Questions about pharaoh-verify

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

FAQPage Schema
How do I verify that child requirements substantively satisfy parent requirements in sphinx-needs?

Content-level requirements verification assesses the actual text of linked sphinx-needs directives to ensure child needs substantively satisfy parent needs, rather than just checking structural completeness. It produces a report with PASS, PARTIAL, FAIL, and SKIP classifications.

How do I check requirements traceability for a targeted scope within my project?

You can scope requirements traceability checks by providing user input or using session data to target specific parent-child pairs. This allows you to verify a subset of linked needs rather than running the validation across the full project.

Does pharaoh-verify integrate with pharaoh.toml configuration settings?

Yes, the verification process respects pharaoh.toml settings for strictness and modes. This integration supports pharaoh workflows by applying configuration gating and updating session-state to support release decisions.

What is the difference between structural completeness and content-level verification of needs?

Content-level verification evaluates the actual text of linked directives to ensure child needs substantively satisfy parent needs, whereas structural completeness only validates that links between requirements exist. This Skill performs the deeper content-level text assessment.

Can I get schema validation for my requirements verification report?

Yes, optional schema validation is applied to the verification report when ubc is available. This ensures the generated PASS, PARTIAL, FAIL, and SKIP classifications meet strict structural and content standards.