team
Skill2 starsChanged 8 months agoApache-2.0View on GitHub
Full multi-agent team review using parallel subagents. Spawns Architect, SecOps, Tester, DevOps, and Verifier concurrently, then consolidates into a prioritized action plan.
50 other projects use a version of this.
Adopted by
Most recently taken up by
- ddivyanshsharmaa/fable-toolkittheir own version, first seen Nov 16, 2026
- shanren/maestrotheir own version, first seen Nov 16, 2026
- Yomudogly/oh-my-agytheir own version, first seen Nov 16, 2026
- kele-dev/Claude-Orchestrator-Skilltheir own version, first seen Nov 16, 2026
- esbenboye/ClaudeCodetheir own version, first seen Nov 15, 2026
- sungminpark-biz/tandem-skillstheir own version, first seen Nov 9, 2026
Used with
Projects with it also use community-led-growth, ph-community-outreach and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
nicepkgSkillph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Also in 5 projects that use this
xfstudioSkillmicro-saas-launcher
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
Also in 5 projects that use this
mastepanoskiSkillux-audit-rethink
Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.
Also in 5 projects that use this
ibahgatSkillralplan
Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.
Also in 8 projects that use this
ncklrsSkillseo-content-strategist
Expert SEO content strategy for SaaS and B2B sites. Use when doing keyword research, planning content clusters, creating pillar pages, optimizing on-page SEO, fixing technical SEO issues, building links, refreshing content, implementing programmatic SEO, mapping search intent, optimizing for SERP features, or measuring content performance. Use for SEO audits, content gap analysis, and organic growth strategy.
Also in 5 projects that use this
- +6 more from nicepkg
Other versions50 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 50
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-codex★ 34ksame name
- MaxMiksa/Auto-Company★ 3.2ksame name
- MaxMiksa/Autonomous-Company★ 3.2ksame name
- zereight/gitlab-mcp★ 2.1ksame name
- nicepkg/ctxport★ 629same name
- ansari-project/codev★ 298same name
- cluesmith/codev★ 298same name
- shenysun/skills-manager★ 243same name
40 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- commit-push-prSkill
- freshSkill
- goSkill
- grillSkill
- investigateSkill
- prove-itSkill
- retroSkill
- saveSkill
- secreviewSkill
- statusSkill
- tddSkill
- techdebtSkill
- test-and-fixSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 36 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Run a multi-agent review of the current change or feature using parallel subagents.
- Distinctive: line 24
Use a single message with multiple Task tool calls:
- Distinctive: line 34
Handling subagent failures: If any agent returns INCOMPLETE or ESCALATING, note it in the consolidation.
- Distinctive: line 36
All five agents run in parallel.
- Distinctive: line 40
After all agents return, synthesize their findings into a single prioritized report.
- Distinctive: line 44
If the review reveals implementation complexity, note where Simplifier could reduce it.
- Distinctive: line 82
Before merging a significant change
- Distinctive: line 85
After a dependency update or security advisory
“Common” is measured: kept by at least 6 in 10 of the 36 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/team — Full Team Review
Run a multi-agent review of the current change or feature using parallel subagents. Each agent runs in its own context window for deep, focused analysis.
Target
$ARGUMENTS
Process
Step 1 — Parallel Agent Spawn
Launch all five review agents concurrently using the Task tool. Each agent gets the review target as context and produces a focused assessment.
Use a single message with multiple Task tool calls:
- Architect (
subagent_type: architect,model: "opus") — Think deeply about the architectural implications. Evaluate system design, module boundaries, API contracts, and dependency decisions for: $ARGUMENTS - SecOps (
subagent_type: secops,model: "opus") — Think deeply about the security implications. Enumerate all attack vectors. Security review: input validation, crypto correctness, dependency vulnerabilities, secret detection for: $ARGUMENTS - Tester (
subagent_type: tester) — Identify test gaps, suggest edge cases, evaluate coverage for: $ARGUMENTS - DevOps (
subagent_type: devops) — Assess build/deploy impact, CI pipeline changes, configuration updates for: $ARGUMENTS - Verifier (
subagent_type: verifier) — Run tests, lint, and build checks. Report current pass/fail state for: $ARGUMENTS
Note: Architect and SecOps use extended thinking (model: "opus") for deeper analysis. Tester, DevOps, and Verifier use standard model for speed.
Handling subagent failures: If any agent returns INCOMPLETE or ESCALATING, note it in the consolidation. Don't re-spawn — report the partial result with the agent's handoff notes.
All five agents run in parallel. Wait for all to complete before proceeding.
Step 2 — Consolidation
After all agents return, synthesize their findings into a single prioritized report. Cross-reference findings — if SecOps flags a vulnerability and Tester is missing a test for it, link them. If Architect suggests a design change and DevOps sees a build impact, connect those.
Step 3 — Simplification Check
If the review reveals implementation complexity, note where Simplifier could reduce it. This is advisory — don't spawn Simplifier unless the user asks.
Output
# Team Review: [Subject]
## Architect
[Design assessment — API contracts, module boundaries, dependency impact]
## SecOps
[Security findings — risk level: LOW/MEDIUM/HIGH/CRITICAL]
## Tester
[Coverage assessment — gaps found, edge cases to add, recommended tests]
## DevOps
[Build/deploy impact — CI changes, config updates, infrastructure needs]
## Verifier
[Current state — tests passing/failing, lint status, build status]
## Simplification Opportunities
[Where complexity could be reduced, or "None identified"]
## Action Plan
Priority 1 (Blocking):
- [ ] [item — agent source]
Priority 2 (Should fix):
- [ ] [item — agent source]
Priority 3 (Nice to have):
- [ ] [item — agent source]When to Use
- Before merging a significant change
- Reviewing a new feature's design and implementation
- Assessing project posture or technical debt
- After a dependency update or security advisory
- Any time the user invokes
/teamwith a review target
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

