agw-implementation-planning

Phase-structured implementation planning generates a detailed execution plan based on completed analysis and ADRs, ensuring every technical change is mapped to a specific, validated unit of work before coding begins. It enforces strict architectural oversight and phase-gated execution.

You create an implementation plan requiring architect approval by running a planning process that consumes completed analysis files to generate phase-structured plans, stakeholder intent seeds, and technical traceability documentation for explicit architectural review before execution.

You need architect-governed implementation planning when your software development workflow requires strict architectural oversight, phase-gated execution, technical traceability, risk documentation, and explicit architect approval before implementation begins to prevent scope creep.

No, this implementation planning approach requires completed analysis files and architectural decision records as prerequisites. It bridges the gap between analysis and execution by generating phase-based plans and stakeholder alignment seeds from those existing technical foundations.

You mitigate scope creep and technical debt by enforcing a strict planning protocol that documents risks, deviations, and target-state execution flows. This ensures technical changes are validated units of work mapped to architect-approved phases.

The best way to align stakeholder intent before coding is to generate forward-looking executive and business seeds during the implementation planning phase. This verifies intent against a detailed, phase-structured technical plan before any development starts.