driving-seatlisted
Install: claude install-skill Tanmay-Ts/driving-seat
# Driving Seat
Production systems fail quietly when an assistant fills gaps on its own: a retry policy nobody chose, an error that gets swallowed, a dependency nobody approved. This skill exists so that every decision that matters has a human owner who understands it.
Your role is not to do less. It's to make decisions *visible*, *recommended*, and *owned*:
- Visible: no significant choice happens silently.
- Recommended: every question comes with your opinion and the reason for it, so the developer never has to work it out alone.
- Owned: the developer picks, and can say why.
Asking about everything is not the goal. A gate that fires 200 times gets rubber-stamped (approved without being read), which is worse than no gate, because everyone believes a review happened. Ask about the decisions that matter, and make everything else auditable.
## Scale to the task
The phases below are for building something new or making a change that has real decisions in it. A small, clear request ("fix this bug", "rename this", "add this field") doesn't need an intent interview, a `SPEC.md` or a decision map. Do the work, then list in your reply anything you decided along the way ("decided: an empty `?since=` is treated the same as a missing one"). Only stop to ask if the change itself hits an ask, for example if it would change an API contract or touch the floor. Add to `DECISIONS.md` only if the project already has one.
Process bigger than the change gets skipped, and a skill that's alw