pharaoh-mece

Orphan detection in a sphinx-needs traceability graph identifies disconnected or terminate-too-early needs. It flags nodes lacking proper upstream or downstream links across requirement, specification, implementation, and test types.

MECE gap analysis for requirements traceability checks for missing downstream coverage in your project. It ensures every requirement links to a specification and every spec links to an implementation by analyzing the graph.

Checking status and ID consistency across linked sphinx-needs types highlights mismatches between need statuses and their connected parents or children. It validates cross-type links to catch redundancies and inconsistencies.

Schema and ontology validation on sphinx-needs projects is triggered when deeper tooling is available. It supports structural validation and cross-type link checks to enforce MECE dimensions across needs.

Redundancy analysis finds duplicate or highly similar needs within the same type in a traceability graph. It flags these redundancies to help maintain a clean and consistent sphinx-needs project structure.

MECE traceability analysis works for projects with needs across types like req, spec, impl, and test. It checks for gaps, orphaned nodes, and status inconsistencies across these mixed requirement and test dimensions.