All authors
Claude Skills by thrum-team
github.com/thrum-team160 skills0 installs0 views
- Adversarial CritiqueUse when an implementer is blocked mid-work by a design flaw, contradiction, or unforeseen fork with 2-3 ways to resolve it - produces a defended pick that unblocks the work and leaves an audit trail so the decision can be revisited if it later proves wrongVotes: 0GitHub stars: 2
- Agent Messaging ProtocolUse when forwarding or relaying information between parties, routing an owner answer, carrying a decision or request through an intermediary, summarizing another author's message, or adding interpretation to someone else's words.Votes: 0GitHub stars: 2
- Brainstorm Queue AwareUse when running as a brainstormer that a Brainstorm Steward is managing — redirect every Q-by-Q question to the Steward as a NEED message and block for the ANSWER instead of asking the human directly. Fires when your briefing names a steward.Votes: 0GitHub stars: 2
- Brainstorm StewardUse when running as the Brainstorm Steward - a persistent watcher that manages a roster of brainstormers (often on other machines), multiplexes their NEED questions into one pane queue for the owner, routes ANSWERs back, and delegates launch and dual-review approval to coordinators (the brainstormer runs its own project-setup after approval). Never decides content.Votes: 0GitHub stars: 2
- Brainstormer Dashboard NeedsUse when running as a brainstormer or researcher whose steward/coordinator publishes NEEDs to the human via a dashboard board — author NEEDs as answerable action-picks, consume routed ANSWERS from dashboard results, and keep the board's view of your question in sync with reality.Votes: 0GitHub stars: 2
- Brainstormer Staying CurrentUse when a long-lived brainstormer worktree may be behind its configured merge target, before review or handoff, or when asked to merge-forward and leave the worktree clean. Resolves the target and merge owner from Thrum config, preserves local work, and verifies freshness after the merge.Votes: 0GitHub stars: 2
- Choosing Subagent ModelsUse before launching a subagent, an Agent or Task call, or an Explore agent, and on every review dispatch - code review, dual review, merge-gate reviewer. Picks the model and effort tier for the runtime you are running under.Votes: 0GitHub stars: 2
- Closing Findings While WarmUse whenever you are about to defer a finding, fix, or cleanup instead of doing it now - proposing a follow-up bead/issue/ticket, catching a sibling defect while wrapping up, feeling something is 'out of scope', or wanting to reach DONE faster. Also use on the manager side, when reviewing a completion report that proposes a deferral. Illustrative (non-exhaustive) phrasing that should trigger this - 'I'll file a follow-up', 'filing this as a P2', 'out of scope for now', 'tracked in a new bead'...Votes: 0GitHub stars: 2
- Configure RolesDetect environment and generate customized role-based preamble templates for your Thrum agents. Creates .thrum/role_templates/ files that auto-apply on agent registration.Votes: 0GitHub stars: 2
- Conversation Only ContextUse at the START of any long-lived agent session (researcher, coordinator, orchestrator, brainstormer), and whenever the operator says we are going to have a long conversation, get a lot done, or keep many threads open - also when context is climbing, when several investigations are in flight at once, when you are about to read code or a multi-file doc set to investigate, or when you catch yourself opening a log to just check quickly.Votes: 0GitHub stars: 2
- Coordinator Assessing Agent CompletionUse when deciding which live agents are finished and can be stood down - 'who can I shut down', 'which agents are done', 'reap dead worktrees', 'reduce the worktree count'. Builds a candidate list checked by direct liveness, never a kill list.Votes: 0GitHub stars: 2
- Coordinator Branch Split On BlockUse when a merge gate (hotpath, philosophy) or dual review BLOCKS on ONE concern of a branch that bundles multiple independent concerns, while the other concern(s) are clean - on a live multi-writer shared branch. Walks the split-land-recut sequence - separate the blocked concern from the clean one(s), land the clean half first, re-cut the blocked half onto the now-moved base, and verify the dropped commits are NOT ancestors of the re-cut tip before re-gating and merging.Votes: 0GitHub stars: 2
- Coordinator Dashboard Human LoopUse when the coordinator publishes or maintains a dashboard board FOR the human owner (roster, NEED queue, owner decisions, pipeline) or routes owner answers from a dashboard back to agents. Loads the human-loop mandate - a posted question is a PROMISE — it stays answerable and visible until answered, and nothing on the board disappears silently on your side.Votes: 0GitHub stars: 2
- Coordinator Deploying A NodeUse when deploying a build to a single node, migrating or not — deploying a build, schema-migrating deploy, pro-bundle install plus service restart on a node, roll out a build to a node, ship to a node, single-node canary. Loads the deploy runbook — verifying the artifact actually CONTAINS the fix, install-before-restart ordering, verify-by-effect, and preventing store corruption on migration.Votes: 0GitHub stars: 2
- Coordinator Dispatching WorkUse when starting an epic, dispatching to an implementer or orchestrator, choosing or re-routing which orchestrator gets a task, creating a worktree for an agent, or spawning a sub-agent. Loads coordinator-specific discipline for kicking off implementation work - routing by requirement and checking the target's load first.Votes: 0GitHub stars: 2
- Coordinator Hotpath Merge GateUse when a hot-path merge gate is dispatched to you or you are its Gate Runner, or before a coordinator runs git merge after a clean dual review. Loads the gate-runner restart rule and the hot-path lenses from the hotpath gate config.Votes: 0GitHub stars: 2
- Coordinator Interacting With The OwnerUse before writing to the human owner, escalating, or composing a thrum send or reply with prose - 'notify the owner', 'escalate', 'a notification just arrived', 'before restarting on a context reading'.Votes: 0GitHub stars: 2
- Coordinator Managing State And LifecycleUse when ending a session, when updating project state, when managing beads epics, or before session close. Loads coordinator-specific discipline for owning project state and shepherding the team's lifecycle.Votes: 0GitHub stars: 2
- Coordinator Merging CodeUse the moment code is presented for merge - a merge report arrives, an agent says MERGE-READY or RECOMMEND MERGE or the branch is ready, you are asked to approve or land or ship a branch, you are about to run git merge, or you are consolidating review findings before a merge. Loads the full merge sequence - dual review as a PRECONDITION not the gate, the mechanical merge-worthiness pre-gate, DISPATCHING both merge gates to the Gate Runner rather than walking the lenses yourself, tripwire che...Votes: 0GitHub stars: 2
- Coordinator Philosophy Merge GateUse when ABOUT TO START a philosophy merge gate - a gate has been dispatched to you, you are picking up a queued gate, you are the Gate Runner beginning a gate - and when a coordinator is about to run git merge on any new feature or large bug fix after dual review came back clean. Loads the gate-runner restart rule (restart at ~50 percent, at a seam BETWEEN gates) plus the FULL .thrum/philosophy.md anti-pattern list and red-flags checklist, walked as a distinct pass rather than folded into th...Votes: 0GitHub stars: 2
- Coordinator Plan Reconcile GateUse when parallel plans for one shared idea are all locked and about to feed project-setup, to check they compose at shared seams before any bead or worktree exists. Uses Fable, the one standing exception to the never-select-Fable rule.Votes: 0GitHub stars: 2
- Coordinator Rolling Out To NodesUse when rolling a build across all nodes — fleet deploy, rolling the nodes, deploy everywhere, ship to every node, canary then the rest, promote the canary, staged rollout, deploying after a merge batch. Orchestrates the staged order and the promotion gate between stages, and delegates each node to the coordinator-deploying-a-node runbook. Load this BEFORE dispatching any node.Votes: 0GitHub stars: 2
- Coordinator Running Autonomous Feature DevelopmentUse when the coordinator is idle or in a post-merge lull and a small, self-contained, reversible backlog item exists that could plausibly be developed and planned autonomously, with the finished plan still going to the human for go/no-go. Not for inventing work to stay busy, for cross-cutting / schema / release-gating items, for items the human flagged as theirs, or for the dispatch and execution mechanics themselves.Votes: 0GitHub stars: 2
- Coordinator Running Brainstorm CyclesUse when starting a brainstorm for a bug fix, feature, or architectural decision the coordinator can't trivially decide alone — spawns a researcher in an isolated worktree, runs the brainstorm interactively with the user, iterates dual-review cycles to ready-to-merge, optionally drives an overarching coherence pass when multiple sibling brainstorms close, then hands off to project-setup. Saves coordinator context by isolating brainstorm work in a sub-agent worktree rather than burning main-co...Votes: 0GitHub stars: 2
- Coordinator Running Review CyclesUse when an implementer reports DONE, when consolidating review findings, when handling implementer pushback on a finding, or when arriving at a review gate. Loads coordinator-specific discipline for running review cycles cleanly.Votes: 0GitHub stars: 2
- Coordinator Single Responsibility Merge GateDEPRECATED — superseded by `coordinator-philosophy-merge-gate`. Invoke that skill instead. (This stub is retained for backward discoverability; it redirects immediately.)Votes: 0GitHub stars: 2
- Deviations ProtocolUse when authoring a plan or implementation prompt - Deviations-from-Source block format, required even when empty.Votes: 0GitHub stars: 2
- Diagnosing Fleet And DaemonUse when the daemon or fleet looks broken - 'daemon down', 'connection refused', 'dial unix', 'database locked', 'agent looks dead', 'where is the daemon log'. Also use before restarting any daemon, for the pre-restart migration check.Votes: 0GitHub stars: 2
- Efficient Multi Agent ResearchUse when investigating, auditing, or reviewing more than 6 items across a codebase - function call sites, pattern usage, file reviews, or any research task with partitionable items that would pollute the main agent's context if read directlyVotes: 0GitHub stars: 2
- Fixing Documentation ErrorsUse the moment you notice docs are wrong, stale, or incomplete - a missing flag, a help text or llms.txt that disagrees with behaviour, a broken example. Triggers include 'the docs don't mention X', 'llms.txt is out of date', 'this example is wrong'.Votes: 0GitHub stars: 2
- Generator Idempotency ProtocolUse when generating config or docs from templates - idempotency invariant for generator skills.Votes: 0GitHub stars: 2
- Implementer Orchestrating ExecutionUse when starting execution of a scoped implementation task — about to implement, ready to write code, executing a bd task. Loads the orchestration procedure — dispatch research, implementation, and verification to sub-agents and synthesize their output instead of doing the legwork inline.Votes: 0GitHub stars: 2
- Implementer Receiving DispatchUse when receiving a new task from the coordinator, starting implementation, scoping a fresh task, or receiving dispatch. Loads implementer-specific discipline for kicking off work cleanly.Votes: 0GitHub stars: 2
- Implementer Receiving Review FeedbackUse when receiving review findings, when a reviewer flagged an issue, during a review cycle, or when responding to review. Loads implementer-specific discipline that complements superpowers:receiving-code-review.Votes: 0GitHub stars: 2
- Implementer Status And HandoffUse when reporting status to the coordinator, marking a task done, or handing off completed work. Loads implementer-specific discipline for closing the loop cleanly.Votes: 0GitHub stars: 2
- Implementer Tdd And QualityUse when writing tests, running tests, hitting a quality gate, or before reporting a task done. Loads project-specific test and quality discipline that complements superpowers:test-driven-development.Votes: 0GitHub stars: 2
- Memory MaintenanceUse when an agent needs to update, delete, supersede or audit an existing memory entry, or manage its edges, comments and hierarchy - after verification, when a finding goes stale, when a rule needs amendment, recovering a soft-deleted memory, or reading change history. Covers edit vs supersede, the unlink-supersede footgun and the hard-delete gate.Votes: 0GitHub stars: 2
- Memory Search AdvancedUse when running thrum memory search with RAG (--near), composing complex predicate stacks, paginating large result sets, interpreting MEM-001..010 hint codes, or diagnosing embedding adapter behavior. Loads three-vector ranking semantics, length-bias caveat, and the full hint catalog.Votes: 0GitHub stars: 2
- Memory To Thrum PointerUse when MEMORY.md is near or over its read limit, or when adding a new memory entry. Moves an entry's full text into a thrum memory record and shrinks its index line to a trigger plus the thrum memory ID, with a byte-for-byte check.Votes: 0GitHub stars: 2
- OrchestrateExecute a plan by launching agents in tmux sessions, managing epic-by-epic execution with review gates, and preparing merge reports. Use when the orchestrator receives a plan handoff from the coordinator.Votes: 0GitHub stars: 2
- Persistent Watcher ArchetypeUse when starting, launching or provisioning a watcher or steward - a coordinator asked to start a watcher on an agent or a roster - and when running as a persistent watcher agent that watches other agents' tmux panes, auto-approves safe modals, warns on context, and escalates up a parent-reference tree. Starting one means running resources/start-watcher.sh, never a hand-built monitor. Distinct from watcher-archetype (the wake-run-exit scan/emit/report substrate) — this archetype stays alive.Votes: 0GitHub stars: 2
- Prime AgentUse on scheduled-agent wake or lean prime restart - replaces the full thrum prime briefing with a lean two-step warmup tuned for short-lived scheduled-agent invocations. Step 1 reads the inbox literally (NOT a discipline assumption); step 2 surfaces newly-shipped skills since the agent last ran.Votes: 0GitHub stars: 2
- Project Gate SetupUse when a project needs its landing-gate configuration established or updated - the canonical config at .thrum/gate-config.json naming the per-landing test, race and lint commands, the focused-versus-full rule, how to build the merged tree, the structural checks, the verdict log and the evidence retention the gate role follows. Detects Go, Node/TypeScript, Python and Rust from the repo, asks when unsure, and writes the file the gate role reads at gate time. Triggers - set up the gate, config...Votes: 0GitHub stars: 2
- Project Hotpath GateUse when a project needs its hot-path gate configuration established or updated - the canonical config at .thrum/hotpath-gate.json defining trigger directories, per-concept detection patterns, and incident prose for the coordinator-hotpath-merge-gate skill. Detects every language present in the repo and drives detection off the shared reliability-class library, so the generated config is real for Go, Python, JS/TS, Rust, or any mix. First invocation generates from project inspection; subseque...Votes: 0GitHub stars: 2
- Project PhilosophyUse when a project needs its implementation philosophy established or updated — the canonical doc at .thrum/philosophy.md defining anti-patterns, red flags, and project-specific rules that implementation agents read at task-start time. First invocation generates from project inspection; subsequent invocations reconcile against current project state and propose diffs.Votes: 0GitHub stars: 2
- Project Rules ProtocolUse when loading project-specific rules - shared rule skill for role skills.Votes: 0GitHub stars: 2
- Project SetupUse when converting a plan file (from writing-plans skill) into beads epics, tasks, implementation prompts, and worktrees — before any coding beginsVotes: 0GitHub stars: 2
- Researcher Answering QueriesUse when another agent has asked you a research question, when fielding a research request, or when responding to a query. Loads the lookup-and-respond protocol so cached findings get reused before fresh investigation starts.Votes: 0GitHub stars: 2
- Researcher InvestigatingUse when investigating, exploring code, working on a research task, when asked to find me X, or to investigate Y. Loads researcher-specific discipline for running an investigation cleanly.Votes: 0GitHub stars: 2
- Routing Messages Across DaemonsUse when thrum send fails with unknown recipient, when sending a cross-box message to an agent on another daemon, when there is no second hop, when you need to route or relay through a paired peer, reach an agent on another box, or tmux send to a remote agent.Votes: 0GitHub stars: 2