spec-implementing-analyzing

To translate approved specifications into an implementation plan, analyze SPECS/*.md files alongside existing code to generate a root ANALYSIS.md defining scope, priorities, and module structure. This enforces traceability from specifications to categories before task generation.

Analyzing project specs and existing code for module structure involves reading SPECS/*.md files to surface boundaries and priorities, then generating an ANALYSIS.md document. This structured plan maps modules and categories to support review before development begins.

Determining build order from approved specifications requires analyzing documentation to surface priorities and scope. Generating an ANALYSIS.md file provides prioritization guidance and category mapping to sequence implementation tasks effectively.

Generate an implementation scope analysis from SPECS when starting Stage 3 implementation from approved specifications. It determines what to build, module relationships, and boundaries, producing a structured plan suitable for review before task generation.

Yes, the specs analysis workflow maintains traceability from documentation to implementation categories. It maps SPECS/*.md files directly to the resulting ANALYSIS.md, ensuring alignment and supporting structured review before generating development tasks.