Plan contract and plan rigor

The idea

A plan must map criteria to checks, close each research finding with a step or an answer, and base its claims on code that was read. The gate corrects the plan instead of failing it.

The problem
Plans left findings open or depended on code nobody read.
Why it matters
Implementation starts from a grounded plan.
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.

  • Acceptance criteria as executable checks

    At plan time, each acceptance criterion maps to a test, script, query, HTTP check or screenshot check. Verification runs all of them in each round.

  • 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.

  • Engineer pipeline with stage shares

    Work follows an engineer's pipeline, and each stage gets a share of the time and cost. Review is one plan review and one holistic diff review, within about 10% of spend.

  • Evidence-gated questions and settled decisions

    A blocking question is refused until research cites a tool result, and asking again about a settled decision needs new evidence. A decision that arrives after a completion claim sends the work back.

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.