pharaoh

Use this agent for deep analysis of sphinx-needs projects requiring complex traceability resolution, large-scale requirement set analysis, or detailed need parsing across multiple files and projects. <example>Context: The user needs to trace a requirement through a complex multi-project setup. user: "Trace REQ-SYS-001 through all subsystem projects" assistant: "I'll dispatch the sphinx-needs-expert agent to handle this complex cross-project traceability query." <commentary>Since the traceability spans multiple projects and may involve external needs, use the sphinx-needs-expert agent for thorough analysis.</commentary></example> <example>Context: The user wants MECE analysis on a large project. user: "Check all 500 requirements for gaps" assistant: "Let me use the sphinx-needs-expert agent to systematically analyze the full requirement set." <commentary>Large-scale MECE analysis benefits from a dedicated agent that can methodically work through the entire set without context pollution.</commentary></example>

Use when drafting one activity diagram showing control flow (actions, decisions, forks/joins, swimlanes) for one procedure or algorithm. Typical ASPICE usage — SWE.3 Software Detailed Design. Renderer tailored via `pharaoh.toml`. Does NOT emit other diagram kinds. Status — PLANNED (design-only scaffold; invoking returns sentinel FAIL until implemented).

Use when verifying that a source file is covered by the need catalogue on two axes — (1) at least one CREQ declares the file as its `:source_doc:`, and (2) every project-defined exception class raised in the file is named by some CREQ's title or content. Exception classes not defined in the project source tree (stdlib, third-party deps) are reported as `external` and do not fail the axis. Classifies non-behavioral files (constants, type aliases, bare re-exports) as skipped. Language-parametric via the shared regex table in `skills/shared/public-symbol-patterns.md` (python / rust / typescript / go / c / cpp / java). Single mechanical structural check.

Use when drafting a single sphinx-needs architecture element from one parent requirement. The artefact type is parameterised via `target_level` (any catalog-declared architecture type — e.g. `arch`, `swarch`, `sys-arch`, `module`, `component`, `interface`). Emits an RST directive block linking back to the parent via `:satisfies:`.

Use when auditing a single architecture element against the 10 ISO 26262-8 §6 axes plus arch-specific axes (traceability back to requirement). Emits structured findings JSON.

Use when running a full project audit in parallel by dispatching 5 atomic audit skills, each writing findings to a shared Papyrus workspace via pharaoh-finding-record for automatic deduplication. Emits the aggregated deduplicated findings list.