project-initialization-phase

Project initialization documentation is generated by running the /init-project command, which uses an interactive questionnaire to create 8 core design documents for greenfield setups. It guides you through 15 essential questions to gather context and automatically builds foundational architecture and tech stack documents.

Yes, brownfield codebase scanning analyzes existing code to auto-detect the tech stack, architecture patterns, and database schemas. This process automatically extracts current project state information to populate the 8 comprehensive design documents without manual entry.

Initializing project structure and docs is handled by an orchestration command that distinguishes between greenfield and brownfield contexts. It validates foundational documentation creation by applying templates for new projects or scanning existing codebases to document the current state.

Manual input is needed only for the 15 essential questions in the interactive questionnaire for greenfield projects. For brownfield projects, the codebase scanning mechanism auto-detects technical details to minimize manual data entry during document generation.

Project initialization creates 8 comprehensive project-level design documents, including overview, architecture, and tech stack files. These foundational documents are generated from templates and validated user input to ensure a solid development baseline.

The interactive questionnaire is required to gather essential project context that automated scanning cannot infer, ensuring the 8 generated design documents accurately reflect architectural intent. This validation step guarantees foundational documentation aligns with specific greenfield or brownfield requirements.