Loading...
Loading...
Found 22 Skills
Claude Code Agent Teams - default team-based development with strict TDD pipeline enforcement
Orchestrate in-session Task tool teams for parallel work. Fan-out research, implementation, review, and documentation across subagents. Use when: parallel tasks, fan-out, subagent team, Task tool, in-session agents.
Interact with Microsoft Teams - send messages, read channels, manage reactions
Team composition knowledge for Claude Code Agent Teams - when to suggest teams, optimal sizing, spawn prompt patterns
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or the loop cap is reached. Use when: implementing features from a spec or plan, hardening existing code, fixing a batch of issues, or any multi-file task that benefits from a build-verify-fix cycle.
Coordinate Claude Code Agent Teams through filesystem-based protocol. Use when orchestrating multiple Claude agents on parallel tasks, need task dependency management, multi-agent code review or implementation. Do not use when single-agent work suffices, task is not parallelizable.
Agent Teams Orchestration Playbook for Claude Code. This skill should be used when the user requests to "create agent teams", "use agent swarm", "set up multi-agent collaboration", "orchestrate agents", "coordinate parallel agents", "organize team collaboration", "build agent teams", "implement swarm orchestration", "set up multi-agent system", "coordinate agent collaboration", or needs guidance on adaptive team formation, quality gates, skill discovery, task distribution, team coordination strategies, or Agent Teams best practices. It should also be used when the user mentions terms like "multi-agent", "agent collaboration", "agent orchestration", "parallel agents", "divisional collaboration", "assemble a team", "put together a team", "multi-agent collaboration", "swarm orchestration", "agent team". Note: "swarm" is a generic industry term; Claude Code's official concept is "Agent Teams".
Orchestrate teams of parallel Claude Code sessions working on the same codebase. Handles task decomposition, agent coordination, context isolation, and merge strategies. Builds on worktree-manager for infrastructure.
Configure and orchestrate Claude Code agent teams (TeamCreate, SendMessage, TaskUpdate workflow). Use when you need multiple agents working in parallel on a complex task, want to coordinate background agents with messaging, or are setting up a lead/teammate architecture with a shared task list. Teams are experimental — enable with --enable-teams flag.
Guide for orchestrating Claude Code agent teams — multiple parallel Claude Code sessions coordinated by a team lead. Use this skill when the user mentions agent teams, teammates, parallel agents, multi-agent workflows, spawning agents, coordinating agents, delegate mode, plan approval for teammates, TeammateIdle or TaskCompleted hooks, or wants to break a task into parallel independent work streams. Also trigger on questions about tmux split-pane mode, in-process teammate mode, Shift+Up/Down agent switching, shared task lists, inter-agent messaging, or designing tasks for multi-agent decomposition. This is an experimental feature requiring CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS to be enabled.
Provides a prompt template and best practices for building Claude Code agent teams. Covers team composition, teammate spawn prompts, task breakdown, file ownership, communication protocols, and delegate mode. Use when creating an agent team, spawning teammates, parallelizing work across multiple Claude Code instances, or deciding whether an agent team is the right approach.
Bootstrap the openspec/ directory structure for Spec-Driven Development in any project. Trigger: When user wants to initialize SDD in a project, or says "sdd init", "iniciar sdd", "openspec init".