project
Skill0 starsChanged 8 days agoMITView on GitHub
Start, update, or close a project in the second brain (30-projects/<name>/ with brief.md and an append-only log.md). Use when the owner says "start a project", "new project", "update project X", "log what we did on X", "where are we on X", "pick up project X", or "close/archive project X".
40 other projects use a version of this.
Adopted by
Most recently taken up by
- br3eze-code/br3eze-codetheir own version, first seen Nov 11, 2026
- HurricaHjz/second-yourselftheir own version, first seen Nov 9, 2026
- saksham10arora-dotcom/everything-claude-codextheir own version, first seen Nov 1, 2026
- kriscard/Skillstheir own version, first seen Oct 28, 2026
- jantichy/claudetheir own version, first seen Oct 27, 2026
- usk6666/yorishiro-proxytheir own version, first seen Oct 25, 2026
Used with
Projects with it also use next, learn and 7 more.
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.
VercelSkillnext
Next.js renderer for json-render that turns JSON specs into full Next.js applications with routes, layouts, SSR, and metadata. Use when working with @json-render/next, building Next.js apps from JSON specs, or creating AI-generated multi-page applications.
Also in 3 projects that use this
genomewalkerSkilllearn
Learn from web sources, generate SKILL.md, and store key patterns in soul memory. Trigger keywords: learn, skill-gen, web-learn, documentation, tutorial.
Also in 8 projects that use this
Microsoft AzureSkilltest
Also in 6 projects that use this
OpenAISkillaudit
Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.
Also in 5 projects that use this
GoogleSkillteach
Teach the user a new skill or concept, within this workspace.
Also in 4 projects that use this
SentrySkillreview
Fixture review skill.
Also in 5 projects that use this
Other versions40 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 40
- fleetdm/fleet★ 7.2ksame name
- samchon/typia★ 6ksame name
- samchon/nestia★ 2.2ksame name
- cwinvestments/memstack★ 433same name
- AlpacaLabsLLC/skills-for-architects★ 420same name
- Achuan-2/siyuan-plugin-task-note-management★ 227same name
- HurricaHjz/second-yourself★ 150same name
- HurricaHjz/SecondSelf★ 150same name
- Soul-Brews-Studio/arra-oracle-skills-cli★ 121same name
- saksham10arora-dotcom/everything-claude-codex★ 96same name
30 more not listed
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 repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brain-reviewSkill
- captureSkill
- gap-finderSkill
- ingestSkill
- lintSkill
- querySkill
- repairSkill
- second-brainSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.
0
Common
Most of the 33 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Write brief.md and log.md (from project-log.md, first entry start).
- Very specific: line 20
Add to index.md under Projects: - [[30-projects/<name>/brief|<Name>]]: one-line outcome (active).
- Very specific: line 24
Read brief.md and the tail of the project's log.md.
- Distinctive: line 34
If scope/outcome changed, propose a brief edit.
- Very specific: line 40
After start, update, or close, run scripts/qmd-sync.sh.
- Very specific: line 43
Read brief.md + the last ~5 log entries + linked artefacts, then answer: goal, current state, last decision, open questions, suggested next …
- Very specific: line 50
Update index.md (status archived) and root log.md: ## [YYYY-MM-DD] project | close <name>.
“Common” is measured: kept by at least 6 in 10 of the 33 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: start · update · resume · close
A project folder lets any agent join cold. brief.md = what it was supposed to be (intent, owner approves
changes). log.md = what it became (append-only). Detect the mode from the request; ask if unclear.
Start
- Name: kebab-case folder
30-projects/<name>/. Checkindex.mdthat it doesn't exist already. - Interview the owner one section at a time, following
90-system/templates/project-brief.md: Why · Outcome · Who it's for · Scope in/out · Constraints & rules · Open questions.- Push back once per section on vague answers: "everyone" is not a segment, "more engagement" is not an outcome, "ASAP" is not a deadline. Offer a sharper rewording.
- "I don't know" is valid → record it under Open questions as
- [ ]. - Pull relevant context from the wiki and link it under Key links.
- Write
brief.mdandlog.md(fromproject-log.md, first entrystart). - Add to
index.mdunder Projects:- [[30-projects/<name>/brief|<Name>]]: one-line outcome (active). log.md(root):## [YYYY-MM-DD] project | start <name>.
Update (after meaningful work)
- Read
brief.mdand the tail of the project'slog.md. - Append to the project log:
## [YYYY-MM-DD] <short label> - What happened: - Decisions: (with why) - Artefacts: [[…]] (files saved in the project folder) - Next: - Save produced artefacts in the project folder (drafts, specs, analyses).
- If scope/outcome changed, propose a brief edit; apply only on the owner's OK.
- Knowledge that outlives the project (lessons, facts about people/tools) → file into
20-wiki/with citations (the project log counts as a source; link it). - Refresh the project's line in
index.md(status, one-line state). Rootlog.md:## [YYYY-MM-DD] project | update <name>.
The log and index entry decay first because they feel invisible. Don't skip them.
After start, update, or close, run scripts/qmd-sync.sh.
Resume ("where are we on X?")
Read brief.md + the last ~5 log entries + linked artefacts, then answer: goal, current state, last decision,
open questions, suggested next step. Read-only unless the owner asks for changes.
Close
- Set
status: archivedinbrief.md. - Append a final
retrospectiveentry: outcome vs. intent, what worked, what didn't, lessons. - File lessons into the wiki (concept pages or a synthesis) with links back to the project.
- Update
index.md(status archived) and rootlog.md:## [YYYY-MM-DD] project | close <name>.
Hard constraints
- Project
log.mdis append-only. Never rewrite past entries; correct with a new entry. brief.mdchanges need the owner's approval.
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.

