brainstorming-explorer

To generate a Project Discovery Draft, systematically explore the codebase to identify entry points, dependencies, and architecture, then critique code quality against principles like Clean Architecture and SOLID to produce the structured SDLC Phase 0 document.

Systematic codebase exploration is the process of analyzing code structure to identify entry points, dependencies, and architectural paradigms. You need it during SDLC Phase 0, project onboarding, or when assessing an unfamiliar system's code quality.

Critique software architecture by analyzing the codebase structure for adherence to Clean Architecture and SOLID principles, identifying code quality issues through interactive brainstorming, and refining architectural opinions via constructive dialogue.

Yes, you can use this approach for SDLC Phase 0 project onboarding. It streamlines system discovery by generating structured Project Discovery Drafts that document codebase architecture, dependencies, and code quality analysis.

The best way to identify entry points and dependencies is applying systematic exploration heuristics to map the codebase structure, followed by an architectural critique to evaluate how components interact and adhere to design principles.

You need a Project Discovery Draft for system discovery because it provides a structured template documenting the codebase's architecture, entry points, and code quality, ensuring comprehensive analysis during SDLC Phase 0 and onboarding.