Brief site
Grill a website brief into BRIEF.md — audience, job-to-be-done, constraints, success metrics.From its SKILL.md
npx -y skills add Alfred-Lau/skills --skill brief-siteAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, as published. Nobody here has run it
Brief Site
Sharpen why this site exists until every decision branch is resolved, then write docs/site/BRIEF.md (or the configured site docs root).
Process
1. Load context
Read docs/agents/site-docs.md if present. Read existing BRIEF.md / BRAND.md / repo README. Prefer facts from the repo over asking.
2. Grill
Invoke the site-grilling discipline: one question at a time, recommend an answer each time. Cover at least:
- Primary audience and the job-to-be-done
- Primary conversion / success action
- Must-have constraints (timeline, locales, brand assets, legal, tech)
- Out of scope
- Success metrics (leading + lagging) — qualitative OK if no analytics yet
- Competitive / reference sites (what to learn, what to avoid)
Completion criterion: user confirms shared understanding; no open branches that would change IA or brand.
3. Write BRIEF.md
Use template.md. Keep it short enough to re-read in one minute.
4. Hand off
Tell the user the next skill is usually /brand-voice (or /information-arch if brand is already locked). Offer /ask-site if unsure.