Intent card with a hold rule

The idea

Each request shows the requester what the organization understood and plans to do. Work waits only for high risk, a named approval, an ask-first setting or an open question.

The problem
Requesters could not see a plan before work started, or had to approve everything.
Why it matters
People see each plan, and are asked only when the rule says so.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • Plan source basis and correction holds

    Each plan revision records every source it cited or followed, with its version. A material change sends the plan back once, and consequential actions check their evidence again.

  • Define deeply before building

    Before building, the worker defines what, why, for whom and how. It checks fit, knowledge and authority, and answers its own questions with research and with colleagues.

  • Area notes and knowledge that stays current

    Research writes a note for each package or folder it touches, kept while the files do not change. Facts tied to a page or ticket go stale when it changes, and pushes to the default branch update ties and notes.

  • Request rewrite

    When a worker first picks up an item, one structured model call rewrites the request into a working prompt and a short plan. The worker sees it next to the requester's exact words, and those words win.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.