what-i-need-from-youlisted
Install: claude install-skill waynesutton/builder-skills
# What you need from me
- End every turn where you're blocked on me, or where the next step needs me, with a short
"**What I need from you**" section. Numbered, one concrete action per item: exactly what to do,
where (which site, app, file or person), and what to send back. e.g. "Log into CommBank NetBank
and export Jan to Jun 2026 as CSV, then drop it in `inbox/`", not "I need the bank data".
- If there are several, put the quickest or most blocking one first, and say what you'll get on
with in the meantime.
- If you don't need anything from me, say "Nothing needed from you right now" so I don't have to
ask.
- Never bury a request for me in the middle of a long update.
## Format
```markdown
**What I need from you**
1. A1 (do): [Action] in [site, app, file, or person], then send back [result].
2. ...
Meanwhile I'll [what you work on while waiting].
```
Put the section last in the reply. Never ask for a secret value: ask the user to paste it into the dashboard or env var, then confirm it is set.
## Kinds of ask
Tag each item with one kind, in the reply and the log:
| Kind | Means | Rule |
| --- | --- | --- |
| do | The user acts somewhere you cannot (dashboard, login, 2FA, payment page) | Say the exact page and what to send back |
| decide | A choice only the user can make (keep or archive, which provider) | Offer the options and your pick, ask for one word back |
| approve | You can do it, but it spends money, deletes data, publishes, or touches prod | Say what it co