workflow-architect

Software architecture planning requires a governed multi-phase workflow that enforces requirements interviewing, research, and brainstorm checkpoints before execution. This approach prevents premature coding by producing a persistent three-level plan covering project, phase, and task hierarchy.

A requirements interview taxonomy is a structured ten-category framework used during architecture planning to ensure comprehensive requirement coverage. It enforces mandatory depth thresholds to eliminate missing critical requirements before drafting the system design.

Yes, you can resume a production readiness workflow safely after interruptions by leveraging persistent session recovery. The process maintains a state file and persists brainstorm artifacts to disk, allowing the architecture session to continue seamlessly.

The architecture workflow enforces strict phase gates preventing code before the execution-planning phase. Adding requirements mid-execution requires returning to the requirements phase to maintain production readiness and update the persistent plan hierarchy.

To avoid first-intuition architecture mistakes, use a workflow with mandatory research and brainstorm checkpoints. These gates enforce evidence-backed decision-making during the draft phase, reducing premature or poorly evaluated architectural choices.