plan-marshall

End-to-end plan lifecycle orchestration automates action routing through workflow documents while enforcing disciplined phase transitions from init to finalize. It applies config-driven behavior, deterministic script routing, and strict gating with user reviews to ensure structured execution.

Workflow-driven routing directs plan actions to the correct workflow document and applies phase transitions deterministically. It enforces config-driven behavior and strict gating with user reviews, ensuring that execution moves through structured phases like init, refine, outline, plan, execute, and finalize.

Yes, you can create plans from predefined recipes or lessons to accelerate onboarding and consistency. Recipe-based creation and lesson-based conversions allow you to quickly generate structured plans and route them through the standard lifecycle phases with deterministic enforcement.

The six phases of plan lifecycle orchestration are init, refine, outline, plan, execute, and finalize. Gatekeeping rules enforce strict phase transitions with auto-continue and review gates, applying config-driven behavior and deterministic script routing to ensure disciplined progression.

Yes, plan lifecycle orchestration enforces strict gating with user reviews and phase transitions. It applies config-driven behavior and deterministic script routing to ensure that every phase change, from init through finalize, is validated and properly reviewed before proceeding.

Use config-driven behavior and deterministic script routing for planning workflows when you need strict enforcement of phase transitions and consistent gatekeeping. This approach ensures disciplined execution across the entire plan lifecycle, preventing unstructured or ad-hoc progression through critical phases.