pharaoh-change

Analyze the full impact of proposed changes to sphinx-needs items across direct and transitive links.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze the full impact of a proposed change to any sphinx-needs item.

Core Features & Use Cases

  • Understand the end-to-end impact across direct and transitive links (including standard links, implements, tests, and codelinks) and generate a structured Change Document.
  • Detect and update session state, produce a Change Document, and support acknowledgment workflows for gated authoring.
  • Support automated and interactive analysis to surface required updates and reviews across linked needs and code.

Quick Start

Invoke the pharaoh-change skill with the target need ID and a plain-language change description to generate a Change Document.

Frequently Asked Questions about pharaoh-change

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

FAQPage Schema
How do I trace the full impact of a proposed change across sphinx-needs requirements and code?

Trace change impact across sphinx-needs by analyzing direct and transitive links including standard links, implements, tests, and codelinks to produce a comprehensive structured Change Document for review.

What is requirements traceability impact analysis and when do I need a Change Document?

Requirements traceability impact analysis identifies all downstream effects of modifying a need. You need a Change Document when assessing proposed changes across linked requirements, tests, and code for comprehensive review workflows.

Can I generate a structured impact report for sphinx-needs items without setting up approval gates?

Yes, you can generate a structured impact report for sphinx-needs items using gate-free invocation. It automatically detects and updates session state to support subsequent acknowledgment workflows for gated authoring.

What is the best way to analyze transitive links and code dependencies for a sphinx-needs requirement change?

The best way to analyze transitive links is applying traceability-aware assessment across standard links, implements, tests, and sphinx-codelinks, surfacing all required updates and reviews in a single structured report.

Does sphinx-codelinks support automated impact analysis for requirement changes?

Yes, sphinx-codelinks supports automated impact analysis by tracing proposed changes across linked code and needs. It surfaces required updates and reviews through both automated and interactive analysis workflows.

Why does my sphinx-needs change analysis miss required updates in linked tests and code?

Change analysis misses updates if transitive links are not fully traversed. Comprehensive analysis must cover direct and transitive links across implements, tests, and codelinks to ensure all required reviews are surfaced.