Menu

Individual skill

brief-builder

0upvotes

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.

skills/brief-builder/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,537
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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)
Back to top