Install the skill, then say what you want to build.

Install

You need Node.js 22.14 or newer and one coding agent: Claude Code, Codex, Cursor, or Antigravity.

npx @manhquy/flow-skill@next

Current pairing: skill product v0.31.0, npm installer 0.7.1-next.0 on @next. @latest still ships 0.7.0 / skill 0.30.0 until promoted. Do not npm i this package. That does not copy the skill. Do not pin the skill version on npm.

What happens: the installer detects agents, you pick homes, the skill lands (example ~/.claude/skills/flow).

Then restart the agent. Until you restart, the agent does not know the skill exists.

Agent	After restart
Claude Code	type `/flow`
Codex CLI	restart once, then type `$flow`
Cursor	reload the tool, open the flow skill
Antigravity	restart the IDE or `agy`, then `/flow`

Optional: bash ~/.claude/skills/flow/runner/flow.sh doctor should print READY.

--help prints installer and skill versions. They are two numbers. See Two version numbers.

What you get

Three capabilities. The first is true after npx. The next two are true after you walk gates or close a card.

An honest stop. /flow next will not unlock the next stage if the file is empty, fabricated, or scope-laundered. Killing the idea is valid. This is a gate refuse; the agent itself keeps running.
A written plan in your repo, when you walk the gates. Six files under flow/, then cards under cards/. Another session can pick up cold. Those files do not exist after install alone.
Done that means the thing exists. Live URL, CLI that runs, importable API, or a skill that actually ran. Not “tests pass.”

First run — one command, one restart, one check.

npx @manhquy/flow-skill@next
# restart the agent
# in a project directory:
I want to build an inventory app for my shop.
# or type /flow  (Codex: $flow)

Chat is the door. Typed /flow always wins. The concierge asks one consent question, then one next action. Routing is reliable on Claude; on Codex or Antigravity treat chat as best-effort and type the verb. The full caveat lives on Everyday loop.

Success on this page: skill on disk, agent restarted, you said what to build or typed /flow, and the harness answered with status or a next action or a gate result.

Long form, including “Watch a gate refuse”: Install and first run.

Everyday commands

You want	Type
Where am I?	`/flow`
Advance or get blocked honestly	`/flow next`
Cut a build slice	`/flow card`
Prove it exists	`/flow check C-001`
Existing codebase	`/flow assess`
Machine check	`/flow doctor`

Codex uses $flow. Full table: Commands. /flow auto is advanced; see When work must halt.

The flows as jobs

Idea → Research → Scope → PRD → ADR → Contract, then cards, then Retro. File names sit beside the job as flow/00-idea.md … flow/05-contract.md, not as headings.

Contract is the one stage you cannot skip. See Why the contract can never be skipped and When work must halt.

An existing repo starts at /flow assess (Assess a brownfield). Teach vs work is one consent question; gates stay identical (Teach vs work).

Do not inline the full walkthrough here. Walk a full project.

When you are stuck

Resume a cold project → Resume mid-project
Unlock a dead session → Unlock a stale session
Troubleshoot install → If install breaks

Learn more

How the two layers work → The two-layer harness
Why “tests pass” is not done → Done means world-state evidence
When work must halt → When work must halt
Why two version numbers → Two version numbers
Architecture → Three layers
Commands, Glossary, Changelog
Power (auto, attest, extra engines) → Agent orchestration

If you only needed to install and run, you can stop above.