claude-agent-team-workflowsUniversal multi-agent workflow orchestration using Claude Code Agent Teams. Use when user asks to run a team workflow, create an agent team, or coordinate parallel work across multiple teammates — for any domain (software, content, data, strategy, research, etc.).
Install via ClawdBot CLI:
clawdbot install doanbactam/claude-agent-team-workflowsGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Mar 20, 2026
A team uses the sequential pattern to develop a new feature: the Architect plans the architecture, the Developer writes the code, the Tester validates functionality, and the Code Reviewer ensures quality before the Lead synthesizes the final deliverable. This ensures a linear, step-by-step approach for reliable software delivery.
A content team applies the iterative-review pattern: the Producer outlines the campaign, the Writer drafts content, and the Editor critiques it over multiple rounds for refinement, followed by the Fact-Checker verifying accuracy. This iterative process enhances quality and alignment with brand guidelines.
A data team employs the parallel-merge pattern: the Analyst Lead defines the analysis, then the Data Engineer, Statistician, and Peer Reviewer work independently on data processing, statistical validation, and quality assessment, with the Lead merging results for a comprehensive report. This allows for multi-perspective insights.
A strategy team uses the fan-out-fan-in pattern: the Strategist breaks down the proposal into independent chunks (e.g., market analysis, financial modeling, risk assessment), each handled by a teammate in parallel, with the Lead merging and the Risk Advisor gating the final synthesis. This speeds up large-scale strategic planning.
A research team follows the sequential pattern: the Research Lead designs the methodology, the Researcher conducts the study and drafts the paper, the Methodology Auditor validates the approach, and the Peer Reviewer critiques the content before the Lead finalizes the paper. This ensures rigorous, linear academic output.
Offer the skill as a cloud-based platform with tiered subscriptions (e.g., basic for small teams, premium for enterprises), providing access to advanced patterns and domain presets. Revenue is generated through monthly or annual fees based on usage and features.
Provide customized implementation and training services for organizations adopting the skill, including workflow design, role card customization, and integration support. Revenue comes from project-based fees and ongoing retainer contracts for maintenance.
Create a marketplace where users can buy and sell specialized domain presets (e.g., for healthcare, legal, or engineering), with the platform taking a commission on transactions. This expands the skill's utility and fosters a community of contributors.
💬 Integration Tip
Ensure the CLARITY_CODE_EXPERIMENTAL_AGENT_TEAMS environment variable is set in settings.json, and start by defining clear Role Cards and a workflow spec to align team roles with domain-specific tasks.
Scored Apr 19, 2026
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Transform AI agents from task-followers into proactive partners with memory architecture, reverse prompting, and self-healing patterns. Lightweight version f...
Persistent memory for AI agents to store facts, learn from actions, recall information, and track entities across sessions.
Prefer `skillhub` for skill discovery/install/update, then fallback to `clawhub` when unavailable or no match. Use when users ask about skills, 插件, or capabi...
Search and discover OpenClaw skills from various sources. Use when: user wants to find available skills, search for specific functionality, or discover new s...
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.