- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add specstoryai/getspecstory --skill workthreads -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add specstoryai/getspecstory --skill workthreads -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add specstoryai/getspecstory --skill workthreads -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add specstoryai/getspecstory --skill workthreads -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/specstoryai/getspecstory/tree/HEAD/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."
git revert / git reset --hard / git checkout -- ...).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).
Write the rollup from that evidence, in the lead's shape:
closed threads);open threads, unresolved or needing verification, with a suggested
next step each;reverted threads);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.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.
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:
.specstory/history corpus?--days N to widen.)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.
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 in
---name: workthreadsdescription: SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any…---# workthreads/SKILL.md總覽
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.
常見問題
從發布者下載 workthreads/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/specstoryai/getspecstory。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。