pharaoh-change

Trace direct and transitive impacts of proposed changes across needs and code links.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze and document the impact of proposed changes across needs, specifications, implementations, tests, and their traceability to code.

Core Features & Use Cases

  • Trace direct and transitive impact across needs and code links to surface affected assets.
  • Generate a structured Change Document with actionable items for owners, tests, and implementations.
  • Support session-state tracking and data access guidelines to enable safe downstream authoring workflows.

Quick Start

Provide the target need ID and a description of the change, and run the impact analysis 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 impact of a requirement change across related needs?

To trace requirement change impact, you provide a target need ID and change description to resolve direct and transitive impacts across links, generating a structured Change Document with actionable items for downstream workflows.

What is transitive impact analysis for requirements traceability?

Transitive impact analysis identifies all directly and transitively impacted needs when a change is proposed, tracing connections across requirement links, code links, and related artifacts to surface affected assets comprehensively.

How do I generate a change document for code and requirement links?

You generate a change document by running an impact analysis on a target need ID, which traces direct and transitive impacts across requirements and code links to surface a structured document with actionable items for owners, tests, and implementations.

Does impact analysis work with Sphinx needs and codelinks?

Yes, impact analysis traces across requirement links and code codelinks to identify affected assets. It includes guidance for data access and session-state updates to support safe downstream authoring workflows.

Can I track session state for downstream authoring after change analysis?

Yes, the impact analysis includes session-state tracking and data access guidelines to enable safe downstream authoring workflows after resolving target IDs and surfacing the Change Document.

What do I need to provide to start a change impact analysis?

To start a change impact analysis, you need to provide the target need ID and a description of the proposed change. The analysis then resolves IDs and traces impacts to generate a Change Document.