flow-plan

Software architecture planning without code is done by generating a structured critique and task decomposition outline in a GODS-formatted whiteboard document. This approach strictly separates architecture planning from implementation, writing results exclusively to a markdown file.

A GODS-formatted whiteboard document is a structured markdown file used to outline software architecture plans, decompose tasks, and validate project requirements. It serves as a central planning artifact before any implementation begins.

To identify uncertainty before implementation, you can use a proactive architecture planning workflow that automatically critiques the plan and raises questions. It highlights gaps in the task decomposition and writes them to a whiteboard document for review.

Yes, you can separate planning from implementation by using a task-management tool to track steps within a GODS-formatted whiteboard document. This ensures the architecture validation phase is completed and documented before any code is written.

The best way to decompose early-stage architecture tasks is by applying structured critique to generate a comprehensive GODS-formatted plan outline. This documentation-first workflow captures all steps and proactive questions in a whiteboard file.

Architecture planning output is saved exclusively to the ./documents/whiteboard.md file. This documentation-first workflow ensures the GODS-formatted plan outline and identified gaps are stored for later execution.