capture-investigation
Write a dense dossier to Tesseract knowledge after a complex investigation, so a future session boots with the findings instead of re-deriving them. Use after root-causing something non-trivial, while the evidence is still fresh.
- License 许可
- MIT
- 最近更新
- 2026-10-21
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- capture-investigation
- description
- Write a dense dossier to Tesseract knowledge after a complex investigation, so a future session boots with the findings instead of re-deriving them. Use after root-causing something non-trivial, while the evidence is still fresh.
03 SKILL.md 正文
The point is that nobody re-runs this investigation. Not a status report — a reusable artifact.
Preconditions
All three, or stop and ask:
- A non-trivial investigation just completed — root cause identified, evidence gathered.
- Follow-on work exists that depends on the findings (tasks filed, or about to be).
- The evidence is still in this session — queries,
file:linerefs, commit SHAs, session ids. Don't reconstruct it after the fact; a dossier assembled from memory is worse than none.
Not for: session status (/end-of-session), a single decision (/capture-decision), or a cross-project pattern (that's knowledge, but not investigation-shaped).
Procedure
1. Draft it
This is a document, so it drafts first — ~/dev/agent-os/workspaces/drafts/<project>/<session>/investigation-<slug>.md:
# Investigation: {slug}
**Boot context** — project, branch, commit SHA, related task ids.
**Identifiers** — session ids, run ids, anything needed to re-pull the evidence.
## Evidence
{Compact tables, one per source (DB / log / tool trace). Rows, not prose.}
## Root cause
{Numbered chains. Each names the mechanical "why" and the affected task.
Where chains compose (A → B → symptom), say so explicitly.}
## Replay
{Literal shell/SQL/tool invocations, copy-pasteable. No narration inside the block.}
## Code refs
{path:line — one per finding}
## Dead ends
{Hypotheses considered and falsified, each with what disproved it.}
## Where to start
{Which follow-on work is entangled and why. A hint, not a plan.}
The Dead ends section is the one that pays. Anyone can re-find the root cause given time; what's expensive is re-eliminating the six things it wasn't. If you cut a section, don't cut that one.
2. Stop and report
Drafted investigation: {slug} → {path}. Review and I'll promote.
3. On approval, promote
knowledge_write
namespace = user/chrispian/knowledge/<project>/investigations
key = <slug>_<YYYY_MM_DD> # a-z 0-9 _ only
kind = investigation
source = manual
pointer_scheme = nil # content-first; the body IS the artifact
pointer_locator = <project>
summary = 3–5 sentences — what broke, why, what it blocks.
This is what surfaces in lookups. Make it load-bearing.
body = the full dossier
tags = ["<project>", "investigation", "<theme>"]
confidence = 0.9
Then archive the draft to ~/dev/agent-os/archive/drafts/<project>/<YYYY-MM-DD>/, and comment the key onto the related Torque tasks so the pointer is findable from the work.
Note on pointers
pointer_scheme: nil is deliberate. File pointers rot — 44% of the existing ones are dead, because files move and Tesseract never hears about it. The body survives regardless, so the body is the artifact.
04 同仓库更多 Skills
tangent
Open a browser workflow when chat is the wrong shape for structured input — triaging many items with one decision, multi-question feedback, or design review. Requires the Tangent MCP server.
release
Cut a release. Use before git tag or gh release create.
push
Push work off this machine. Use before any git push.
pull-request
Open a pull request. Use before gh pr create.
end-of-session
Wrap up a work session — reconcile the git tree, commit what this session authored, review drafts, and capture durable signal. Use when the user signals the session is ending.
commit
Commit work in a tree another session may be using. Use before any git commit.