phase-templates

Phase templates provide reusable definitions for discovery, exploration, architecture, and planning phases. Instead of rewriting phase content for each workflow, reference standardized templates that enforce consistent sections, outputs, and integration hooks across devloop commands, agents, and plan execution.

Phase templates define standardized phase sections, expected outputs, and integration hooks like plan.md generation and phase prompts. They enforce domain-skill references and consistent execution patterns across discovery, exploration, architecture, planning, implementation, and testing scenarios.

Yes. Phase templates apply to devloop commands, agents, and plan execution. A single template definition ensures consistent phase behavior whether invoked through commands, agent tasks, or workflow plans, eliminating duplication across your devloop environment.

Templates standardize phase outputs and command references, creating predictable handoff points between discovery, exploration, planning, and implementation phases. This consistency reduces friction when passing context and decisions between workflow stages.

Reference existing phase templates in your devloop commands instead of defining phases inline. Templates eliminate duplicating phase content and automatically apply standardized sections, outputs, and integration hooks to ensure consistent execution patterns.