brain-to-docs
Interview the user to turn project vision and decisions into README and ADR documentation.
Profile →npx skills add sickn33/agentic-awesome-skills --skill brain-to-docs --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# brain-to-docs ## When to Use - Use when the user wants to extract project vision, decisions, or preferences into durable docs. - Use when README and ADRs should be built through a back-and-forth interview. The whole purpose: extract as much of the user's taste, judgment, knowledge, vision, preferences, and decisions as possible into text — saved as clear, concise markdown docs for the project. README holds the vision; `docs/adr/` holds the decisions. ## The loop 1. **Check docs first, every time.** Read `docs/adr/` (and `README.md`) before doing anything — other agents and people add/edit ADRs constantly. 2. **Ask 5 different questions** in plain text (never a questions UI) — default 5 unless the user asks for a different number. Make them high-variety: a wide, creative spectrum of unique angles, not all the same type (e.g. not all "tech stack" or all "product" or all "monetization"). Exception: if the user asks for a specific focus area, follow it. The user answers whichever they find most useful. 3. **Update docs after EVERY answer** — no exceptions. You decide whether it updates `README.md` or becomes a new ADR — whatever makes sense. 4. Repeat until the user says "we're done"
- When to Use
- The loop
- Rules
- Limitations
What does the brain-to-docs skill do?
Interview the user to turn project vision and decisions into README and ADR documentation.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill brain-to-docs --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.