arminzou/dotbrain / plugin/skills/maintain-brain
maintain-brain
VerifiedCapture, update, check, and clean up private project understanding. Use when preserving useful context, revising a Brain record, checking drift or broken references, or removing obsolete and redundant Brain material.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.4 KB |
| agents/openai.yaml | config | 126 B |
| references/adr-format.md | markdown | 3.8 KB |
| references/context-format.md | markdown | 1.3 KB |
| references/design-format.md | markdown | 5.3 KB |
| references/dotbrain-skills.md | markdown | 2.1 KB |
| references/findings.md | markdown | 2.1 KB |
| references/writing.md | markdown | 6.5 KB |
references/findings.md
View on GitHub# Findings and references
Use `.brain/docs/` when a finding, reference, or explanation needs continuing discovery
that existing sources do not adequately support. Prefer a source link or an existing
relevant document; choose a descriptive filename only when a new record earns its upkeep.
Retained initiative-specific uncertainty belongs in its design. Use Beads for work and
execution evidence needing durable continuation or coordination.
A useful finding carries:
| Part | Contents |
| --- | --- |
| Claim | What was observed, inferred, hypothesized, proposed, or accepted |
| Source | Inspected file and revision, check output, document, conversation approval, or stable URL |
| Applicability | Date, version, environment, scope, and limits that affect reuse |
| Implication | Why the finding matters, separately from the observed fact |
| Open question | What remains unknown and what would resolve it, if relevant |
Record enough check detail to assess a retained claim: command, revision,
environment, result, and evidence location. A passing source check does not establish
runtime behavior. A source's assertion is not an independently verified observation;
attribute it and retain conflicting evidence. Current behavior alone does not establish
historical intent.
For a reference, retain its title, author or owning organization when known, URL or file
location, relevant revision or access date, and why it matters. Distinguish a direct quote
from a paraphrase and your inference. Preserve user-provided wording and literal examples
when reorganizing source material. Keep sensitive source contents private and never store
credentials in a note.
For maintained explanations, update current behavior and retain earlier evidence only
when it still informs current understanding or unfinished work. During authorized cleanup,
remove obsolete records and repair their pointers; historical value alone need not keep
them in the Brain. Give retained historical findings their applicability rather than a
current guarantee. An adopted public requirement is maintained through `repo-rules`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |