Feature
Deliver features from requirements to reviewed release. The AI drives through Capture, planning, execution, and Verify.
the steps, as stored
- 01Capture
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.
- 02Define Plansapproval gateagent: planner
Decompose the initiative into the minimum set of child work items required to ship it. Types are semantic, not structural — most substantial work becomes a plan (which elaborates into phases), but a small, self-contained item can be a direct task or bug child of the initiative with no plan wrapper. Pick the type that matches the work. For each item, produce:
- Title (action-oriented, 5-10 words) - Type (plan for work that needs its own phases; task/bug for a small, directly executable item) - 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.
- 03Create Plansagent: planner
Create one child task per approved work item, attached to this initiative as the parent, using the type chosen at define-plans:
- type: plan for work that will elaborate into its own phases; type: task or bug for a small, directly executable item - title and summary: from the approved decomposition - status: backlog (each child's own workflow takes over from there)
For plans, do not pre-define phases — that is the responsibility of each plan's workflow. Confirm all children were created and linked before advancing.
- 04Execute Plansgated
Execution is in progress. This step blocks until every child (plan, task, or bug) reaches a terminal state (completed or cancelled).
If a child stalls or is blocked, address the issue on that child's own workflow — not here. The gate re-evaluates on each advance attempt.
- 05Verifyapproval gateagent: reviewer
Validate the initiative as a whole. Individual children 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 child owns the gap
If gaps remain, reject this step. The workflow returns to execute-plans so the responsible child can be reopened. Do not patch the gap inline here.
Request operator approval before advancing.
- 06context-capturefragment
- 07Completecontext gate
Initiative shipped. Mark it completed and close out.
use it for
- Ship a dark-mode toggle from spec to verified release
- Add CSV export end to end — capture, build phases, review, verify
- Build a notification system with sign-off before the plans execute
without it, with it
| without | with feature |
|---|---|
| Requirements live in a Slack thread; the build starts before anyone agrees on scope | The AI drives through Capture first, then pauses at an approval step so you sign off on the plan before any code is written |
| Nobody can reconstruct why a feature shipped the way it did | Every step — Capture, plans, execution, Verify — is logged automatically, so the audit trail is already there |
| Each engineer delivers features a different way, with different gaps | The AI drives the same six-step process every time, and child work must finish before the feature closes |