The core loop

You only need to remember one command:

/hyperpower:build "a habit tracker with streaks"

That's it. Everything else runs when a step needs it. You don't call the planner, the reviewer or the checks yourself.

What comes back is a feature, the changed files as they are written, and a table of checks. That table is the part to learn to read:

  types    pass       0.4s
  unit     pass       2.1s
  lint     fail       0.9s
  prose    fail       0.1s
Gates  2 passed, 2 failed, 0 did not run

Warned  2

Three outcomes, and the third is the one worth knowing:

Result	Means
pass	the command ran and succeeded
fail	the command ran and failed
did not run	nothing was checked. Never a pass.

did not run is the one most tools get wrong. A missing linter, a timeout, a tool that is not installed: all of them report did not run rather than quietly passing. If you see it, something needs installing or configuring, and nothing about that check has been verified.

Under Warned, a check failed but did not stop the run. Under Failed, it stopped. Which is which is yours to set, per check, in hyperpower.yml.