2026-08-25

🎚️ Delivery profiles: pick how much rigor the loop spends

The loop shipped with one speed — the rigor we use on DevStride itself: fine-grained items, deep specs, a wide adversarial review, and a second reviewer re-checking every fix. Right for a revenue-bearing product, wrong for a greenfield one, where a team measured hours per item reviewing code that had no users yet.

Version 0.10.0 makes rigor a choice. A delivery profile is one word that moves the loop's knobs together: how finely a plan is sliced, how deep each spec goes, how wide the adversarial review fans out, how many review rounds run, and which checks gate a merge.

• prototype — fast. One item per vertical slice a user can see, short specs, a narrow review, no second local reviewer, and the release unit merges on its own when its last item lands.
• standard — the new default: the middle a working product wants.
• enterprise — the rigor the loop ran at before.

Floors never move: one maximum-effort adversarial pass per item, the security lens on any auth-boundary diff, a green local gate before merge, and full cloud review plus CI at the release pull request.

🔀 Rebalance a running plan

A plan sliced for enterprise that now needs prototype no longer has to be rebuilt. /devstride:rebalance I1234 prototype re-slices the not-started items, shows a before/after table, and writes nothing until you sign off. Done and In Progress work is untouched; absorbed items are archived with a pointer to their successor, never deleted. It is the eighteenth skill.

⏱️ A bounded review loop

• Local review rounds are capped per profile — none, one, or two per item. Past the cap, remaining findings are fixed without a re-review, and anything that is not P1 or security is deferred with a written rationale.
• Cloud reviewer waits fail fast. A request must be proven registered within two minutes, or the reviewer is dropped and reported. The timeout now bounds only a reviewer that really was asked: 5, 10, or 20 minutes by profile.

What to do

Update the plugin and restart Claude Code:

claude plugin marketplace update devstride
claude plugin update devstride@devstride

Then run /devstride:setup in each repository to pick a profile; it writes "profile" and matching defaults into .claude/ds-config.json. A plan can carry its own — /devstride:plan I1234 prototype — which wins for that plan.

📚 Choose a delivery profile · Rebalancing a plan · Configuration reference