amplify-planning

Strategy-first planning is enforced by capturing the rationale for decisions in a strategy document that requires approval before any implementation plan is drafted, reducing misaligned project scope.

Documenting feature rationale works best by creating a strategy document first to capture alternatives, decisions, and approval criteria, effectively guiding development and reducing misalignment before execution.

Set up a two-document workflow by creating a strategy document first using a provided template, then drafting the implementation plan only after the strategy document successfully passes the required approval gates.

Yes, the strategy planning workflow enforces approval gates specifically for non-trivial product initiatives and architectural changes, ensuring strategy must precede implementation and be formally approved before work begins.

Yes, you can apply approval gates and templates to manage unaligned project scope by enforcing a strategy-first workflow that captures decisions and rationale before implementation details are executed.

A two-document strategy and implementation workflow should not be used for trivial features that lack architectural changes, as the overhead of strategy documentation and formal approval gates outweighs the governance benefits for simple tasks.