agent-teams
Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team…
The index of every pro-workflow skill and command, grouped by job, with when to reach for each and whether it is human-run or auto-triggered. Use when you are not sure which skill fits, want the full map, or ask "what can this do", "which skill for X", "list the workflow".
$ npx -y skills add rohitg00/pro-workflow --skill skill-router --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/skill-routerContext preview
The summary Claude sees to decide when to auto-load this skill.
The index of every pro-workflow skill and command, grouped by job, with when to reach for each and whether it is human-run or auto-triggered. Use when you are not sure which skill fits, want the full map, or ask "what can this do", "which skill for X", "list the workflow".
name: skill-router description: The index of every pro-workflow skill and command, grouped by job, with when to reach for each and whether it is human-run or auto-triggered. Use when you are not sure which skill fits, want the full map, or ask "what can this do", "which skill for X", "list the workflow". user-invocable: true
You cannot hold 41 skills and 23 commands in your head. This is the index so you do not have to. Each entry says what it is for and how it fires: `[human]` you invoke it deliberately, `[auto]` the agent reaches for it from your prompt.
Keep this honest. When a skill is added, renamed, removed, or changes how it fits a flow, update this file in the same change. A router that points at a skill that no longer exists, or omits a new one, is worse than none.
State the job in one line. Match it to a group below. If two skills look close, the `when to reach` clause is the tiebreaker. Most skills have a matching slash command of the same name, so this index covers commands too.
These slash commands ship without a skill of the same name: `/commit`, `/develop`, `/doctor`, `/handoff`, `/learn`, `/list`, `/parallel`, `/replay`, `/search`, `/skill-optimize`, `/wiki`.
Every skill declares one intent. `[human]` skills are deliberate, side-effectful, or session rituals and carry `user-invocable: true`. `[auto]` skills earn their place in context by a description precise enough to fire on the right prompt and stay quiet otherwise. See [`rules/skill-conventions.mdc`](../../rules/skill-conventions.mdc) for the full convention and the write-operation rules for state-changing skills.
Claude Code learns from your corrections: self-correcting memory that compounds over 50+ sessions. Context engineering, parallel worktrees, agent teams, and 17 battle-tested skills.
Repo: rohitg00/pro-workflow
Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team…
Auto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate tooling. Use when onboarding a new codebase.
Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change…
Capture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never…
Smart context compaction with state preservation. Saves critical files, task progress, and working state before compaction, restores after. Use before manual…
Master the four operations of context engineering — Write, Select, Compress, Isolate. Manage token budgets, compaction strategies, and context partitioning to…