Delivery
explore
Talk through a product, feature, or plan as a product-engineering partner who knows the project's goals and constraints, weighs what already exists, and helps decide what is worth building and how you will know.
Say “explore this”
Delivery · Portable skill
Break a plan, spec, or conversation into verifiable vertical-slice tasks with blockers, listed in the spec's Tasks checklist.
npx skills add gaboesquivel/flow-skills -s to-tasksNatural language is the interface. Any of these, or your own words, reach the skill.
Vertical-slice tasks with blockers and an area each, and the ready set. Writes the spec's Tasks checklist.
The authoritative, versioned instruction your agent follows, from skills/to-tasks/SKILL.md.
Break a plan, spec, or conversation into tasks: independently verifiable vertical slices, each naming the tasks that block it. Outcomes, dependencies, and integration cost set the count, never a target: a first MVP may need several tasks, a small change one. Split where a slice can be demonstrated alone, needs separate review, or would not fit one session; never per layer, file, or step.
app/notes when nothing else in app changes), including routes outside its main package; build keeps concurrent work apart by area, so disjoint areas must mean disjoint changes.Wide refactors no vertical slice can land green use expand–contract: add the new form; migrate call sites in green batches by package, each blocked by the expand; remove the old form, blocked by every batch. Batches that cannot stay green alone share an integration branch and a final verify task.
"Break it down" authorizes writing the spec's Tasks section without approval, one line per task, committed on the spec's branch:
- [ ] NN: Title. Area: a, b. Blocked by: NN.
Omit Blocked by when none. Add one indented sentence only when the title cannot say what to build. The spec's Acceptance holds the checks. Without a spec, write one with to-spec first or return a labelled local draft. Keep paths and code out of task text.
Task issues open only when asked: one per task from the issue template, blockers linked once every number exists, and (#N) appended to each line. Say when they are public; on a retry, open only the missing ones.
Tasks are not pull requests or worktrees; build groups them. Report where the tasks live and the ready set, then wait for "build it".
<issue-template>
Its link, if any.
Area: as in the checklist line.
The end-to-end behaviour, from the user's side.
</issue-template>
Delivery
Talk through a product, feature, or plan as a product-engineering partner who knows the project's goals and constraints, weighs what already exists, and helps decide what is worth building and how you will know.
Say “explore this”
Delivery
Turn the conversation into a numbered draft spec using project conventions, and accept it when approved.
Say “spec it”
Delivery
Implement an authorized change on a branch, then review, fix, check, and confirm the branch is live, without merging.
Say “build it”
Delivery
Review work in a fresh context against intent, the spec, and root context, on top of /code-review, and repair confirmed defects; "review only" stays read-only.
Say “review it”
Delivery
Land work on the default branch without asking: build and verify it first when needed, then merge and check the shipped commit is live; or push a branch with no pull request.
Say “ship it”