← ClaudeAtlas

throughlinelisted

Throughline keeps the thread of work intact on work that's big enough to drift or that outlives one sitting. Two linked habits: (1) TASK TRACK — an emoji-tagged task list with exactly one ⭐️ MAIN goal anchor, so you can see at a glance whether you're still solving the main thing or have drifted; (2) HANDOFF — compact a session into a plain-markdown handoff doc the next agent (any agent) can pick up cleanly. Reach for it when: a long or many-step task is at real risk of losing the thread, you catch yourself drifting off the original goal, you're wrapping up or running low on context, you're switching agents or sessions, or you're explicitly asked to 'hand this off' / 'write a handoff' / 'summarize for the next session' / 'compact this' / 'pick up where we left off' / 'resume'. Do NOT reach for it on short, self-contained tasks that finish in one pass — the full protocol is overhead there. Capability-agnostic and cross-platform — works as a skill or a plain paste-in prompt.
jovesun-lab/whetstone · ★ 7 · AI & Automation · score 81
Install: claude install-skill jovesun-lab/whetstone
# Throughline *Keep the thread — Task Track within a session, Handoff across them.* > **For any AI agent reading this file.** The frontmatter uses Claude's skill format; the > body is plain markdown. It works the same for Claude, OpenAI, Gemini, Cursor, Cline, Aider, > or a local model — paste the body in as a prompt if your platform has no skill system. > Assume **nothing** about your host's capabilities; everything here degrades gracefully > (see "Capability-agnostic by design" below). ## What this is Long or multi-agent work fails in two predictable ways, and this skill is two habits that each kill one of them: - **Within a session, reasoning drifts off the goal.** You solve a small problem, which surfaces another, which pulls you somewhere adjacent to what you started on. Every step is locally reasonable; together they bend the trajectory. **Task Track** makes that drift *visible* by keeping one ⭐️ MAIN goal anchor in front of you. - **Across sessions, the thread is dropped.** A fresh run (or a different agent) starts cold, re-derives what was already known, or trusts a stale summary. **Handoff** carries the thread forward as a plain-text artifact any agent can pick up. **The correlation — the load-bearing point.** The **⭐️ MAIN tag is the shared goal anchor.** Task Track holds it *within* a run; Handoff carries it (plus state) *across* runs. One sentence: **don't lose the thread — within a session or between them.** The same anti-drift purpose runs throug