Skip to content

specstoryai/getspecstory / workthreads

workthreads

Flagged

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.

install.sh

View on GitHub
#!/usr/bin/env bash
# Install the workthreads skill so it is available from any Claude Code session.
#
# Self-contained: bundles workthreads' own engine. No dependency on any other skill.
# Re-run any time to update. Pass a target dir to override the default.
set -euo pipefail

HERE="$(cd "$(dirname "$0")" && pwd)"          # .../workthreads
DEST="${1:-$HOME/.agents/skills/workthreads}"

if [ ! -f "$HERE/scripts/workthreads.mjs" ]; then
  echo "error: engine not found at $HERE/scripts - run this from the workthreads/ directory of a clone." >&2
  exit 1
fi

mkdir -p "$DEST"
rm -rf "$DEST/scripts"
cp -R "$HERE/scripts" "$DEST/scripts"          # bundle the self-contained engine
cp "$HERE/SKILL.md" "$DEST/SKILL.md"           # SKILL.md calls ${CLAUDE_SKILL_DIR}/scripts/workthreads.mjs

mkdir -p "$HOME/.claude/skills"
ln -sfn "$DEST" "$HOME/.claude/skills/workthreads"

echo "installed workthreads:"
echo "  skill  -> $DEST"
echo "  linked -> $HOME/.claude/skills/workthreads"
echo "Open a new Claude Code session, then run /workthreads (skills load at session start)."
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall