obra/superpowers

Before Network or broad shell → After Network or broad shell

2ce8aa15d05b → 22f0b463e7a5

+ 34 If nothing is open when you write your first message and there's one
+ 35 sensible way, steps 1 to 3 happen in that message (see Your First
+ 36 Message).
+ 37 
- 45 project or their context already answers.
+ 49 project or their context already answers, or reopen what they've
+ 50 already decided.
- 61   corrections, then one question about what they want: the thing their
- 62   request leaves open whose answer would most change what gets built.
+ 66   corrections. Then, if they haven't told you why they want it, even if
+ 67   you can guess, ask about that: one open question in their own terms,
+ 68   with nothing to pick from. If they have told you, and their request
+ 69   and the project leave open something whose answer would change what
+ 70   gets built, ask about the one that would change it most; when its
+ 71   choices can be named, sketch each concretely, with what it trades off
+ 72   and which you'd pick. If nothing like that is open, there's one
+ 73   sensible way: end with the short design itself (the approach, a line on
+ 74   why the others don't fit, and the design in a few lines) and ask them
+ 75   to approve it. Their approval covers the approach and the design: write
+ 76   the short design doc as approved and go on to the plan.
- 75   design discussion): end with your question. They want this
- 76   conversation.
- 77 - **They didn't:** they may not want a conversation at all. After your
- 78   question, add a light, one-line offer to just get going instead, like
+ 89   design discussion): end there. They want this conversation.
+ 90 - **They didn't:** they may not want a conversation at all. End with a
+ 91   light, one-line offer to just get going instead, like
- 88 Each message ends with one question: a single sentence with no list of
- 89 example answers hanging off it. Use plain language, pitched just a little
- 90 above where your human partner is. Match their vocabulary; never use
- 91 process jargon. You never need to quote this skill to your human
- 92 partner.
+ 101 Ask a question only when the answer would change what gets built and
+ 102 neither the request nor the project answers it. Otherwise, state your
+ 103 call and your reason as a proposal they can correct, and move the work
+ 104 forward. Process steps are always your calls: writing things up, where
+ 105 files go, looking further, how to show something. Do them and say so.
+ 106 Ask one at a time. Use plain language, pitched just a little above where
+ 107 your human partner is. Match their vocabulary; never use process jargon.
+ 108 You never need to quote this skill to your human partner.
- 98 **Get them describing.** Open questions come first. Their own words carry
- 99 intent that your options can't. Offer a short menu only when they're
- 100 stuck. When they say "just guess" or "what do you think?", propose
- 101 something concrete.
+ 114 **Get them describing.** Until you know why they want it, ask open
+ 115 questions, with no example answers attached. Their own words carry
+ 116 intent that your options can't. Once you know why, when a decision has
+ 117 choices you can name, sketch each concretely, with what it trades off
+ 118 and which you'd pick. When they say "just guess" or "what do you think?",
+ 119 propose something concrete.
- 105 libraries for an app; the medium for a piece of art. Find out early which
- 106 of those choices they want to make, which they're handing to you, and what
- 107 they already have to work with. Someone with strong views or skills will
- 108 want to talk it through. Someone counting on you needs sensible defaults,
- 109 said in plain words. When there's existing work, build on what it already
+ 123 libraries for an app; the medium for a piece of art. Read from how they
+ 124 talk which of those choices they want to make. Someone who raises the how
+ 125 or asks about trade-offs wants the options with your pick. Someone who
+ 126 talks about outcomes is handing you the how: make those calls and state
+ 127 each in a line. When there's existing work, build on what it already
- 134 **Offer recon.** Once you have a bit of grounding and looking further
- 135 would help, offer to go look: deeper into their codebase or project,
- 136 their own files and data, or the web. Say what you'd look for. They
- 137 decide whether you go.
+ 152 **Do recon.** Once you have a bit of grounding and looking further
+ 153 would help, go look: deeper into their codebase or project, their own
+ 154 files and data, or the web. Say what you looked for and what you found.
- 143 existing work rules out. Present the two or three that remain, grounding
- 144 each in what the project actually does and saying what it trades off.
- 145 Recommend one and say why, then ask which way they want to go. When
- 146 there's genuinely one sensible way, say so and explain why the others
- 147 don't fit. This is for how it gets built; for what they want, get them
+ 160 existing work rules out. Sketch the two or three that remain concretely
+ 161 enough to picture, grounded in what the project actually does, with what
+ 162 each trades off. Recommend one and say why, then ask which way they want
+ 163 to go; if they've handed you the how, say you'll go with your pick
+ 164 instead. When there's genuinely one sensible way, say so in that
+ 165 message and explain why the others don't fit; the design comes in the
+ 166 next one. This is for how it gets built; for what they want, get them
- 150 **Show, don't tell.** Offer the visual companion (below) whenever seeing
- 151 would help more than reading:
+ 169 **Show, don't tell.** Whenever seeing would help more than reading,
+ 170 sketch it in text: a few lines of what they'd see. Offer the visual
+ 171 companion (below) when the look itself is theirs to decide:
- 183 look at, like a page, a screen, a schedule, or a printout? If so, and
- 184 they haven't seen the visual companion offer yet, send the offer instead
- 185 (its own message, below) and hold the chunk for the next message. Once
- 186 they've accepted, put a mockup next to the description.
+ 203 look at, like a page, a screen, a schedule, or a printout? If so, put a
+ 204 text sketch next to the description. If the look itself is theirs to
+ 205 decide and they haven't seen the visual companion offer yet, send the
+ 206 offer instead (its own message, below) and hold the chunk for the next
+ 207 message. Once they've accepted, put a mockup next to the description.
- 226 Otherwise, ask. Your human partner's preferences override both.
+ 247 Otherwise, pick a sensible place and say where. Your human partner's
+ 248 preferences override both.
- 269 | "I've answered their questions, so I'll write the doc" | Lay out the approaches first, in a message of their own. |
+ 291 | "I've answered their questions, so I'll write the doc" | Lay out the approaches first, in a message of their own (or, when nothing was open from the start, in your first message's short design). |

Compare on GitHub

Before Not checked yet → After Network or broad shell

First observation → 2ce8aa15d05b

No earlier version was observed for comparison.

Compare on GitHub

Before Network or broad shell → After Network or broad shell

2ce8aa15d05b → 22f0b463e7a5

Compare on GitHub

Before Not checked yet → After Network or broad shell

First observation → 2ce8aa15d05b

No earlier version was observed for comparison.

Compare on GitHub

Before Instructions only → After Instructions only

2ce8aa15d05b → 22f0b463e7a5

Compare on GitHub

Before Not checked yet → After Instructions only

First observation → 2ce8aa15d05b

No earlier version was observed for comparison.

Compare on GitHub

Before Local scripts → After Local scripts

2ce8aa15d05b → 22f0b463e7a5

- 126   `../subagent-driven-development/scripts/sdd-workspace PLAN_FILE` — it
+ 126   `../subagent-driven-development/scripts/sdd-workspace PLAN_FILE` by its
+ 127   absolute path, from the working tree you're executing in — it
- 172 - Run this skill's `scripts/task-start PLAN_FILE N`. It prints the brief
+ 173 - Run this skill's `scripts/task-start PLAN_FILE N` by its absolute path,
+ 174   from the working tree you're executing in. It prints the brief
- 225 with the test command the brief names for the whole task. It runs the
+ 227 by its absolute path, from the working tree you're executing in, with the test command the brief names for the whole task. It runs the
- 237 (MERGE_BASE = the commit the branch started from, e.g.
+ 239 by its absolute path, from the working tree you're executing in (MERGE_BASE = the commit the branch started from, e.g.

Compare on GitHub

Before Not checked yet → After Local scripts

First observation → 2ce8aa15d05b

No earlier version was observed for comparison.

Compare on GitHub

Before Instructions only → After Network or broad shell

2ce8aa15d05b → 22f0b463e7a5

Compare on GitHub

Before Not checked yet → After Instructions only

First observation → 2ce8aa15d05b

No earlier version was observed for comparison.

Compare on GitHub

Before Instructions only → After Instructions only

2ce8aa15d05b → 22f0b463e7a5

Compare on GitHub

Before Not checked yet → After Instructions only

First observation → 2ce8aa15d05b

No earlier version was observed for comparison.

Compare on GitHub

Before Instructions only → After Network or broad shell

2ce8aa15d05b → 22f0b463e7a5

Compare on GitHub

Before Not checked yet → After Instructions only

First observation → 2ce8aa15d05b

No earlier version was observed for comparison.

Compare on GitHub

Before Network or broad shell → After Network or broad shell

2ce8aa15d05b → 22f0b463e7a5

- 114   `bash scripts/sdd-workspace PLAN_FILE` — it prints the plan's git-ignored
+ 114   `bash scripts/sdd-workspace PLAN_FILE` by its absolute path, from the
+ 115   working tree you're executing in — it prints the plan's git-ignored
- 203   `bash scripts/task-brief PLAN_FILE N` — it extracts the task's full text to a
+ 204   `bash scripts/task-brief PLAN_FILE N` by its absolute path, from the
+ 205   working tree you're executing in — it extracts the task's full text to a
- 241 **DONE:** Generate the review package (`bash scripts/review-package PLAN_FILE BASE HEAD`, from this skill's directory — it prints the unique file path it wrote; BASE is the commit you recorded before dispatching the implementer — never `HEAD~1`, which silently drops all but the last commit of a multi-commit task), then dispatch the task reviewer with the printed path.
+ 243 **DONE:** Generate the review package (`bash scripts/review-package PLAN_FILE BASE HEAD` by its absolute path, from the working tree you're executing in — it prints the unique file path it wrote; BASE is the commit you recorded before dispatching the implementer — never `HEAD~1`, which silently drops all but the last commit of a multi-commit task), then dispatch the task reviewer with the printed path.
- 260   `bash scripts/review-package PLAN_FILE BASE HEAD` and pass the reviewer the file path
+ 262   `bash scripts/review-package PLAN_FILE BASE HEAD` by its absolute path, from
+ 263   the working tree you're executing in, and pass the reviewer the file path

Compare on GitHub

Before Not checked yet → After Network or broad shell

First observation → 2ce8aa15d05b

No earlier version was observed for comparison.

Compare on GitHub

Before Local scripts → After Network or broad shell

2ce8aa15d05b → 22f0b463e7a5

Compare on GitHub

Before Not checked yet → After Local scripts

First observation → 2ce8aa15d05b

No earlier version was observed for comparison.

Compare on GitHub

Before Instructions only → After Network or broad shell

2ce8aa15d05b → 22f0b463e7a5

Compare on GitHub

Before Not checked yet → After Instructions only

First observation → 2ce8aa15d05b

No earlier version was observed for comparison.

Compare on GitHub

Before Instructions only → After Network or broad shell

2ce8aa15d05b → 22f0b463e7a5

Compare on GitHub

Before Not checked yet → After Instructions only

First observation → 2ce8aa15d05b

No earlier version was observed for comparison.

Compare on GitHub

Before Instructions only → After Instructions only

2ce8aa15d05b → 22f0b463e7a5

Compare on GitHub

Before Not checked yet → After Instructions only

First observation → 2ce8aa15d05b

No earlier version was observed for comparison.

Compare on GitHub

Before Instructions only → After Instructions only

2ce8aa15d05b → 22f0b463e7a5

Compare on GitHub

Before Not checked yet → After Instructions only

First observation → 2ce8aa15d05b

No earlier version was observed for comparison.

Compare on GitHub

Before Instructions only → After Network or broad shell

2ce8aa15d05b → 22f0b463e7a5

Compare on GitHub

Before Not checked yet → After Instructions only

First observation → 2ce8aa15d05b

No earlier version was observed for comparison.

Compare on GitHub

Before Local scripts → After Network or broad shell

2ce8aa15d05b → 22f0b463e7a5

Compare on GitHub

Before Not checked yet → After Local scripts

First observation → 2ce8aa15d05b

No earlier version was observed for comparison.

Compare on GitHub