Use when a problem, idea, or change of intent is worth capturing as a long-form page, or the person asks to write it up. Never chooses a solution; the tracker issue belongs to create-ticket.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Brief
A brief says what is wrong or wanted, for whom, and how a user would know it is solved. It survives a change of approach, because it contains no approach. Alternatives belong in the options document. Steps belong in the plan.
## Capture the intent
- Preserve the person's language and constraints. Ground every statement in a source: the conversation, an issue, a bug report, the code.
- Keep four things visibly apart: facts, decisions already made, proposals, and open questions. Label suspected causes and unmeasured impact as such.
- Capture the trigger: what happened, what was expected, and what it costs. For a new idea, capture the unmet need.
- When the request arrives with a solution attached ("add patches to cut editing costs"), look at the actual behaviour and cost first, and write the problem underneath it.
- Ask what is missing instead of inventing it: what prompted this, who is affected, what a good result would enable, what would make the current approach good enough.
- Read the code, or give a fresh-context subagent one question to answer with the `gather-evidence` skill, when a fact about today's behaviour is needed. Give the subagent just that question.
…
The line at the top of this page pins the label git:20260924.44e305d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (3281 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
dcouple/pane · 603 stars · license a license file GitHub does not identify · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lb3g5pf6sdhk7dcv
GET https://markdownregistry.com/api/v1/resolve?ref=dcouple/pane/brief
GET https://markdownregistry.com/api/v1/blob/260269765ac14942130626390b04c074bd577b6ce98c2807c4df486d868fb5ca
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
dcouple/pane · main/src/services/paneChatBundle/skills/babysit-pr/SKILL.md · Use after a pull request is open to watch its CI and review-bot comments until it is ready. Fixes real findings…
dcouple/pane · main/src/services/paneChatBundle/skills/bug-intake/SKILL.md · Use when the person reports broken behaviour or starts a session to file a bug. Reproduces and reports. Never fixes.
dcouple/pane · main/src/services/paneChatBundle/skills/codebase-design/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…
dcouple/pane · main/src/services/paneChatBundle/skills/cold-read/SKILL.md · Give a fresh agent something to walk through with zero context - a PR body, a landing page, a document, a process…
dcouple/pane · main/src/services/paneChatBundle/skills/create-ticket/SKILL.md · Capture work and evolving intent during discussion as one or more GitHub tickets, published briefs, or both. Use for…
dcouple/pane · main/src/services/paneChatBundle/skills/discussion/SKILL.md · Have an interactive discussion about a topic, approach, feature, or bug without making code changes. Researches the…
dcouple/pane · main/src/services/paneChatBundle/skills/eli5/SKILL.md · Teach an unfamiliar topic from first principles with a picture-first HTML explanation, published to the workspace's…
dcouple/pane · main/src/services/paneChatBundle/skills/excalidraw-pr-diagrams/SKILL.md · Draw Excalidraw diagrams that make a visual argument, such as a pull request's before/after visual overview, an…
dcouple/pane · main/src/services/paneChatBundle/skills/explain-visually/SKILL.md · Complement an answer or discussion with a first-principles visual HTML explanation, published to the workspace's…
alirezarezvani/claude-skills · c-level-agents/skills/brief/SKILL.md · Use for /c-level-agents:brief, or to frame a strategic question (options, assumptions, success criteria) as a one-page…
suboss87/fdeops · skills/brief/SKILL.md · Clarify a new customer brief, desired outcome, constraints and evidence gaps. Use for kickoff or a first meeting; do…
greenfield-inc/pane · main/src/services/paneChatBundle/skills/brief/SKILL.md · Use when a problem, idea, or change of intent is worth capturing as a long-form page, or the person asks to write it…
oliver-kriska/claude-elixir-phoenix · plugins/elixir-phoenix/skills/brief/SKILL.md · Interactive briefing of a plan file — explains reasoning, schema decisions, component choices. Use when developers need…
educlopez/ui-craft · .agents/skills/brief/SKILL.md · Write or update the project's durable design brief at .ui-craft/brief.md. Invoke when the user asks for brief on their…
educlopez/ui-craft · .codex/skills/brief/SKILL.md · Write or update the project's durable design brief at .ui-craft/brief.md. Invoke when the user asks for brief on their…
educlopez/ui-craft · .gemini/skills/brief/SKILL.md · Write or update the project's durable design brief at .ui-craft/brief.md. Invoke when the user asks for brief on their…
