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
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.
npx skills add gaboesquivel/flow-skills -s reviewNatural language is the interface. Any of these, or your own words, reach the skill.
A fresh-context review through flow-reviewer on top of /code-review, with requirement verdicts, scope, glossary, and DESIGN.md checks. Writes fixes for confirmed defects; "review only" writes nothing.
The authoritative, versioned instruction your agent follows, from skills/review/SKILL.md.
"Review it" gets an independent read and ends in repaired work: confirmed defects fixed and verified, or left unresolved with the reason. The author is never the reviewer. A spec's proof is a verdict on each acceptance scenario step (satisfied, unmet, or unresolved), each with evidence.
Claude Code's /code-review hunts bugs and /security-review checks trust boundaries. The plugin's flow-reviewer agent runs them and adds Flow's checks. Without that agent or /code-review, run these steps yourself and label the review single-agent.
build's Size guard picks the tier from the change, never its author, for a standalone "review it" too; "deep review" runs Deep. Tiers map to /code-review levels: Quick → low, Standard → medium, Deep → high.
Scope: the working tree by default, or a branch, pull request, or spec. Run flow-reviewer with head, tier, and spec or request. It adds:
unresolved, and unmet is Importantbuild's Scope guardGLOSSARY.md, flagging a missing entry only when it creates a meaningful ambiguity or naming inconsistencyPRODUCT.md, DESIGN.md, ARCHITECTURE.md, or GLOSSARY.md states, compare it with that statementDESIGN.md and UI basics when the diff changes UI, including material experiential defects (a missing loading, empty, or error state) seen in the rendered result; a whole-journey walk is experience'sBe able to explain the consequential choices the change made. Findings cite file:line: Important (blocks), Nit (at most three), or Pre-existing (never blocks).
Fix each Important finding and unmet step on the branch, covering its whole bug class, with a check that fails without the fix when the bug could return unnoticed. Answer every other finding: fixed, or resolved with reason. "Review only" or "don't fix" stays read-only. Inside build, the main thread repairs. A re-review covers only the new diff and never repeats a finding. After three rounds with an Important finding open, stop patching and rethink the approach; fix a recurring finding at its source (a lint rule, skill, or AGENTS.md).
A count ("2 Important, 1 Nit"), then scenario verdicts, findings by severity, repairs, and open items. On GitHub, post it as a comment, never an approval.
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
Break a plan, spec, or conversation into verifiable vertical-slice tasks with blockers, listed in the spec's Tasks checklist.
Say “break it down”
Delivery
Implement an authorized change on a branch, then review, fix, check, and confirm the branch is live, without merging.
Say “build 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”