capture-brainstorming
Skill10 starsChanged 18 days agoLicence not identifiedView on GitHub
Capture a project's brainstorming into a free-form BRAINSTORM.md handoff log covering the findings reached, the facts shared, the directions taken and rejected, and the open topics for the analyst. Runs in two modes. Full capture mines BOTH the current conversation AND past session transcripts, so a later `/analyst` session starts warm. Checkpoint mode is a fast incremental save of new decisions, facts, and open issues, built to run repeatedly during a long session so nothing is lost. Use full capture when the user says "save our brainstorm", "capture the brainstorming", "write up what we figured out", "prep this for the analyst", or "save everything before we spec it". Use checkpoint mode on "checkpoint this", "save our progress", "save what we have so far", and you may run one unasked at a clear milestone. Also hands deferred action items to the `todo` skill. NOT for snapshotting code or a feature branch (use pr-checkpoint), and NOT for end-of-session context saving (use save-context or close-session).
In this repository13 other files it gives its agents.
- analystSkill
- architectSkill
- build-a-pocSkill
- close-sessionSkill
- grill-meSkill
- init-projectSkill
- plan-gateSkill
- plan-status-sheetSkill
- prd-to-issuesSkill
- save-contextSkill
- tddSkill
- todoSkill
- write-a-prdSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 6 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.