Team pipeline profile and layered preferences

The idea

Onboarding proposes how the team works (design first, test first, trunk, approvals, strict paths, stage shares), with a backtest over 30 merged PRs. Accepted settings resolve in layers, with the person's own layer on top.

The problem
One fixed pipeline does not fit every team, and defaults overrode what people chose.
Why it matters
The runtime follows the team's accepted process, and the person's own way wins.
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.

Where it lives in the product

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

  • Learning from the person's own AI history

    A person imports their own transcripts, files, commits and messages. Traits they accept steer briefs, checks and voice. History they bind to one repository becomes facts, decisions and documents that they confirm.

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.