plan

To break down settled direction into executable tasks, the process creates a tactical handoff that converts research and structure into vertical-slice task sets. This applies sequencing, risks, and verification strategy to reduce ambiguity and rework.

Vertical-slice task classification organizes executable tasks by categorizing them as AFK (automated) or HITL/review-gated. This classification includes clear blockers, acceptance criteria, and out-of-scope notes to ensure quality control during implementation handoffs.

To publish tactical plan artifacts with proposal gating, you use an artifact gate workflow to ensure the plan is approved before tasks are created. Finalized artifacts and tasks are then committed with repo-relative paths in the content.

Yes, you need vault context loading before drafting an executable task set. It requires loading vault context and confirming or creating structure via vlt/plannotator to ensure the task set aligns with settled research and design.

Yes, you can bypass artifact gating when creating a plan and task set by using the --auto flag. This skips the approval workflow and automatically publishes the tactical QRDSPI plan artifacts and vertical-slice tasks.

A limitation of using vertical slices for task breakdown is that it strictly requires settled research, design, and structure context. Without this prior direction confirmed, the task breakdown cannot accurately define sequencing, risks, or verification strategy.