research-loglisted

# Research Log This skill maintains a unified research-log workspace in `~/.research/` and uses it to actively improve research, not merely to record it. The data model and all file schemas are defined in `references/conventions.md` — read it first whenever you touch the store. The skill earns its keep at three moments: - **M1 — decision-time guardrail.** Surface relevant anti-patterns *before* the user commits to an approach. See "Decision guardrail" below — this fires from conversation, not only on command. - **M3 — recall when stuck.** Search across all projects for prior lessons and solutions. - **M4 — real-time drift.** Flag work that has drifted from the current Compass focus. ## Decision guardrail (M1) — always active Whenever the user proposes a research approach — an architecture, model, loss function, methodology, experimental design, or "let's do X" choice — **before agreeing, elaborating, or helping execute it**: 1. Read `~/.research/rules.md` (small, promoted-rules-only; cheap to load). 2. Check whether any Rule's trigger/Check matches the proposed action. 3. If a Rule matches, surface it first: "You are about to {X}; this bit you in {projects} — {Check}." Include the evidence. Let the user decide; do not block. 4. If nothing matches, say nothing about rules and proceed normally. This is a behavioral directive, not a hook. It applies in any registered project's working directory. Keep it lightweight — only promoted Rules are checked, and only when an