vawe-brieflisted
Install: claude install-skill vawe-hq/skills
# vawe-brief: the interview, then the brief
When you talk to the person, use plain words: describe what the viewer sees, not the harness terms (map: harness/lib/plain-words.mjs).
Run this skill inside a vawe checkout (`AGENTS.md`, `taste/`, `bin/vawe`). With none, get one: `git clone https://github.com/vawe-hq/vawe.git && cd vawe && npm install && bin/vawe-dev doctor`.
A thin request makes a thin film. Ask the person for the missing details once, at the start, then write the brief. Once the Board is filled, show the plan and end with "If you like it, type /vawe-approve".
## 0. Ask for the details
```bash
bin/vawe new <name> --request "<the ask>" --questions-json
```
This writes nothing. It prints the open details as `calls`, each call at most 4 questions in the shape of
the AskUserQuestion tool (required details first). The list is `DETAILS` in `harness/lib/measured-brief.mjs`.
Call AskUserQuestion once per call, in order, with that call's `questions` as given. Map each answer (the chosen label without "(Recommended)", or the "Other" text) to a `key: value` line in an answers file, the key being the header in lower case. Then run `bin/vawe new <name> --request "<the ask>" --answers <file>`.
If the person answers "you decide", or no person is there (hill-climb, CI), run `bin/vawe new` with `--defaults`: it guesses each open detail and names which.
When the request is thin, add one more call before the answers file: offer 2 or 3 ideas for the key beat as one AskUserQuest