Plan Templates

To generate an implementation plan template, the workflow routes the correct roadmap, session plan, or detail plan structure based on plan type, docs-only scope, and TDD requirements. It enforces status lifecycle and phase difficulty formatting rules before drafting.

Workflow orchestration for phase planning is needed when creating structured implementation plans. It synchronizes roadmap and governance context from project documentation to prevent hallucinated versions and missing required steps during plan file generation.

To apply TDD and hardened audit gates to a project plan, the template routing process detects these strict requirements and selects a specialized plan structure. This ensures execution constraints and governance rules are embedded directly into the phase scaffolding.

Yes, you can create a documentation-only plan. The template routing mechanism identifies the docs-only scope and applies different execution constraints to the generated plan, ensuring the structure matches the documentation requirements without code dependencies.

Plan templates fail to match governance conventions when roadmap and project governance synchronization is skipped. The workflow requires syncing agent rules and skills from project documentation before drafting any plan content to avoid broken conventions.

The best way to manage status lifecycle and phase difficulty in a roadmap is using template scaffolding. It enforces the Draft to Active status progression and applies difficulty-tag and model-hint conventions for each phase during generation.