phase-kickoff

To convert phase documentation into an ordered execution plan, you parse the current phase document to generate tiered work packages organized by epics. This process creates structured work packages with titles, goals, acceptance criteria, and spec checklists from fragmented phase docs.

Spec-first project planning is a workflow where phase documents define requirements before execution, producing test-first plans with acceptance criteria and spec checklists. You need it when phase documents require structured conversion into actionable, test-validated work packages.

Creating work packages with acceptance criteria from a phase document involves extracting phase requirements and generating proposed packages that include title, goal, acceptance criteria, spec checklist, criticality, and dependencies. The phase document must be parsed to produce an ordered plan with a first executable work package for immediate action.

Yes, generating work packages for UI tasks can include RTL and Hebrew obligations as part of the proposed package structure. The phase-kickoff process specifically accounts for RTL and Hebrew obligations when defining work packages, ensuring localization requirements are captured alongside criticality and dependencies.

Yes, phase-kickoff operates without external dependencies or components, functioning as a standalone planning tool. It directly processes the current phase document to produce an ordered execution plan, proposed work packages, and a first executable item without requiring additional frameworks or libraries.

The best way to keep project state in sync after planning a phase is to generate todos that include updating the current phase document at docs/phases/CURRENT.md. This ensures the phase document reflects the latest execution plan, work packages, and project status after the planning process completes.