gsdd-new-project

Auditing existing code for project planning involves inspecting repositories to identify current architecture, active components, and technical constraints, which then informs the generated specifications and execution roadmaps for subsequent development phases.

Generating a specification and roadmap requires analyzing project goals through targeted questioning and evaluating existing code, ultimately producing a detailed SPEC.md file and a phased ROADMAP.md for project scaffolding and execution.

A detailed project specification and roadmap ensures thorough planning and alignment among developers by clarifying system goals, documenting architectural constraints from existing code, and establishing a phased execution plan for project scaffolding.

Yes, this project planning approach supports existing codebases by auditing current repositories to inspect architecture and constraints, then using that analysis to generate updated specifications and execution roadmaps for continued development.

The best way to audit code for documentation is to inspect existing repositories for architecture, components, and constraints, using those findings to drive targeted questioning and generate accurate project specifications and phased plans.

No, you do not need an existing codebase; the process can start by asking what you want to build, using targeted questioning to clarify desired system requirements, and then generating detailed specifications and execution plans.