- 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.
FAQ
게시자에게서 workthreads/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/specstoryai/getspecstory에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.