A weekly summary of coding work across a team's repositories, built from the work records produced by coding agents. It groups related sessions into projects and marks each line of work as new, open, or recently closed.

Use it to prepare a weekly work report across repositories and track ongoing or recently completed work.

It avoids reading huge agent transcripts by hand and gives a lead one view of what was finished and what still needs attention.

workthreads — Skill for Claude Code and Codex by specstoryai: A weekly summary of coding work across a team's…

About the project

SpecStory is a local-first tool that records and indexes conversations with AI coding assistants so developers can search, reuse, and share their solutions. It is for preserving coding decisions, snippets, and other knowledge across projects and development tools. Its catalogue skills and commands process saved sessions into reusable agent skills and connect the workflow to coding agents.

specstoryai/getspecstory · 1,321 stars · on GitHub · specstory.com

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/specstoryai/getspecstory/workthreads

Any agent

npx skills add specstoryai/getspecstory --skill workthreads

Clone the repo

git clone --depth 1 https://github.com/specstoryai/getspecstory

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/specstoryai/getspecstory/workthreads.svg)](https://agentmods.dev/skills/specstoryai/getspecstory/workthreads)

Your own site

<a href="https://agentmods.dev/skills/specstoryai/getspecstory/workthreads"><img src="https://agentmods.dev/badge/skills/specstoryai/getspecstory/workthreads.svg" alt="Measured on agentmods" height="20"></a>

Per session 126 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,274 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00126	$0.01274
Opus 5	$0.00063	$0.00637
Sonnet 5	$0.00025	$0.00255
Haiku 4.5	$0.00013	$0.00127

Measured 6d ago against content hash 0c74ebfbe38f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

workthreads scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

The scan reads SKILL.md. This mod also ships 9 executable files (install.sh, scripts/lib/db.mjs, scripts/lib/discover.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

workthreads/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workthreads

A lead needs a weekly answer across the team's repos: what work happened this week, what got finished, and what is still open and needs a next step. Workthreads produces that rollup from SpecStory histories - the .specstory/history transcripts your coding agents already write. It reports lines of work and their lifecycle (new / open / recently closed).

A deterministic engine (scripts/workthreads.mjs threads) does the retrieval, clustering, and classification; you do the synthesis - you turn its evidence into the lead's weekly report. Do not try to read raw transcripts yourself; they can be hundreds of thousands of lines. Run the engine and write the rollup from its output.

This skill is harness-portable (agentskills.io format). Where it names a specific tool (e.g. AskUserQuestion), treat that as "use your harness's equivalent; fall back to plain chat."

How the engine splits the work

The engine groups the window's beats by project and clusters them into threads (a line of work that can span several sessions). It assigns each thread one lifecycle status relative to today:
- new - first activity within the last 7 days.
- open - unresolved, still active (the open loops).
- closed - latest outcome was success and the thread has gone quiet; flagged reverted when a beat ran a rollback command (git revert / git reset --hard / git checkout -- ...).
Output is deterministic (stable sort, no wall-clock timestamps in the body), so two runs on the same corpus are byte-identical.

Default flow: the weekly rollup

Index the corpus into workthreads' own DB. Point at the team's repos and build/update it:

node "${CLAUDE_SKILL_DIR}/scripts/workthreads.mjs" index --projects <parent-of-repos> --db <db>
# or a single tree:  --scan <root>     or a single history dir:  --dir <dir>

Run threads cross-project for the last 7 days and capture the evidence:
```
node "${CLAUDE_SKILL_DIR}/scripts/workthreads.mjs" threads --db <db> --days 7            # human digest
node "${CLAUDE_SKILL_DIR}/scripts/workthreads.mjs" threads --db <db> --days 7 --json     # machine-readable
```
The digest prints, per project, three sections in order - New, Open, Recently closed - each thread with its evidence refs (path:line), last-activity date, status, and a reverted marker. --json emits an array of threads (project, status, reverted, the files touched, last-activity date).

Read the full file on GitHub · 89 lines

Files

What ships with it

18 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

6d ago First seen · 89 lines · 126 tokens per session scan A 0c74ebfbe38f

Subscribe to this mod's changes

workthreads is a skill published in the GitHub repository specstoryai/getspecstory (1,321 stars, last pushed yesterday), licensed Apache-2.0. It adds 126 tokens to every session and 1,274 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Project management ai chat-history copilot copilot-chat vscode vscode-extension

backseat-driver-testing

Testing strategies for Calva Backseat Driver MCP tools. Use when: Testing Backseat Driver, validating tool updates, testing structural editing workflows, verifying REPL evaluation with who-tracking, testing shadow-cljs runtime discovery and targeting, testing output log filtering, testing load-file tool, smoke testing…

BetterThanTomorrow/calva-backseat-driver · 106 tokens

backseat-driver-internals

Backseat Driver extension internals — Ex framework contracts, app-db state architecture, MCP socket server lifecycle, enrichment system, Datascript output log, activation sequences, and namespace reference. Use when: modifying core extension code, debugging state issues, working with app-db or Ex framework…

BetterThanTomorrow/calva-backseat-driver · 82 tokens

backseat-driver

Effective use of the Backseat Driver extension and its tools for Clojure interactive programming. Use when: working in Clojure (including all dialects and runtimes) project, be it reading, planning, developing, or evaluating code in the REPL, looking up function documentation or ClojureDocs examples, choosing REPL…

BetterThanTomorrow/calva-backseat-driver · 186 tokens

editing-clojure-files

Structural editing of Clojure files using Backseat Driver tools. Use when editing or planning edits: creating/adding/inserting/replacing/deleting top-level forms, fixing bracket balance, resolving indentation issues, planning multi-edit sequences, recovering from failed edits, or working with Rich Comment Forms in…

BetterThanTomorrow/calva-backseat-driver · 135 tokens

e2e-testing

E2E test authoring for Backseat Driver. Use when: writing, modifying, or debugging e2e tests under e2e-test-ws/, adding new MCP test scenarios, investigating test failures, understanding test infrastructure, or working with files matching test.cljs in the e2e workspace.

BetterThanTomorrow/calva-backseat-driver · 66 tokens

icon-jetbrains

Create or review IntelliJ New UI SVG icons, theme variants, sizes, and palette.

Kilo-Org/kilocode · 23 tokens