workthreads
/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.
- Author
- specstoryai ↗
- Repository
- getspecstory ↗
- Licence
- Apache-2.0
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 19
- Scripts
- 9
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 9 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: install.sh, scripts/lib/db.mjs, scripts/lib/discover.mjs, scripts/lib/indexer.mjs, scripts/lib/parse.mjs, scripts/lib/patterns.mjs, scripts/lib/threads.mjs, scripts/workthreads.mjs, tests/threads.test.mjs
What it does and when to use it
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.
Triggers from the description
Arguments
/workthreads Enter = guided setup · or plain English, e.g. 'last 7 days, just the open loops
Original author description
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 it works
- How the engine splits the work
- Default flow: the weekly rollup
- Guided start
- Conventions
SKILL.md preview
---
name: workthreads
description: 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.
argument-hint: "Enter = guided setup · or plain English, e.g. 'last 7 days, just the open loops'"
allowed-tools: Bash, Read, Write, AskUserQuestion
license: Apache-2.0
metadata:
author: Greg Ceccarelli
version: "1.0.0"
---
# 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
1. **Index the corpus** into workthreads' own DB. Point at the team's repos and build/update it:
```bash
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>
```
2. **Run `threads` cross-project for the last 7 days** and capture the evidence:
```bash
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).
3. **Write the rollup** from that evidence, in the lead's shape:
- (a) a high-level result: session count and active projects in the window;
- (b) per-project **highlights** of completed work (the `closed` threads);
- (c) **open loops** - the `open` threads, unresolved or needing verification, with a suggested
next step each;
- (d) notable **rollbacks / abandoned efforts** (the `reverted` threads);
- (e) cite evidence refs (`path:line`) so each claim is checkable.
Add a caveat that **the week may still be in progress**, so `open` and `new` threads are
snapshots, not final outcomes.
4. **Save it to a dated file** so the rollup is durable and diffable week over week:
```
.specstory/workthreads/<YYYY>-W<week>.md
```
(ISO week number, e.g. `.specstory/workthreads/2026-W25.md`). Also offer `threads --out <file>`
to drop the raw digest beside your written summary.
## Guided start
If the user just invokes the skill with no specifics, ask three short questions (use
`AskUserQuestion` or plain chat), then run the default flow with the answers:
- **Scope** - which repos / parent directory holds the team's `.specstory/history` corpus?
- **Window** - how many days back? (default **7** for the weekly rollup; `--days N` to widen.)
- **Goal** - the whole **rollup**, just the **open loops**, just **recently closed**, or a quick
**status** line? Tailor which sections you emphasize to the answer.
## Conventions
Node ESM only, zero dependencies, Node >= 22.5. No em dashes anywhere (use " - "). The engine path
never calls an LLM or the network; all judgment (the written narrative, suggested next steps,
emphasis) is yours.
Files in this package (19)
- README.md 3 KB
- SKILL.md 5 KB
- install.sh 1 KB
- package.json 1 KB
- docs/2026-06-24-WORKTHREADS-AS-BUILT.md 6 KB
- fixtures/threads-bar/.specstory/history/2026-06-06_09-00-00Z-scaffold-search-index.md 1 KB
- fixtures/threads-bar/.specstory/history/2026-06-20_11-00-00Z-fix-search-index.md 1 KB
- fixtures/threads-bar/.specstory/history/2026-06-21_15-00-00Z-start-notif-badge.md 1 KB
- fixtures/threads-foo/.specstory/history/2026-06-02_09-00-00Z-begin-checkout-flow.md 1 KB
- fixtures/threads-foo/.specstory/history/2026-06-09_10-00-00Z-finish-checkout-flow.md 1 KB
- fixtures/threads-foo/.specstory/history/2026-06-12_14-00-00Z-payment-retry-rollback.md 1 KB
- scripts/workthreads.mjs 3 KB
- scripts/lib/db.mjs 4 KB
- scripts/lib/discover.mjs 3 KB
- scripts/lib/indexer.mjs 7 KB
- scripts/lib/parse.mjs 10 KB
- scripts/lib/patterns.mjs 14 KB
- scripts/lib/threads.mjs 12 KB
- tests/threads.test.mjs 8 KB
Versions
The database has no other skills named workthreads.
Database snapshot: 13.11.2026 · package version 624e9c7bde1a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95lore
SpecStory Lore - mine your SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more) into a persistent corpus, surface your reproducible workflows with corroborated evidence, and interactively forge the chosen ones into skills installed across all… - 100specstory-session-summary
Summarize recent SpecStory AI coding sessions in standup format. Use when the user wants to review sessions from .specstory/history, prepare for standups, track work progress, or understand what was accomplished. - 100specstory-guard
Install a pre-commit hook that scans .specstory/history for secrets before commits. Run when user says "set up secret scanning", "install specstory guard", "protect my history", or "check for secrets". - 100team-weekly-report
Generate a weekly team status report combining JIRA and GitHub data. Fetches closed, open, stale, and blocked issues plus PR activity for each team member. Requires a team config YAML file with JIRA project, GitHub repos, and team member mappings. Use when the user asks for a… - 100weekly-update
Write the weekly team update from the week's record, for the team or for a manager, client or board. Use for "write the weekly update", "weekly recap", "what did we get done this week", or "status report". - 90report
Activity report from total-agent-memory for a project and period. Use when the user types /report or asks "report for today", "what did we do this week", "weekly / monthly summary", "status report", "retro for project X", "all-time report", "report for last week", or a report…