AGENT SKILL

brain-to-docs

Use when the user wants to extract project vision, decisions, and preferences from his head into clear documentation (README + ADRs) through a back-and-forth Q&A loop. Triggers on "brain-to-docs", "build out the docs", "extract the vision", "let's document this project".

License 许可
MIT
最近更新
2026-10-29
Stars
★ 1
Forks
0

01 前言 Front Matter

name
brain-to-docs
description
Use when the user wants to extract project vision, decisions, and preferences from his head into clear documentation (README + ADRs) through a back-and-forth Q&A loop. Triggers on "brain-to-docs", "build out the docs", "extract the vision", "let's document this project".
disable-model-invocation
true

03 SKILL.md 正文

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 he finds 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 he asks, or he's making a severe mistake.

04 同仓库更多 Skills

Rabot-Dutilleul
Rabot-Dutilleul/Fabien-skills

anti-sleep

Keep the Windows machine awake from WSL for a set duration or while a process runs.

★ 1
Rabot-Dutilleul
Rabot-Dutilleul/Fabien-skills

anti-sleep

Keep the user's MacBook awake reliably with macOS caffeinate for a set duration or while a process runs. Use for "don't let my Mac sleep", "keep the screen on", "anti-sleep", "caffeinate", overnight work, or long builds. Unlike a normal background job, it survives temporary agent-shell cleanup.

★ 1
Rabot-Dutilleul
Rabot-Dutilleul/Fabien-skills

security-audit

Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.

★ 1
Rabot-Dutilleul
Rabot-Dutilleul/Fabien-skills

storm-research

Use when someone asks to run Storm Research, use the storm-research skill, run the STORM method on a topic, says "storm research this" / "storm report on X" / "give me a STORM briefing on X", or wants a multi-perspective, citation-verified HTML research briefing on a topic. Runs a 4-phase pipeline: five expert lenses (Practitioner, Academic, Skeptic, Economist, Historian) -> contradiction map -> synthesized HTML report -> adversarial peer review + primary-source verification. Best for topics where multiple viewpoints and fact-checked claims matter; overkill for a simple factual lookup.

★ 1
Rabot-Dutilleul
Rabot-Dutilleul/Fabien-skills

research

Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

★ 1
Rabot-Dutilleul
Rabot-Dutilleul/Fabien-skills

last30days

Research what people actually say about any topic in the last 30 days. Pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, and the web. Includes a doctor health check to diagnose broken or missing sources.

★ 1