Sub-skill of agent-teams: Decision Matrix: Team vs Sequential.
Scanned 9/9/2026
Install to Claude Code
npx -y skills add vamseeachanta/workspace-hub --skill decision-matrix-team-vs-sequential --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Decision Matrix Team Vs Sequential?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-decision-matrix-team-vs-sequential)More formats (shields.io, HTML) on the badges page.
---
name: agent-teams-decision-matrix-team-vs-sequential
description: 'Sub-skill of agent-teams: Decision Matrix: Team vs Sequential.'
version: 1.0.0
category: workspace-hub
type: reference
scripts_exempt: true
---
# Decision Matrix: Team vs Sequential
## Decision Matrix: Team vs Sequential
| Task profile | Use team? | Rationale |
|-------------|-----------|-----------|
| < 5 files, single domain | **No** | Sequential is faster than team overhead |
| Writing WRK items / skills | **No** | Small, sequential, ~minutes each |
| 3+ independent workstreams > 20 min each | **Yes** | Parallelism pays off |
| Bulk file transforms (50+ files) | **Yes** | Bash agent per batch |
| Research + implementation (separate concerns) | **Yes** | Explore agent + Bash agent |
| Cross-repo changes (each repo independent) | **Yes** | One agent per repo |
| WRK-205 knowledge graph (115 files) | **Yes** | 3 parallel streams |
**Rule of thumb**: If you would finish faster doing it yourself than explaining
it to a teammate, do it yourself.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".