Git Worktree Manager
microsoft/WindowsAppSDK
Creates and manages Git worktrees with PowerShell scripts so separate issues and Copilot sessions each get an isolated branch, build and test environment.
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).
Install Workthreads
$ npx skills add specstoryai/getspecstory --skill workthreads -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install specstoryai/getspecstory workthreads --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/specstoryai/getspecstory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workthreads .claude/skills/workthreads && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "workthreads" agent skill from https://github.com/specstoryai/getspecstory/tree/dev/workthreads into .claude/skills/workthreads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthreads", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/specstoryai/getspecstory/tree/dev/workthreadsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add specstoryai/getspecstory --skill workthreads -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install specstoryai/getspecstory workthreads --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/specstoryai/getspecstory.git skills-src && mkdir -p .agents/skills && cp -r skills-src/workthreads .agents/skills/workthreads && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "workthreads" agent skill from https://github.com/specstoryai/getspecstory/tree/dev/workthreads into .agents/skills/workthreads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthreads", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add specstoryai/getspecstory --skill workthreads -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install specstoryai/getspecstory workthreads --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/specstoryai/getspecstory.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/workthreads .cursor/skills/workthreads && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "workthreads" agent skill from https://github.com/specstoryai/getspecstory/tree/dev/workthreads into .cursor/skills/workthreads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthreads", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/specstoryai/getspecstory.git --path workthreads--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add specstoryai/getspecstory --skill workthreads -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install specstoryai/getspecstory workthreads --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/specstoryai/getspecstory.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/workthreads .gemini/skills/workthreads && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "workthreads" agent skill from https://github.com/specstoryai/getspecstory/tree/dev/workthreads into .gemini/skills/workthreads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthreads", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install specstoryai/getspecstory workthreadsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add specstoryai/getspecstory --skill workthreads -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/specstoryai/getspecstory.git skills-src && mkdir -p .github/skills && cp -r skills-src/workthreads .github/skills/workthreads && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "workthreads" agent skill from https://github.com/specstoryai/getspecstory/tree/dev/workthreads into .github/skills/workthreads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthreads", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add specstoryai/getspecstory --skill workthreads -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install specstoryai/getspecstory workthreads --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/specstoryai/getspecstory.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/workthreads .opencode/skills/workthreads && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "workthreads" agent skill from https://github.com/specstoryai/getspecstory/tree/dev/workthreads into .opencode/skills/workthreads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthreads", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
workthreads- GitHub stars
- 1.3k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 542 words
- Files
- 21 (incl. scripts)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
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).
- Works in 4 steps: Index the corpus into workthreads' own… → Run threads cross-project for the last 7… → Write the rollup from that evidence, in… → …
- Someone asks what happened this week
- SKILL.md covers How the engine splits the work, Default flow: the weekly rollup, Guided start and Conventions
- Runs Shell scripts from its folder; calls node and git
What it does
Workthreads is an agent skill from specstoryai/getspecstory. 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…
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 29 other files, including scripts (for example `README.md`, `docs/2026-06-24-WORKTHREADS-AS-BUILT.md` and `fixtures/threads-bar/.specstory/history/2026-06-06_09-00-00Z-scaffold-search-index.md`).
It sits in Development. It works with Visual Studio Code and Git. The repository describes itself as: Install our local first extensions for your favorite AI IDE or Terminal Agent. Process your histories into reusable skills with Lore. Sync your conversations to the cloud. File… The licence is Apache-2.0.
When your agent uses it
- Someone asks what happened this week
- What is still open
- What did the team finish
- Give me the weekly rollup
Example prompts
- “what happened this week”
- “what is still open”
- “what did the team finish”
- “/workthreads”
Requirements
- A Bash shell
- Pre-approved tools (allowed-tools): Bash, Read, Write, AskUserQuestion
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Index the corpus into workthreads' own DB. Point at the team's repos and build/update it
- Run threads cross-project for the last 7 days and capture the evidence
- Write the rollup from that evidence, in the lead's shape
- Save it to a dated file so the rollup is durable and diffable week over week
What it can do on your machine
Read from SKILL.md and the folder at commit a0dd4db. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
BashReadWriteAskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
nodegit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Workthreads loads about 1.3k tokens when it runs. Until then it costs about 140 tokens; SKILL.md has 542 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Write, AskUserQuestion
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from specstoryai/getspecstory at commit a0dd4db, republished under its Apache-2.0 licence (© specstoryai). 542 words, ~1,264 tokens.
Download SKILL.mdSave it as
.claude/skills/workthreads/SKILL.md (or your agent's skills folder). This skill also uses 20 other files; get the full folder from GitHub.- 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.
- allowed-tools
- Bash, Read, Write, AskUserQuestion
- argument-hint
- Enter = guided setup · or plain English, e.g. 'last 7 days, just the open loops'
- license
- Apache-2.0
- metadata.author
- Greg Ceccarelli
- metadata.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
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>Run
threadscross-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-readableThe 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 arevertedmarker.--jsonemits an array of threads (project,status,reverted, the files touched, last-activity date).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
closedthreads); - (c) open loops - the
openthreads, unresolved or needing verification, with a suggested next step each; - (d) notable rollbacks / abandoned efforts (the
revertedthreads); - (e) cite evidence refs (
path:line) so each claim is checkable. Add a caveat that the week may still be in progress, soopenandnewthreads 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 offerthreads --out <file>to drop the raw digest beside your written summary.
Show full SKILL.md (112 more words)Show less
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/historycorpus? - Window - how many days back? (default 7 for the weekly rollup;
--days Nto 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.
© specstoryai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 20 other files (scripts) in workthreads of specstoryai/getspecstory.
- SKILL.md
- README.md
- docs/2026-06-24-WORKTHREADS-AS-BUILT.md
- fixtures/threads-bar/.specstory/history/2026-06-06_09-00-00Z-scaffold-search-index.md
- fixtures/threads-bar/.specstory/history/2026-06-20_11-00-00Z-fix-search-index.md
- fixtures/threads-bar/.specstory/history/2026-06-21_15-00-00Z-start-notif-badge.md
- fixtures/threads-foo/.specstory/history/2026-06-02_09-00-00Z-begin-checkout-flow.md
- fixtures/threads-foo/.specstory/history/2026-06-09_10-00-00Z-finish-checkout-flow.md
- fixtures/threads-foo/.specstory/history/2026-06-12_14-00-00Z-payment-retry-rollback.md
- install.sh
- package.json
- scripts/lib
- … and 9 more
Open the folder on GitHubat commit a0dd4db
Compare with similar skills
Workthreads next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Workthreads this skillspecstoryai/getspecstory | 1.3k | — | ~1.3k | Automated safety check: Notes | Apache-2.0 | |
| Git Worktree Managermicrosoft/WindowsAppSDK | 4.7k | — | ~2k | Automated safety check: Pass | MIT | |
| Roo Conflict Resolutionzgsm-ai/costrict | 4.4k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| ReleasePowerShell/vscode-powershell | 1.9k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Vscode981377660LMT/algorithm-study | 277 | 2 repos | ~290 | Automated safety check: Pass | None | |
| Agentbox Setupmadarco/agentbox | 523 | — | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
- Official
Roo Conflict Resolution
zgsm-ai/costrict
Provides comprehensive guidelines for resolving merge conflicts intelligently using git history and commit context.
Release
PowerShell/vscode-powershell
Guide for preparing a release of the PowerShell VS Code extension.
Vscode
981377660LMT/algorithm-study
VS Code integration for viewing diffs and comparing files. An agent skill from 981377660LMT/algorithm-study.
Agentbox Setup
madarco/agentbox
Generate an agentbox.yaml for the current AgentBox workspace.
Release
querylenshq/ef-querylens
A skill your agent uses when: creating a release, publishing a version, cutting a release, tagging a release, releasing plugin, release workflow, prepare release, create git tag, create GitHub…
More from specstoryai/getspecstory
Lore
specstoryai/getspecstory
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…
Related
Works with
Categories
Questions about Workthreads
What does Workthreads 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). Workthreads is an agent skill from specstoryai/getspecstory. 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).
When should I use Workthreads?
Workthreads fits situations like: someone asks what happened this week; what is still open; what did the team finish; give me the weekly rollup.
How do I install Workthreads in Claude Code?
Run `npx skills add specstoryai/getspecstory --skill workthreads -a claude-code`. Or copy the skill folder (workthreads in specstoryai/getspecstory) into .claude/skills/workthreads in your project. Claude Code loads it when a task matches its description.
How do I install Workthreads in Codex?
Run `npx skills add specstoryai/getspecstory --skill workthreads -a codex`. Or copy the skill folder (workthreads in specstoryai/getspecstory) into .agents/skills/workthreads in your project. Codex loads it when a task matches its description.
Can I use Workthreads in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add specstoryai/getspecstory --skill workthreads -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workthreads, .gemini/skills/workthreads, .github/skills/workthreads and .opencode/skills/workthreads in your project.
What does Workthreads need to run?
Going by SKILL.md and its folder, Workthreads needs a shell for the scripts in its folder and the command-line tools its instructions call (node and git). Our summary lists: A Bash shell. Its frontmatter pre-approves these tools: Bash, Read, Write, AskUserQuestion.
Does Workthreads access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Workthreads safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Workthreads use?
Workthreads is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Workthreads use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Workthreads?
Skills that share tags, products or a category with Workthreads: Git Worktree Manager (microsoft/WindowsAppSDK, 4.7k stars), Roo Conflict Resolution (zgsm-ai/costrict, 4.4k stars), Release (PowerShell/vscode-powershell, 1.9k stars) and Vscode (981377660LMT/algorithm-study, 277 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Workthreads?
specstoryai (a GitHub organization) maintains it in specstoryai/getspecstory, which has 1,348 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.
Source: specstoryai/getspecstory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.