client-brief
Skill1 starsChanged 35 days agoMITView on GitHub
Turns a messy client message, email, or voice-note transcript into a one-page brief with scope, assumptions, and open questions. Use when someone pastes a WhatsApp thread, an email, or meeting notes and asks what the job actually is. Does not price the work and does not invent budget, deadline, or audience.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- aditya-vermax/skillstheir own version, first seen Nov 8, 2026
- promptadvisers/claude-code-next-stepstheir own version, first seen Sep 7, 2026
- kshyam/opencode-and-claude-skillstheir own version, first seen Aug 30, 2026
- alejopijuan/Claude-Code-Agency-Co-Foundertheir own version, first seen Jul 9, 2026
- coopersimson96/ai-content-systemtheir own version, first seen Jun 25, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- alejopijuan/Claude-Code-Agency-Co-Founder★ 19same name
- coopersimson96/ai-content-system★ 17same name
- promptadvisers/claude-code-next-steps★ 5same name
- aditya-vermax/skills★ 1same name
- kshyam/opencode-and-claude-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 repository13 other files it gives its agents.
- agent-ready-siteSkill
- arabic-copySkill
- arabic-localizationSkill
- arabic-seoSkill
- design-tokens-extractorSkill
- freelance-quoteSkill
- product-sheetSkill
- rtl-uiSkill
- shared-server-deploySkill
- ui-inventorySkill
- vat-worksheetSkill
- video-readerSkill
- zatca-invoiceSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Read the whole message before writing.
- Distinctive: line 24
Put anything missing under Open questions.
- Distinctive: line 32
If two messages disagree, write both and ask which one stands.
- Distinctive: line 34
No price, no discount, no timeline you made up.
- Distinctive: line 38
Every line is either in the source or marked as an open question.
“Common” is measured: kept by at least 6 in 10 of the 5 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
Client brief
Turn one messy client message into a brief a person can send back. Read only what they pasted. Leave gaps as questions.
When to use
- A WhatsApp thread, email, or transcript needs to become a clear job description.
- The user asks "what are they actually asking for?"
When not to use
- They want a price, a quote, or payment terms. Use freelance-quote for that, after this brief exists.
- The message is a contract to review for legal risk. Say so and stop.
Workflow
- Read the whole message before writing.
- Fill
references/brief-template.md. Copy a fact only when the message states it. - Put anything missing under Open questions. Do not guess the budget, the deadline, the audience, or the deliverable count.
- Split the ask into In scope and Out of scope. Out of scope is only what they explicitly excluded, or what a reader could confuse with the ask.
- End with one next step: the single question that unblocks the work.
- Show the brief to the user. Do not send it to the client unless they ask.
Rules
- Quote the client's words when a phrase is easy to misread. Keep the quote short.
- If two messages disagree, write both and ask which one stands.
- Arabic and English can sit in the same brief. Do not translate a requirement into a different requirement.
- No price, no discount, no timeline you made up.
Done check
- Every line is either in the source or marked as an open question.
- In scope does not contain a deliverable they never mentioned.
- The next step is one question, not a plan.
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.