Team
Run the four-role Herdr team (pm, po, dev, qa panes) that ships one feature of this repo. In the main session the user runs /team as the orchestrator (up, status, go, down); in a role pane the orchestrator prompts /team role: pm|po|dev|qa. Requires HERDR_ENV=1.
Install
npx skills add shenysun/skills-manager --skill teamgit clone --depth 1 https://github.com/shenysun/skills-manager.git /tmp/skills-manager
mkdir -p ~/.claude/skills
cp -r /tmp/skills-manager/.claude/skills/team ~/.claude/skills/teamPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Team
Four roles in Herdr panes ship one feature: **pm** grills and publishes the spec, **po** answers the grilling and rules on defects on the user's behalf, **dev** implements one ticket per invocation, **qa** derives and executes the acceptance checklist. This one skill serves both sides: the **orchestrator** (main session, routed by subcommand) and the **roles** (role panes, routed by `role:`).
Roles never share context. **Files are the interface**: every artifact lives in `.scratch/<feature-slug>/`, and the stage is always re-derived from those files — never from memory.
Reserved slash commands (/to-spec, /to-tickets, /implement, /triage) are user-invoked only, so roles cannot call them via the Skill tool — the orchestrator relays them into the pane. Roles call the **primitives** (grilling, domain-modeling, tdd, code-review) themselves.
## Orchestrator mode
You are not a fifth worker: you create the layout, route turns, and surface escalations to the user. For exact herdr command sequences, prompt texts, and the team.md format, load [references/orchestration.md](references/orchestration.md).
### Guards
1. Verify `test "${HERDR_ENV:-}" = 1`; otherwise say you are not inside Herdr and stop.
2. Confirm the cwd is this repo's root — role panes must start there to load `.claude/skills/`.
3. Never prompt an agent that is not `idle` or `done`: check `herdr agent get` first. A `blocked` role is waiting at a question or approval UI — never re-prompt it.Details
- Skill name
team- Repository
- shenysun/skills-manager
- Path
.claude/skills/team/SKILL.md- License
- MIT
- Repo updated
- 4 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Team skill do?
Run the four-role Herdr team (pm, po, dev, qa panes) that ships one feature of this repo. In the main session the user runs /team as the orchestrator (up, status, go, down); in a role pane the orchestrator prompts /team role: pm|po|dev|qa. Requires HERDR_ENV=1.
How do I install the Team skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add shenysun/skills-manager --skill team. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Team popular?
It lives in shenysun/skills-manager, which has 243 GitHub stars and 6 forks, and is included in 1 curated skill list.
Related skills
Skills Manager
243shenysun/skills-manager
Operate the skills-manager CLI — manage a local skill hub (install, import, distribute to agents/projects, update) and backfill provenance for source-less skills (adopt lockfile evidence, search the ecosystem for candidates, verify, get the user's approval, write sources). Use this skill whenever the user mentions skills-manager, the skill home / hub (~/.skills-manager), importing skills from agent runtime directories, distributing or undistributing skills, updating skills from their sources, tagging skills with domain categories (类别 / 分类 / categories), applying / inspecting a category set (类别
Gherkin Bdd
559KunoLu/640-skills
Use when adding, changing, reviewing, testing, synchronizing, or read-only ingesting user-visible behavior with BDD, Gherkin, Given/When/Then scenarios, .feature files, acceptance criteria, knowledge catalogs, or bug-fix behavior specs.
Plaid
221BuildGreatProducts/plaid
Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is
Maestro Mobile E2E
559KunoLu/640-skills
Use when generating or running Maestro Mobile/Hybrid E2E flows, deriving Maestro YAML from BDD `.feature` scenarios, configuring Maestro report paths, or debugging Maestro iOS real-device runs.
Ue Testing Debugging
468quodsoler/unreal-engine-skills
Use when writing or running Unreal Engine tests, adding logging, or profiling a build. Also use when the user mentions 'UE_LOG', 'log category', 'DEFINE_LOG_CATEGORY', 'UE_LOGFMT', 'verbosity', 'check', 'ensure', 'ensureMsgf', 'verify', 'IMPLEMENT_SIMPLE_AUTOMATION_TEST', 'automation test', 'TEST_CLASS', 'CQTest', 'AFunctionalTest', 'latent command', 'Unreal Insights', 'TRACE_CPUPROFILER_EVENT_SCOPE', 'TRACE_BOOKMARK', 'stat unit', 'SCOPE_CYCLE_COUNTER', 'memreport', 'DrawDebugLine', 'UE_VLOG', 'gameplay debugger', 'ShowDebug', 'console command', 'CVar', or 'why is my frame time bad'. For modu
Ab Test Setup
514Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI
Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.