team-workflow plugin
Seventeen skills that ship as one pack — a portable discipline for tracked, multi-session, agent-assisted development: the orchestrator seat a non-engineer works from (one session routing, auditing, and merging parallel lanes), a router entry point, a once-per-repo setup interview that records whether you lead from that seat or read code and pick skills, per-repo institutional memory written as side effects of work, relentless grilling, decision maps, throwaway prototypes, autonomous research lanes, ticket filing, human-step wizards, session handoffs, a build discipline of seam-scoped test-first tracer slices, a disciplined bug-diagnosis loop where no fix ships without a named cause, an adversarial review that breaks changes before they ship, a skeptic-verified state review of the codebase itself, an append-only decision trail that lets a human audit an unattended run after stepping away, and a PR-writing standard that leads with the problem, shows before-and-after proof, and says whet
How to install the team-workflow plugin
Run both commands inside Claude Code. The first adds the marketplace once; the second installs the plugin.
/plugin marketplace add timharris707/skills
/plugin install team-workflow@skillsWhat's inside team-workflow
17 parts read from the plugin's own files.
Skills 17
Claude loads it when the task matches- adversarial-review
Run an adversarial review of a change before it ships: isolated finders trying to break it, a skeptic pass that kills unproven findings, and a gate on confirmed blockers. Use before committing substantial work, at lane close-out, when the user asks for an adversarial or red-team review of a diff/branch/PR, or before external reviewers see the change.
- codebase-review
Run a state review of the codebase: the counterpart to adversarial-review's change review. Use before building against an upcoming spec (make the change easy first), when lanes merged since the last review cross the repo's threshold, or when lanes or the orchestrator report the code fighting them.
- decision-map
Chart or work a decision map for genuinely foggy work before any build slice is written: a new primitive, a milestone charter, an integration nobody can spec in one sitting. Use when asked to chart a decision map, work a map ticket, or plan a decision-heavy effort whose open questions gate each other.
- diagnose
The disciplined bug-fixing loop: no fix ships without a cause the fixer can state in one plain sentence, with evidence. Use when any fix is about to ship without a nameable cause, when a bug resists its first fix attempt, or when a bug-shaped lane brief points here.
- domain-memory
Keep per-repo institutional memory: a domain glossary plus lightweight decision records, written as side effects of work. Use when a grilling closes, a review rejection or declined finding is dispositioned, the decider corrects a session's wrong assumption, a session starts in a repo whose binding names a memory home, or the store passes its size bound.
- grilling
Interview the decider relentlessly to turn a half-formed plan, design, or idea into shared understanding: a design tree worked in rounds until nothing is silently assumed. Use when asked to grill, stress-test, or pressure-test thinking, and before charting a decision map or writing a spec off a conversation nobody has pressure-tested.
- handoff
Write a structured session handoff so a fresh session resumes losslessly. Use when context is filling up (around half the window), when wrapping a work session, or when the user says "handoff", "checkpoint", "wrap up", or "save state".
- implement
How a working lane builds an item: seam-scoped test-first, tracer-first sequencing, a green checkpoint per slice, and file-don't-fix scope discipline. Use when a build-shaped lane brief points here, when implementing a spec or tracked item, or when mid-build discoveries tempt a lane beyond its brief.
- orchestrate
Run one session as the lead developer of an agent team: it takes tracked work, routes it into parallel lanes, audits what comes back, and owns the merge, so the human brings decisions and never implements. Use when the user says "orchestration mode", asks one session to coordinate several lanes/sessions, or hands over an orchestrator role.
- pr-writing
Write a pull request the decider can judge from its description alone: problem first, before-and-after evidence, a can-we-undo call. Use when filing a PR, updating a PR description, responding to PR review feedback, or writing a PR or review-thread comment on someone's behalf.
- prototype
Build throwaway prototype code that answers a design question: UI variants on a live route, or a terminal UI or single shareable HTML file over a pure logic module. Use when a question is "how should this look / behave / feel in action" and discussion or static artifacts cannot settle it.
- research
Run an autonomous research lane against primary sources, ending in cited findings and, when the missing facts are human-held, a questionnaire. Use for investigations of vendor materials, regulations, upstream repos, recorded calls, or any fact-finding that should run fire-and-report.
- router
Entry point for the team-workflow pack: names every pack skill and when to reach for it. Use when unsure which team-workflow skill applies, or to orient a new session/repo on what the pack offers.
- setup
Once-per-repo binding interview for the team-workflow pack: records how the pack composes with this repo and seeds the binding doc the other skills read. Use when installing the pack into a repo, refreshing an existing installation's bindings, or auditing a consuming repo for drift after a pack release (audit mode).
- show-me-your-work
Keep a reviewable decision trail for long-running or unattended work: one append-only TSV log, one row per decision with its why, evidence, and result. Use when starting an autonomous, multi-phase, or loop run a human reviews after stepping away, when a reviewer needs the trail to trust a result without rerunning it, or when the user asks for a decision log or says show your work.
- to-tickets
Turn a plan, a spec, a closed decision map, or a pressure-tested conversation into tracer-bullet work items on the repo's tracker, each an issue-as-spec with its blocking edges wired. Use when asked to file tickets, break work down, or move from "we've decided" to "it's on the board".
- wizard
Generate an interactive bash wizard that walks a human through a procedure only they can perform: third-party dashboards, credentials, DNS records, CI secrets, one-off cutovers. Use when a task stalls on steps an agent cannot take, or when a manual setup is tedious to re-explain every time. Not for steps the agent can perform itself.
Using team-workflow in Claude Code
Skills need no command. Claude reads them when your request matches what they describe.
Update, turn off or remove
- Update the plugin (shell)
- claude plugin update team-workflow@skills
- Refresh the marketplace
- /plugin marketplace update skills
- Turn it off for now
- /plugin disable team-workflow@skills
- Remove it
- /plugin uninstall team-workflow@skills
Skills in team-workflow
- adversarial-reviewtimharris707/skills
Run an adversarial review of a change before it ships: isolated finders trying to break it, a skeptic pass that kills unproven findings, and a gate on confirmed blockers. Use before committing substantial work, at lane close-out, when the user asks for an adversarial or red-team review of a diff/branch/PR, or before external reviewers see the change.
2 files45stars - codebase-reviewtimharris707/skills
Run a state review of the codebase: the counterpart to adversarial-review's change review. Use before building against an upcoming spec (make the change easy first), when lanes merged since the last review cross the repo's threshold, or when lanes or the orchestrator report the code fighting them.
3 files45stars - decision-maptimharris707/skills
Chart or work a decision map for genuinely foggy work before any build slice is written: a new primitive, a milestone charter, an integration nobody can spec in one sitting. Use when asked to chart a decision map, work a map ticket, or plan a decision-heavy effort whose open questions gate each other.
3 files45stars - diagnosetimharris707/skills
The disciplined bug-fixing loop: no fix ships without a cause the fixer can state in one plain sentence, with evidence. Use when any fix is about to ship without a nameable cause, when a bug resists its first fix attempt, or when a bug-shaped lane brief points here.
2 files45stars - domain-memorytimharris707/skills
Keep per-repo institutional memory: a domain glossary plus lightweight decision records, written as side effects of work. Use when a grilling closes, a review rejection or declined finding is dispositioned, the decider corrects a session's wrong assumption, a session starts in a repo whose binding names a memory home, or the store passes its size bound.
3 files45stars - grillingtimharris707/skills
Interview the decider relentlessly to turn a half-formed plan, design, or idea into shared understanding: a design tree worked in rounds until nothing is silently assumed. Use when asked to grill, stress-test, or pressure-test thinking, and before charting a decision map or writing a spec off a conversation nobody has pressure-tested.
2 files45stars - handofftimharris707/skills
Write a structured session handoff so a fresh session resumes losslessly. Use when context is filling up (around half the window), when wrapping a work session, or when the user says "handoff", "checkpoint", "wrap up", or "save state".
3 files45stars - implementtimharris707/skills
How a working lane builds an item: seam-scoped test-first, tracer-first sequencing, a green checkpoint per slice, and file-don't-fix scope discipline. Use when a build-shaped lane brief points here, when implementing a spec or tracked item, or when mid-build discoveries tempt a lane beyond its brief.
2 files45stars - orchestratetimharris707/skills
Run one session as the lead developer of an agent team: it takes tracked work, routes it into parallel lanes, audits what comes back, and owns the merge, so the human brings decisions and never implements. Use when the user says "orchestration mode", asks one session to coordinate several lanes/sessions, or hands over an orchestrator role.
6 files45stars - pr-writingtimharris707/skills
Write a pull request the decider can judge from its description alone: problem first, before-and-after evidence, a can-we-undo call. Use when filing a PR, updating a PR description, responding to PR review feedback, or writing a PR or review-thread comment on someone's behalf.
2 files45stars - prototypetimharris707/skills
Build throwaway prototype code that answers a design question: UI variants on a live route, or a terminal UI or single shareable HTML file over a pure logic module. Use when a question is "how should this look / behave / feel in action" and discussion or static artifacts cannot settle it.
4 files45stars - researchtimharris707/skills
Run an autonomous research lane against primary sources, ending in cited findings and, when the missing facts are human-held, a questionnaire. Use for investigations of vendor materials, regulations, upstream repos, recorded calls, or any fact-finding that should run fire-and-report.
3 files45stars - routertimharris707/skills
Entry point for the team-workflow pack: names every pack skill and when to reach for it. Use when unsure which team-workflow skill applies, or to orient a new session/repo on what the pack offers.
2 files45stars - setuptimharris707/skills
Once-per-repo binding interview for the team-workflow pack: records how the pack composes with this repo and seeds the binding doc the other skills read. Use when installing the pack into a repo, refreshing an existing installation's bindings, or auditing a consuming repo for drift after a pack release (audit mode).
5 files45stars - show-me-your-worktimharris707/skills
Keep a reviewable decision trail for long-running or unattended work: one append-only TSV log, one row per decision with its why, evidence, and result. Use when starting an autonomous, multi-phase, or loop run a human reviews after stepping away, when a reviewer needs the trail to trust a result without rerunning it, or when the user asks for a decision log or says show your work.
4 files45stars - to-ticketstimharris707/skills
Turn a plan, a spec, a closed decision map, or a pressure-tested conversation into tracer-bullet work items on the repo's tracker, each an issue-as-spec with its blocking edges wired. Use when asked to file tickets, break work down, or move from "we've decided" to "it's on the board".
2 files45stars - wizardtimharris707/skills
Generate an interactive bash wizard that walks a human through a procedure only they can perform: third-party dashboards, credentials, DNS records, CI secrets, one-off cutovers. Use when a task stalls on steps an agent cannot take, or when a manual setup is tedious to re-explain every time. Not for steps the agent can perform itself.
3 files45stars
team-workflow plugin questions
How do I install the team-workflow plugin?
In Claude Code run /plugin marketplace add timharris707/skills, then /plugin install team-workflow@skills.
What does the team-workflow plugin include?
team-workflow bundles 17 skills.
How do I update or remove the team-workflow plugin?
Update it with claude plugin update team-workflow@skills in your shell, or from the Installed tab of /plugin. Remove it with /plugin uninstall team-workflow@skills.
What license is the team-workflow plugin under?
MIT, as stated in the plugin's manifest.