speckit-plan

A multi-phase planning workflow generates design artifacts by orchestrating phases from initial research to contract definition. It applies repository-specific guidance and evaluates extension hooks before and after planning to ensure architecture alignment and conservative design decisions.

The best way to plan implementation workflows requiring rigorous architecture alignment is a phase-driven template process. It ensures explicit context loading and gate evaluation at each step, producing documented outputs while preserving existing repository structure through conservative design decisions.

Creating planning artifacts with decision traceability requires a workflow that updates agent context dynamically during the process. By applying a plan template, the workflow documents extension hooks and captures new decisions explicitly across phases, ensuring every architectural change is tracked.

Yes, the planning workflow template integrates extension hook checks before and after the planning process. This ensures repository-specific guidance is applied and any custom logic is executed at the correct phase boundaries during artifact generation.

Yes, you can use a plan template to structure research and data modeling for repositories requiring conservative design decisions. The workflow ensures conservative changes by evaluating gates and applying repository-specific guidance to preserve the existing structure while generating artifacts.

You should avoid a multi-phase implementation planning workflow if your project does not require rigorous upfront planning or explicit gate evaluation. This template is designed for complex repositories needing architecture alignment and documented extension hooks, not for rapid prototyping or simple tasks.