mcpField
B
brain-to-docs

brain-to-docs

github.com/davidondrejDocuments4.2k217 installsUpdated today
Repository

About brain-to-docs

brain-to-docs is a skill for capturing a user's decisions, preferences, and project vision in concise Markdown documentation. It reads existing project docs first, then updates the README or records decisions as ADRs after each answer.

Key features

  1. 01Read README and ADRs first
  2. 02Ask five varied plain-text questions by default
  3. 03Update docs after every answer
  4. 04Separate vision from decisions
  5. 05Format numbered ADRs with defined sections

Use cases

  1. 01Capture product vision in a project README
  2. 02Record project decisions as ADRs
  3. 03Turn ongoing discussions into maintained documentation

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/davidondrej/skills --skill brain-to-docs

After installing, type/brain-to-docsin Claude Code to confirm it loaded.

Details

From the project README

brain-to-docs

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" (or similar).

Rules

  • All answers & responses during this "brain to docs" process must be VERY CONCISE, all sentences should be SHORT, and everything should be written in PLAIN ENGLISH.
  • ADRs: short, numbered NNNN-slug.md, Status + Context + Decision + Consequences.
  • README: vision only. Decisions go in ADRs.
  • Don't challenge the user's thinking unless they ask, or they're making a severe mistake.

Comments

Markdown supported