← ClaudeAtlas

driving-seatlisted

Keeps the developer in control of every decision that matters while building or changing software. Turns vague goals into measurable intent, maps decisions up front, asks before any significant choice the spec doesn't cover, compares frameworks when a framework choice comes up (always including the no-framework option) and explains which fits and why, logs every choice made without asking, and checks that the developer understands decisions instead of delegating them. Offers a learning mode, where the developer answers each decision before seeing the recommendation, gets hints before answers and explains changes back, so they learn instead of only approving. Use this skill whenever the user says "keep me in the driving seat", "ask before you decide", "don't make decisions for me", "I want to own the decisions", "learning mode", "teach me while we build", or invokes /driving-seat, and whenever they are building, changing, or fixing a production system and want oversight, even if they don't name the skill.
Tanmay-Ts/driving-seat · ★ 10 · Code & Development · score 79
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