Genie

Code is a commodity. Harnesses get replaced. Context stays.

  A time-lapsed replay of a real /wish run, host details hidden and agent launch line removed. Its figures are one labelled sample, from its own genie wish report. Full video

Give /wish one decided task. It checks that the task fits, builds it in its own worktree, runs your repository's own check, has an agent that did not write the code review the exact commit, and opens a pull request. Merging stays with you.

Claude Code runs it as /wish, Codex as $wish, and other agents by name. Docs · Skills · Discord

One /wish from a real run, shortened:

How it works

Designs and plans stay in your repository as markdown, with the reviews that approved them, so the next agent you use reads the same context. Each step is a skill. One decided task goes straight to wish. Anything bigger takes the whole loop, where every gate is run by an agent that did not do the work:

brainstorm → design review → wish → plan review → work → implementation review → PR

- brainstorm settles an idea into a DESIGN.md. A design review approves it before any plan is written.
- wish delivers one task end to end and returns a pull request ready for you to merge. Work bigger than one task becomes a WISH.md with execution groups, and a plan review approves it before anything is built.
- work runs the approved groups in dependency order, each with its own scoped worker, and ends at an implementation review.
- review runs those reviews. After work, it checks the result against the plan's criteria and returns SHIP, FIX-FIRST or BLOCKED. fix repairs the blocking gaps with bounded retries and a fresh reviewer.
- council sits beside the loop. It pressure-tests a decision through independent lenses and changes nothing.

Designs, plans and verdicts…