product-brief
Skill12 starsChanged 48 days agoMITView on GitHub
Write docs/product/PRODUCT-BRIEF.md by reverse-engineering the approved prototype — every screen, the flow as actually clicked, and the gaps the prototype implied but never showed (empty states, errors, permissions, offline). Runs at WIZARD stage 4.1, after BP v0.0.2 and after a prototype direction is approved in Phase 3. Use when the user asks "o que exatamente a gente vai construir?", "quais telas o MVP tem?", "o que fica de fora?".
10 other projects use a version of this.
Adopted by
Most recently taken up by
- Job-Yang/jobbyang-ai-skillstheir own version, first seen Nov 6, 2026
- Job-Yang/jobyang-ai-skillstheir own version, first seen Nov 6, 2026
- MarkTripoli/skillstheir own version, first seen Nov 1, 2026
- vindreshsingh/engineering-skillstheir own version, first seen Oct 20, 2026
- rterakedis/leanwheel-skillstheir own version, first seen Oct 17, 2026
- emotixco/claude-skills-foundertheir own version, first seen Oct 7, 2026
Used with
Projects with it also use setup.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
VercelSkillsetup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- emotixco/claude-skills-founder★ 796same name
- davekilleen/Dex★ 509same name
- Job-Yang/jobbyang-ai-skills★ 100same name
- Job-Yang/jobyang-ai-skills★ 100same name
- MarkTripoli/skills★ 2same name
- rterakedis/leanwheel-skills★ 2same name
- tolgalogy/agentic-development-framework★ 2same name
- erik-kroon/skills★ 1same name
- philpalmieri/engineering-manager-skills★ 1same name
- vindreshsingh/engineering-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- business-plan-impact-reviewSkill
- codemapSkill
- cost-watchdogSkill
- daily-standupSkill
- decision-logSkill
- deploy-vercel-supabaseSkill
- feature-scaffoldSkill
- first-100-usersSkill
- grow-sustainablySkill
- multi-ai-reviewSkill
- os-self-testSkill
- pitchSkill
- plain-portuguese-explainerSkill
- privacy-auditSkill
- processizeSkill
- project-genesisSkill
- prototype-labSkill
- registry-pickSkill
- release-checkSkill
- research-wavesSkill
- rollback-safeSkill
- secrets-disciplineSkill
- secrets-scanSkill
- sprint-managementSkill
- sprint-roadmapSkill
- usage-monitorSkill
- verify-build-worksSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use after BP v0.0.2 is accepted and a prototype direction has been approved in Phase 3.
- Very specific: line 12
Create docs/product/PRODUCT-BRIEF.md as the operational product document.
- Distinctive: line 20
Every screen in the approved prototype appears in the brief, or is explicitly marked as cut.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Brief Skill
Runs at Phase 4.1 of WIZARD.md.
Use after BP v0.0.2 is accepted and a prototype direction has been approved in Phase 3.
Create docs/product/PRODUCT-BRIEF.md as the operational product document. Not investor copy — that is the Business Plan's job.
Method: reverse engineering, not invention
The product was designed in Phase 3. This skill reads docs/product/DESIGN-DIRECTION.md and prototype-lab/<chosen>/ and writes down what is already there.
Required checks:
- Every screen in the approved prototype appears in the brief, or is explicitly marked as cut.
- The user flow section matches the flow that was actually clickable in the prototype.
- UX tone is derived from
DESIGN-DIRECTION.md, not invented. - Anything the prototype implied but never showed — empty states, errors, permissions, offline, edge cases — is listed as a gap, not silently filled in.
That last check is the reason the prototype comes first. A written spec invents its own completeness; a prototype makes the holes visible.
Contents
One-liner, personas, jobs to be done, user flows, MVP, Phase 1, Phase 2, non-goals, activation moment, retention loop, monetization logic, trust/compliance requirements, UX tone, product risks.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.