Define deeply before building

The idea

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.

The problem
Agents start building before they understand the request.
Why it matters
Plans start from a written definition, with at most one question to the requester.
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 contract and plan rigor

    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.

  • Intent card with a hold rule

    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.

  • Typed requests in every direction

    Workers and people ask each other typed questions (review, information, decision, help, handoff) peer to peer, up or down, with due times, defaults, redirects and an inbox.

  • Authority ladder: the owner is the last resort

    A question goes to the asker's manager worker, then the CEO, which decides from the org profile and record; a person gets it only for an owner reason, and their answer becomes a precedent.

  • Delegation down the chain with fan-out

    A manager splits work into parts, creates every child in one transaction with dependencies, and waits once for all of them.

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.