Research brief
Rendered from playbook/docs/brief-template.md.
Research brief - <slug>
Copy this file to playbook/briefs/<slug>.md before outlining. Do not draft until every required field is filled.
| Field | Value |
|---|---|
| Slug | |
| Working title | |
| Article shape | Specimen Record / Boundary Case / Domain Trap / Comparison Note / Revision Pass |
| Category | |
| Intent tags | |
| AI authors credited | |
| Reviewer or checker | none / named person |
| Date |
1. Concept gate
Reader's real question:
-
Why this belongs in the catalog:
-
Bug claim in one sentence:
The bug is ____________________, where ____________________ makes ____________________ harder to see or choose.
What this bug is not:
-
Nearby bugs to check:
| Nearby bug | Difference |
|---|---|
Concept gate: Is this specific, distinct, grounded, and correctable? yes / revise
2. Sources and research
List 2 to 4 sources or established concepts to verify.
| Source / concept | Year | What it supports | URL / DOI / note |
|---|---|---|---|
Do not invent titles, years, DOIs, or effect sizes. If a source is uncertain, say so.
3. Article plan
Explained boundary:
-
Examples planned (4-8 quote examples):
1. 2. 3. 4.
Real-world scenarios, if useful:
-
Impact:
-
Causes:
-
Self-spotting signs, if useful:
-
Prevention moves (3-6):
-
Questions & Answers, if genuinely sharp:
-
Reframing examples (2-3):
| Label | Original thought | Reframed thought |
|---|---|---|
Related thinking bugs:
| Bug | Difference note |
|---|---|
4. Rewrite inventory (only for existing pages)
- Current sections:
- Current examples worth preserving:
- Current sources:
- Current reframes:
- Current related links:
- What can be removed, and why:
5. Sign-off
- ☐ Belonging test passed
- ☐ Nearby bugs checked
- ☐ Sources verified or uncertainty labeled
- ☐ Examples are concrete
- ☐ Reframes are realistic, not forced optimism
- ☐ Credits model/person named