pharaoh-tailor-detect

To detect sphinx-needs conventions, analyze the project's needs.json index to infer ID prefixes, separators, regex patterns, lifecycle states, and artefact field usage. This process generates a structured JSON report detailing the observed conventions for auditing and configuration generation.

A needs.json index is used to store and export the structured data of a built sphinx-needs project. Analyzing this file allows you to observe actual project conventions, such as ID prefixes, lifecycle states, and artefact fields, without manually inspecting source files.

Auditing lifecycle states and ID prefixes in sphinx-needs is done by analyzing the built needs.json index. This observation process surfaces the actual regex candidates and state conventions used, outputting a structured JSON report for review.

Yes, you can generate tailoring configurations by first observing the existing sphinx-needs project conventions. Analyzing the needs.json index produces a JSON report of ID patterns and artefact fields, which serves as the input for generating the final tailoring configuration.

No, convention detection requires no external dependencies. It operates by directly analyzing the needs.json index and current IDs from your built sphinx-needs project to produce a structured JSON report of the observed conventions.

The best way to prepare a sphinx-needs project for tailoring is to audit its current conventions. By analyzing the needs.json index to identify ID regex patterns and artefact fields, you create a reliable JSON report that ensures safe configuration generation.