Borrowing it
Nothing to install: this file belongs to shep-ai/shep. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shep-ai/shep/main/.claude/skills/shep-workstreams/SKILL.mdgit clone --depth 1 https://github.com/shep-ai/shepWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/shep-ai/shep/shep-workstreams)<a href="https://agentmods.dev/skills/shep-ai/shep/shep-workstreams"><img src="https://agentmods.dev/badge/skills/shep-ai/shep/shep-workstreams.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00147 | $0.02428 |
| Opus 5 | $0.00073 | $0.01214 |
| Sonnet 5 | $0.00029 | $0.00486 |
| Haiku 4.5 | $0.00015 | $0.00243 |
Grade A, and why
shep-workstreams scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workstream Breakdown & Parallel Execution with Shep
Turn a large, vague body of work into a small set of parallel workstreams, then execute each one as an isolated shep feature. One workstream = one feature = one worktree = one agent.
The rule this skill exists to enforce
Never tell an agent "work on all of it." That produces context loss, jumping between unrelated tasks, dozens of touched files, giant commits, and merge conflicts.
Act like a tech lead: partition first, then run one focused agent per partition.
Two phases, hard separated
PHASE 1 — PLAN PHASE 2 — EXECUTE
(read-only, no shep (shep feat new / start,
mutations, produces wave by wave, monitored)
WORKSTREAMS.md)
Do not create a single feature until Phase 1 is written down and the user has approved it. The plan is cheap. Rework across six half-merged branches is not.
Phase 1 — Produce the workstream plan
Step 1: Read every source doc, in full
Read all the input material (PRDs, design docs, roadmap, existing specs, issue lists) before writing anything. Then inventory the deliverables — not the docs, the actual things that must exist when this is done.
Step 2: Answer the five tech-lead questions
Answer these explicitly in the plan. They are the whole point of the exercise:
- What is on the critical path? Which deliverables block everything else, and which are genuinely independent?
- What does the dependency graph look like? Which files and components are shared between deliverables? Which subtrees are touched by exactly one deliverable?
- What is the right worktree split? Group deliverables into the smallest set of parallel branches that minimises merge conflicts. Estimate merge risk for each.
- What are the integration milestones? Replace "finish V6" with contract-level checkpoints ("backend contract frozen", "design system frozen", "CRUD complete", "QA").
- Which decisions are irreversible? What should be decided now because changing it later is expensive — and what should be deliberately delayed behind a flag?
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 211 lines · 147 tokens per session scan A f0d13614d027
shep-workstreams is a skill published in the GitHub repository shep-ai/shep (248 stars, last pushed 4d ago), licensed MIT. It adds 147 tokens to every session and 2,428 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
context-driven-development
Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a conductor/ directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when…