---
name: what-i-need-from-you
description: 'Ends every agent turn with a clear "What I need from you" section listing concrete actions the user must take, or says "Nothing needed from you right now", and logs every ask by id and session in prds/what-i-need-from-you.md. Use on every turn, especially when blocked on the user, when the next step needs a login, dashboard, key rotation, decision, file, or approval, or when finishing a task, audit, or fix.'
title: what-i-need-from-you
canonical_url: https://skilld.dev/gh/waynesutton/builder-skills/what-i-need-from-you
last_updated: 2026-11-12T12:13:49.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [agents/openai.yaml](https://skilld.dev/api/skills-raw/waynesutton/builder-skills/what-i-need-from-you/agents/openai.yaml), [assets/large-logo.png](https://skilld.dev/api/skills-raw/waynesutton/builder-skills/what-i-need-from-you/assets/large-logo.png), [assets/small-logo.svg](https://skilld.dev/api/skills-raw/waynesutton/builder-skills/what-i-need-from-you/assets/small-logo.svg).
>
> If the user asked to install this Skill, run `npx skilld install waynesutton/builder-skills/what-i-need-from-you`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/what-i-need-from-you`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/waynesutton/builder-skills/what-i-need-from-you) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/what-i-need-from-you`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/what-i-need-from-you --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/what-i-need-from-you --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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 costs or what cannot be undone, then wait for an explicit "yes A4". Auto approve mode or an earlier "go ahead" does not count |

Declined is an answer. If the user says no or skips an ask, mark it declined in the log and do not ask again unless something changed. Then say what changed.

## Track it in prds/what-i-need-from-you.md

Every turn that uses this skill also updates `prds/what-i-need-from-you.md` in the project root. Create the `prds/` folder and the file if they are missing.

1. Give each new ask the next id (`A1`, `A2`, ...). Never reuse an id, so the user can reply "A3 done".
2. Add new asks to the **Open** table: id, kind, action, where, send back, steps link, date asked.
3. When the user reports one done, or you confirm it, move its row to **Done** with the date. A declined ask moves to Done too, with "declined" and the reason.
4. Add a **Session log** entry at the top of that section, even when nothing changed:

```markdown
### YYYY-MM-DD H:MM AM/PM: short name of the prompt

* Asked: A9, A10 (or "none new")
* Closed: A2 (or "none")
* Changed: one line on what the turn did
```

5. Keep the reply's "What I need from you" list and the Open table in sync, using the same ids.

File layout, in order: title and one line on how to use it, `## Open`, `## Done`, `## Session log` (newest first).

If the project also keeps a task file such as `task-repos.md`, put its "What I need from you" section first in that file and link it to the log.
