Feature

Verify the initiative is well-scoped before any plan work begins.

Required elements:

• A specific, unambiguous title
• A one-line summary of the user-visible outcome
• A clear statement of the problem solved or value delivered

If any element is missing or ambiguous, identify the gap and ask
the operator to clarify. Do not advance with an under-specified
initiative.

Decompose the initiative into the minimum set of plans required
to ship it. For each plan, produce:

• Title (action-oriented, 5-10 words)
• Scope (what it includes and what it explicitly excludes)
• Surface area (components, files, or systems it touches)
• Sequencing notes (only if execution order is load-bearing)

Prefer fewer, broader plans over many narrow ones. Present the
decomposition to the operator and request approval before
creating any child tasks.

Create one child task per approved plan, attached to this
initiative as the parent. For each:

• type: plan
• title and summary: from the approved decomposition
• status: backlog (the plan's own workflow takes over from there)

Do not pre-define phases — that is the responsibility of each
plan's workflow. Confirm all plans were created and linked before
advancing.

Plan execution is in progress. This step blocks until every child
plan reaches a terminal state (completed or cancelled).

If a plan stalls or is blocked, address the issue on that plan's
workflow — not here. The gate re-evaluates on each advance attempt.

Validate the initiative as a whole. Individual plans were verified
in isolation; this step confirms they integrate into the outcome
the initiative promised.

Report:

• The user-facing path or scenario exercised
• What worked
• What did not work, and which plan owns the gap

If gaps remain, reject this step. The workflow returns to
execute-plans so the responsible plan can be reopened. Do not
patch the gap inline here.

Request operator approval before advancing.

If anything non-obvious was learned during this task, write it
to:

docs/learnings/{YYYY-MM-DD}-{task-slug}.md

The file is a plain Markdown note. Suggested structure:

• What I learned
• Why it was non-obvious
• What I'd do differently next time

If nothing non-obvious came up, skip this step — do not create
an empty file.

Initiative shipped. Mark it completed and close out.