capture-followup
Record deliberately deferred work to Tesseract so it resurfaces when a future session touches the same area. Use when you choose not to fix something now, or a "## Follow-ups" section lands in a tracking file.
- License 许可
- MIT
- 最近更新
- 2026-10-21
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- capture-followup
- description
- Record deliberately deferred work to Tesseract so it resurfaces when a future session touches the same area. Use when you choose not to fix something now, or a "## Follow-ups" section lands in a tracking file.
03 SKILL.md 正文
A soft signal for future recall — no ticket, no lifecycle. For work that should actually get scheduled, use /blg (Torque).
Procedure
0. Dedup. tesseract_recall namespaces=["user/chrispian/memory/followups"] query="<slug>". Followups go stale faster than anything else here — the work gets done, or its context moves.
On a hit, you must choose one — a hit you neither supersede nor deprecate stays live and reads as independent corroboration:
| The hit is… | Do |
|---|---|
| the same record, understanding changed | memory_write same key + supersedes: <revision_id> from the lookup result |
| wrong, or no longer applies | mcp__mux__memory_deprecate revision_id=<id> |
| genuinely a different record | write the new key — and say in one line why it is different |
The lookup you just ran returned revision_id. That is the value supersedes takes.
1. Dedup. tesseract_recall namespaces=["user/chrispian/memory/followups"] query="<slug>". Already there → say so and offer to update it rather than duplicating.
2. Write.
memory_write
namespace = user/chrispian/memory/followups
memory_key = <slug> # 3–5 words, a-z 0-9 _ ONLY
payload_summary = one sentence, ≤140 chars
payload_body = what's deferred, WHY it was deferred, and where to pick it up
tags = ["followup", "captured_during_session", "project:<project>"]
author_agent_id = claude-code | codex | …
author_version = model slug
trigger = manual
session_id = the SESSION: value from the SessionStart hook
origin = observation
confidence = 0.85
status = canonical
3. Confirm in one line: Captured follow-up: <summary>
Rules
- Hyphens are rejected in keys. Normalize to underscores.
- Always record why it was deferred. Without it a future session has to reconstruct the reasoning and usually just re-decides. The "why" is most of the value.
- Point at the files or prior decisions involved.
- Project and ticket are tags, never key segments.
Follow-up vs backlog
- Follow-up (here) — surfaces on recall when someone works nearby. Agents only.
/blg(Torque) — a real item with priority that gets scheduled.
Both when it's genuinely both. Neither for "would be nice someday."
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.