spec-analyzing

To turn research markdown reports into a structured specification plan, you need a tool that extracts insights from `.research/*.md` files and defines scope, priorities, and SSOT mapping for implementation.

SSOT mapping in specification writing identifies single sources of truth to ensure consistent documentation. It is needed to prevent conflicting data across multiple SPEC documents during implementation planning.

To generate a root ANALYSIS.md that synthesizes multiple research reports, place your findings in a `.research/` folder and run an analysis process to output a structured project plan at the root directory.

Yes, you can define SPEC dependencies and priorities directly from markdown research notes by synthesizing the findings into a structured plan that outlines actions, dependencies, and philosophy updates.

The best way to structure documentation before writing technical specifications is to synthesize existing research into an analysis document containing Context, Structure, Priorities, Dependencies, and SSOT Map sections.

Yes, you need a specific folder structure to analyze research for specification writing. Research files must be placed in a `.research/` directory as markdown files for the analysis process to read and synthesize them.