workflow-team — autonomous parallel development workflow workflow-team, cc-test-notion-invoice-web, community, autonomous parallel development workflow, ide skills, workflow-team install, workflow-team lead command, workflow-team teammate command, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Ideal for Team Lead Agents and teammates requiring autonomous parallel development workflows with automated task and dependency analysis. workflow-team is an autonomous parallel development workflow for Agent Teams, facilitating task management and dependency analysis.

Features

Invokes workflow with /workflow-team lead or /workflow-team teammate commands
Enters PlanMode for task scope analysis and file dependency identification
Breaks work into tasks with clear file ownership using CLAUDE.md and PROJECT-STRUCTURE.md
Analyzes task scope and identifies required files and dependencies
Reads ROADMAP.md for project planning and management

# Core Topics

autonomous parallel development workflow workflow-team install workflow-team lead command workflow-team teammate command
onepunch-tk onepunch-tk
[0]
[0]
Updated: 3/8/2026

Agent Capability Analysis

The workflow-team skill by onepunch-tk is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance. Optimized for autonomous parallel development workflow, workflow-team install, workflow-team lead command.

Ideal Agent Persona

Ideal for Team Lead Agents and teammates requiring autonomous parallel development workflows with automated task and dependency analysis.

Core Value

Empowers agents to invoke workflow-team lead or teammate modes, analyzing task scope, identifying required files and dependencies, and breaking work into tasks with clear file ownership using CLAUDE.md, PROJECT-STRUCTURE.md, and ROADMAP.md.

↓ Capabilities Granted for workflow-team

Automating task assignments for team members
Analyzing dependencies between project files
Generating parallel development workflows for Agent Teams

! Prerequisites & Limits

  • Requires access to CLAUDE.md, docs/PROJECT-STRUCTURE.md, and docs/ROADMAP.md files
  • Limited to Agent Teams workflow
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

workflow-team

Discover how to invoke autonomous parallel development workflows with /workflow-team lead or /workflow-team teammate. Learn more and get started today!

SKILL.md
Readonly

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 (file ownership prevents conflicts).

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

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?

Ideal for Team Lead Agents and teammates requiring autonomous parallel development workflows with automated task and dependency analysis. workflow-team is an autonomous parallel development workflow for Agent Teams, facilitating task management and dependency analysis.

How do I install workflow-team?

Run the command: npx killer-skills add onepunch-tk/cc-test-notion-invoice-web. 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: Automating task assignments for team members, Analyzing dependencies between project files, Generating parallel development workflows for Agent Teams.

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?

Requires access to CLAUDE.md, docs/PROJECT-STRUCTURE.md, and docs/ROADMAP.md files. Limited to Agent Teams workflow.

↓ 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/cc-test-notion-invoice-web. 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.

Related Skills

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

View All

widget-generator

Logo of f
f

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete privacy.

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

flags is a Next.js feature management skill that enables developers to efficiently add or modify framework feature flags, streamlining React application development.

★ 138.4k
⑂ 0
Browser

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

★ 72.8k
⑂ 0
AI

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

★ 72.8k
⑂ 0
AI