brief-builder
Interview the user with sharp, one-at-a-time questions to turn a vague request into a tight, complete brief any other skill can run on. Use when a request is fuzzy, under-specified, or 'help me think this through', or before running a skill that needs inputs the user hasn't given. Produces a structured brief (goal, audience, constraints, success criteria) and hands off to the right skill — by interrogating, not guessing.
npx skills add mohitagw15856/pm-claude-skills --skill brief-builder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Brief Builder Skill Most weak AI output comes from a weak brief — the model guessed at context instead of getting it. This skill flips that: it **interviews** the user with focused questions, *one or two at a time*, following up where answers are thin, until it has enough to produce excellent work. Then it writes the brief and hands off. The whole value is asking the right questions in the right order — not producing on the first vague sentence. ## Required Inputs - **The raw ask** — whatever the requester actually said, however vague ("we need a dashboard", "marketing wants a one-pager"). Verbatim beats paraphrased; the gaps in their words are the interrogation map. - **Who is asking and who will consume the output** (if known) — the same ask from a CEO and an intern needs different briefs. - Optional: any prior artifacts the ask relates to (the doc being replaced, the thread that sparked it). ## How to run this skill (the interrogation loop) 1. **Read what they gave you** and identify the *task type* (a launch? a doc? a decision? a piece of copy?). 2. **Ask the smallest set of high-leverage questions first**, ONE or TWO at a time — never a 20-question wall. Lead with the questi
- Required Inputs
- How to run this skill (the interrogation loop)
- The question backbone (adapt to the task)
- Output Format
- 1. The questions (interactive)
- 2. The brief (once enough is gathered)
- 3. Handoff
- Quality Checks
- Anti-Patterns
- Based On
What does the brief-builder skill do?
Interview the user with sharp, one-at-a-time questions to turn a vague request into a tight, complete brief any other skill can run on. Use when a request is fuzzy, under-specified, or 'help me think this through', or before running a skill that needs inputs the user hasn't given. Produces a structured brief (goal, audience, constraints, success criteria) and hands off to the right skill — by interrogating, not guessing.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill brief-builder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.