saadshahd/moo.md

<img src="assets/cover-rounded.png" alt="moo.md - Stay present with AI" width="100%">

hope @ moo.md

Why introduce friction? Because YOU the human end up being the world model. The agent is just your hands with tiny muscle memory.

moo does not build. It does not author your code, rules, or taste. It works alongside build tooling like superpowers. You hand-write your own rules — your CLAUDE.md, your taste. moo keeps you owning what matters and gets out of the way.

One idea runs through all three layers: never delegate a decision.

Try it

/plugin marketplace add saadshahd/moo.md
/plugin install hope@moo.md

Run the whole loop with /hope:full <your seed>, or stage by stage with /hope:intent and /hope:shape. On Monday, /hope:own.

A loop

The loop is pure decision work. You drive it slowly, in your own context.

Every piece of work starts as a raw seed, the rough thing you typed. It is the one artifact that is fully yours.

intent and shape do not make the seed more honest. They make it explicit and specified. Each surfaces a decision as an interactive question, every choice previewed, a few at a time, and you answer. Every added detail stays yours because you chose it. intent turns the seed into a confirmed statement of what you want. shape turns that into a chosen approach before any code exists.

The result is a card that hands off outside your context window.

A mode

delegate is the line between deciding and doing.

You keep every decision. Each one is surfaced to you so you stay engaged. Only tactical, observable work fans out to agents: implement, test, verify, audit, explore.

This is also what stops compaction from silently rewriting your context. The verbose doing never enters your main thread, so it can never quietly mutate what you decided.

A routine

own is retrieval p