workthreads

1# Workthreads
2 
3A lead needs a weekly answer across the team's repos: what work happened this week, what got
4finished, and what is still open and needs a next step. **Workthreads** produces that **rollup**
5from SpecStory histories - the `.specstory/history` transcripts your coding agents already write.
6It reports **lines of work and their lifecycle** (new / open / recently closed).
7 
8A deterministic engine (`scripts/workthreads.mjs threads`) does the retrieval, clustering, and
9classification; **you do the synthesis** - you turn its evidence into the lead's weekly report.
10Do not try to read raw transcripts yourself; they can be hundreds of thousands of lines. Run the
11engine and write the rollup from its output.
12 
13This skill is **harness-portable** (agentskills.io format). Where it names a specific tool
14(e.g. `AskUserQuestion`), treat that as "use your harness's equivalent; fall back to plain chat."
15 
16## How the engine splits the work
17 
18- The engine groups the window's beats **by project** and clusters them into **threads** (a line
19  of work that can span several sessions). It assigns each thread one lifecycle **status** relative
20  to today:
21  - **new** - first activity within the last 7 days.
22  - **open** - unresolved, still active (the open loops).
23  - **closed** - latest outcome was success and the thread has gone quiet; flagged **reverted**
24    when a beat ran a rollback command (`git revert` / `git reset --hard` / `git checkout -- ...`).
25…