Brief Me — Pre-Build Requirements Interview

Ask an agent to "build me a landing page" and it quietly guesses the audience, the value proposition, and the goal from thin context — guesses you never actually confirmed, and that quality varies with however much you happened to type in the prompt. This skill surfaces those guesses as explicit questions up front, in one short structured interview, and hands off the answers as a durable file instead of a paragraph that gets lost in the conversation. Works the same way whether you're defining a marketing website, a web app screen, or a mobile/product UI — the very first question is simply "what kind of site or app is this."

What it does

• Asks about site/app type, target audience, and the core value proposition
• Follows up with a persona-level question (age range, income level, occupation, life stage) — not just a broad B2C/B2B label
• Asks about competitive differentiation, scale, device priority, and existing brand assets — whichever apply, skipping what clearly doesn't (e.g. no "scale" question for a single-page pitch)
• Asks the conversion goal and any open-ended notes or constraints (tone, things to avoid, accessibility needs)
• Writes everything to BRIEF.md in your project root, in whatever language you're using in the conversation

How it works

1. Four rounds of interview questions — four questions, then one, then up to four, then one — each with concrete options plus an open "Other" field
2. This is a one-shot interview, not a back-and-forth grilling session
3. The answers are synthesized into a structured BRIEF.md
4. It stops there — it does not chain into any other skill automatically

Tip: more detail in, sharper brief out

You don't need to answer from a blank slate. Paste in a rough business description — even one unstructured paragraph — and the skill turns it into concrete multiple-choice options with a recommended pick for each question, so most of the interview becomes confirming inferences rather than typing from scratch. The more specifics you give it upfront (numbers, competitors, a target age range), the sharper its questions get and the more useful the resulting BRIEF.md is.

What it is not

It does not ask design-style questions (colors, fonts, layout) — that belongs to whatever mockup or build step comes next. This skill stays one level above, at the business-requirements level, and produces exactly one file.

Requirements

None beyond a Claude Code agent. No local file access beyond writing BRIEF.md to the project root, no network calls, no other skills required. Works standalone in any project.

Works well with

BRIEF.md is a plain Markdown file — hand it to whatever mockup-building, scaffolding, or coding workflow you use next. Many agentic build workflows will pick up a BRIEF.md sitting in the project root on their own; otherwise just reference or paste it in as context. This skill can also be called by your own orchestrator skill if you want to pipe the interview answers directly into a project-setup step instead of writing the file (see "Orchestrated mode" in SKILL.md).

More from KMRVID

The full Claude Code skill bundle for Figma, Tailwind and Astro workflows is available on Gumroad: https://gaspanik.gumroad.com/l/kmrvid-claudeskills