workflow-team — for Claude Code workflow-team, claude-rr7-starterkit, community, for Claude Code, ide skills, workflow-team lead, workflow-team teammate, PlanMode, CLAUDE.md, TaskCreate

v1.0.0
GitHub

Sobre este Skill

Cenario recomendado: Ideal for AI agents that need agent teams workflow. Resumo localizado: # Agent Teams Workflow Autonomous parallel development workflow for Agent Teams. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Recursos

Agent Teams Workflow
Autonomous parallel development workflow for Agent Teams.
Invoke with: /workflow-team lead or /workflow-team teammate
For Team Lead (/workflow-team lead)
2 Read CLAUDE.md, docs/PROJECT-STRUCTURE.md, docs/ROADMAP.md

# Core Topics

for Claude Code workflow-team lead workflow-team teammate PlanMode CLAUDE.md TaskCreate
onepunch-tk onepunch-tk
[0]
[0]
Updated: 3/18/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
8/11
Quality Score
46
Canonical Locale
en
Detected Body Locale
en

Cenario recomendado: Ideal for AI agents that need agent teams workflow. Resumo localizado: # Agent Teams Workflow Autonomous parallel development workflow for Agent Teams. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Por que usar essa habilidade

Recomendacao: workflow-team helps agents agent teams workflow. Agent Teams Workflow Autonomous parallel development workflow for Agent Teams. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Melhor para

Cenario recomendado: Ideal for AI agents that need agent teams workflow.

↓ Casos de Uso Práticos for workflow-team

Caso de uso: Applying Agent Teams Workflow
Caso de uso: Applying Autonomous parallel development workflow for Agent Teams
Caso de uso: Applying Invoke with: /workflow-team lead or /workflow-team teammate

! Segurança e Limitações

  • Limitacao: 3 Use Delegate Mode (Shift+Tab) — do NOT implement yourself
  • Limitacao: - Lead MUST verify NO file overlap before spawning teammates
  • Limitacao: - Use git diff --name-only to check for conflicts before merge

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is workflow-team?

Cenario recomendado: Ideal for AI agents that need agent teams workflow. Resumo localizado: # Agent Teams Workflow Autonomous parallel development workflow for Agent Teams. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install workflow-team?

Run the command: npx killer-skills add onepunch-tk/claude-rr7-starterkit/workflow-team. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for workflow-team?

Key use cases include: Caso de uso: Applying Agent Teams Workflow, Caso de uso: Applying Autonomous parallel development workflow for Agent Teams, Caso de uso: Applying Invoke with: /workflow-team lead or /workflow-team teammate.

Which IDEs are compatible with workflow-team?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for workflow-team?

Limitacao: 3 Use Delegate Mode (Shift+Tab) — do NOT implement yourself. Limitacao: - Lead MUST verify NO file overlap before spawning teammates. Limitacao: - Use git diff --name-only to check for conflicts before merge.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add onepunch-tk/claude-rr7-starterkit/workflow-team. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use workflow-team immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

workflow-team

# Agent Teams Workflow Autonomous parallel development workflow for Agent Teams. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Agent Teams Workflow

Autonomous parallel development workflow for Agent Teams. Invoke with: /workflow-team lead or /workflow-team teammate

For Team Lead (/workflow-team lead)

Phase 1: Plan

StepAction
1Enter PlanMode
2Read CLAUDE.md, docs/PROJECT-STRUCTURE.md, docs/ROADMAP.md
3Analyze task scope, identify required files and dependencies
4Break work into tasks with clear file ownership (no overlapping files)
5Create detailed step-by-step plan with task breakdown
6Exit PlanMode → wait for plan approval

After plan approval, create tasks via TaskCreate and spawn teammates immediately. No separate confirmation needed.

Phase 2: Execute (after user approval)

StepAction
1Switch to development branch, create a working branch for the team
2Spawn teammates with detailed prompts (see Spawn Example below)
3Use Delegate Mode (Shift+Tab) — do NOT implement yourself
4Monitor teammate progress, unblock as needed

Enable Plan Approval for complex/risky tasks. All teammates work on the same feature branch.

WARNING: File Ownership is CRITICAL

  • Overlapping file assignments = merge conflicts = wasted work
  • Lead MUST verify NO file overlap before spawning teammates
  • Use git diff --name-only to check for conflicts before merge

Spawn Example

Create an agent team with N teammates:
1. "{name}" — Read {task-file-path}. Own files: {file-list}.
2. "{name}" — Read {task-file-path}. Own files: {file-list}.
Use Opus for all teammates. Require plan approval.

Phase 3: Review & Merge (after all teammates complete)

StepAction
1Run the project's test command (see CLAUDE.md Commands) to verify integration
2Run code-reviewer sub-agent on all changed files
3Run e2e-tester sub-agent to validate user flows
4Read report in /docs/reports/code-review/ → fix ALL issues where status ≠ "complete"
5Merge working branch → development
6Update ROADMAP.md and PROJECT-STRUCTURE.md

Merge Strategy

main
 └── development
      └── {working-branch}  ← single branch, all teammates work here
           ├── teammate-A commits (owns: file-list-A)
           ├── teammate-B commits (owns: file-list-B)
           └── teammate-C commits (owns: file-list-C)

After all teammates done → Phase 3

Git Conventions

See workflow-commits.md

For Teammates (/workflow-team teammate)

Execution Steps

StepAction
1Read CLAUDE.md, docs/PROJECT-STRUCTURE.md, assigned task file
2Run unit-test-writer sub-agent (Red Phase). NEVER analyze patterns or write test code yourself — always delegate to the unit-test-writer subagent.
3Implement code to pass tests (Green Phase) → run the project's test command (see CLAUDE.md Commands)
4Run the project's coverage command (see CLAUDE.md Commands)
5Commit per workflow-commits.md
6Message lead: files changed, test results, remaining issues

Teammate Rules

  • ONLY modify files assigned to you
  • NEVER touch files owned by another teammate
  • Shared files (barrel index.ts, routes.ts): message lead before modifying
  • New files: create freely within your task scope
  • Do NOT create branches — work on the feature branch created by lead

Failure Recovery (Autonomous)

IF any step fails:
  1. Log to docs/reports/failures/{teammate-name}-{timestamp}.md
  2. Retry SAME approach (1 attempt)
  3. Retry DIFFERENT approach (1 attempt)
  4. After 3 failures:
     → Message lead: "Blocked on [issue]. Attempted [approaches]."
     → Pick up next available task
     → DO NOT STOP

Communication

EventAction
Task completeMessage lead with summary
Blocked by another taskMessage lead, pick up next task
Found issue in shared codeMessage lead (don't fix directly)
Need design decisionMessage lead with options + recommendation

Cost Notes

  • Use opus model for teammates
  • Teammates: NO code-reviewer — TDD cycle is the quality gate, lead handles all review in Phase 3
  • Lead runs code-reviewer + e2e-tester as the single review gate post-merge
  • Minimize sub-agent calls per teammate
  • Avoid broadcast messages — message lead directly

Habilidades Relacionadas

Looking for an alternative to workflow-team or another community skill for your workflow? Explore these related open-source skills.

Ver tudo

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
Inteligência Artificial

widget-generator

Logo of f
f

Gerar plugins de widgets personalizáveis para o sistema de feed do prompts.chat

★ 149.6k
⑂ 0
Inteligência Artificial

flags

Logo of vercel
vercel

O Framework React

★ 138.4k
⑂ 0
Navegador

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Desenvolvedor