project-brief
Skill5 starsChanged 33 days agoMITView on GitHub
Starts a new project note (a single file, or a folder with Brief, Current-State and Decisions) by interviewing the user for the why, scope and definition of done; or, for an existing project, loads its brief and current state and summarizes where things stand before any work begins. Use when the user says "start a project", "new project", "write a brief for X", "what's the status of X", "catch me up on X", "let's work on X", runs /project-brief, or when a task touches a project whose notes you have not read yet this session.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- Git-FED/MuseAi-Skills-Guidetheir own version, first seen Nov 8, 2026
- DoKu67/claude-code-skilstheir own version, first seen Oct 16, 2026
- anhvu3594/claude-skillstheir own version, first seen Oct 15, 2026
- hmj1026/dhpktheir own version, first seen Oct 13, 2026
- sd0xdev/sd0x-dev-flowtheir own version, first seen Oct 8, 2026
- sd0xdev/sd0x-harnesstheir own version, first seen Oct 6, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- Git-FED/MuseAi-Skills-Guide★ 121same name
- zrosenfield/sharepoint-ai-skills★ 96same name
- flurdy/agent-skills★ 9same name
- MarcoZorn/agencykit★ 6same name
- DoKu67/claude-code-skils★ 4same name
- erendevelops/erendev-claude-skills★ 2same name
- hmj1026/dhpk★ 2same name
- anhvu3594/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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- decision-recordSkill
- inbox-triageSkill
- log-feedbackSkill
- meeting-notesSkill
- onboardingSkill
- research-captureSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Read Brief.md and Current-State.md (folder project), or the single project note.
- Distinctive: line 40
Use the user's words for the why and the scope.
- Very specific: line 42
Add typed links where they apply (works_with::, depends_on::, part_of::).
- Very specific: line 43
Run python3 scripts/check_vault.py, show the user the note, and commit if they have agreed to agent commits.
“Common” is measured: kept by at least 6 in 10 of the 10 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
Project brief
First find out whether the project exists: Grep Projects/ for the name (files and folder names, and title-like headings).
Existing project: load it
- Read
Brief.mdandCurrent-State.md(folder project), or the single project note. SkimDecisions.mdheadings and the last few meetings that link the project. - Summarize in the chat, in under ten lines: the goal, where things stand, next actions, open questions, anything blocked.
- Point out anything that looks stale:
updated:more than a month old whilestatus: active, checked boxes still listed as next actions, aCurrent-Statethat contradicts a newer meeting note. Ask before fixing.
Then do the task the user came for.
New project: create it
1. Interview (short)
- What is it, and why now?
- What is in scope, and what is explicitly out?
- How will you know it worked? Push for something checkable ("ten people use it", "the bed survives a season"), not "it's good".
- Who else is involved? (Link existing person notes.)
- The first two or three next actions.
2. Choose the shape
- Single file (
Projects/Name.md) by default. - Folder (
Projects/Name/Brief.md,Current-State.md,Decisions.md) when the project will run for months, involve several people, or collect many decisions. A single-file project can be split into a folder later; offer that when one grows past a couple of screens.
3. Write it
- From
System/Templates/Project.md(andProject-Current-State.mdandDecision.mdfor the folder shape). - Use the user's words for the why and the scope.
- Fill
created:andupdated:with today's date and setstatus: active(orideaif they are not starting yet). - Add typed links where they apply (
works_with::,depends_on::,part_of::). - Run
python3 scripts/check_vault.py, show the user the note, and commit if they have agreed to agent commits.
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.

