workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still an open loop, and what was just started. Use when someone asks "what happened this week", "what is still open", "what did the team finish", "give me the weekly rollup", or wants a status report over a .specstory/history corpus.
npx skills add specstoryai/getspecstory --skill workthreads --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. - **o
- How the engine splits the work
- Default flow: the weekly rollup
- Guided start
- Conventions
node "${CLAUDE_SKILL_DIR}/scripts/workthreads.mjs" index --projects <parent-of-repos> --db <db>
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-readableWhat does the workthreads skill do?
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still an open loop, and what was just started. Use when someone asks "what happened this week", "what is still open", "what did the team finish", "give me the weekly rollup", or wants a status report over a .specstory/history corpus.
How do I install it?
Run `npx skills add specstoryai/getspecstory --skill workthreads --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From specstoryai/getspecstory, a repository with 1,295 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.