Map and analyze traceability across sphinx-needs projects with structured trace trees.
npx skills add https://github.com/useblocks/pharaoh --skill pharaoh-trace-useblocks
Please help me install this Agent Skill. Skill: pharaoh-trace Source: https://github.com/useblocks/pharaoh/tree/main/skills/pharaoh-trace Command: npx skills add https://github.com/useblocks/pharaoh --skill pharaoh-trace-useblocks
Traces and visualizes how needs, specifications, implementations, tests, and code relate in sphinx-needs projects to reveal coverage and potential gaps and to support validation workflows.
Identify a target need and run a trace to display its upstream and downstream relationships across all configured link types.
High-intent search queries and answers about installing and using this skill.
Tracing requirements in sphinx-needs involves mapping a target need to build a bidirectional trace graph. This graph surfaces upstream and downstream relationships across standard links, extra_links, and codelinks to reveal coverage and gaps.
Requirements traceability tracks relationships between needs, specifications, implementations, tests, and code. Graph analysis helps by building a structured trace tree with labeled edges and statuses to surface cycles, gaps, and coverage for validation workflows.
Yes, you can filter traceability depth and link types when navigating sphinx-needs projects. The trace supports optional depth and type filters, allowing scalable navigation across standard links, extra_links, and codelinks.
Yes, sphinx-needs traceability supports multi-project contexts and cycle detection. It reads project configuration like extra_links and pharaoh.toml to detect cycles, surface gaps, and emit a structured trace tree across project boundaries.
The best way to analyze downstream relationships from requirements to code is running a trace on a target need. It traverses configured sphinx-codelinks and extra_links to emit a structured trace tree showing labeled edges and statuses.
patdhlkTrace upstream and downstream relationships across needs and linked artifacts.
DenissvgnValidate deliverables against requirements by examining architecture, test coverage, and implementation artifacts.
useblocksAnalyze the full impact of proposed changes to sphinx-needs items across direct and transitive links.
useblocksAnalyzes sphinx-needs traceability graphs to identify gaps, orphaned nodes, redundancies, and status or ID inconsistencies across req, spec, impl, and test types.
