Loading...
Loading...
Found 54 Skills
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Only to be triggered by explicit /parallel-task-spark commands.
Use this when the user requests you to execute multiple tasks in parallel, start multiple workers/agents simultaneously, launch multiple independent sessions using tmux, prevent PM from directly bypassing implementation protocols, or when you act as a PM to decompose and assign tasks to multiple independent workers. Trigger terms include "parallel execution", "start multiple", "simultaneous execution", "assign workers", "multi-agent parallelism", "start workers", "tmux launch", "independent session", "anti-escape", "task assignment", "do together". Do not use for single short tasks, cross-platform task status management, or Git branch/commit/PR/merge security rules.
Break down complex tasks into atomic, actionable goals with clear dependencies and success criteria. Use when planning multi-step projects, coordinating agents, or decomposing complex requests.
Use when working with performance testing review multi agent review
Dispatch and coordinate parallel agent execution. Manages concurrent task processing with result aggregation and error handling.
Use when user has complex multi-agent workflows, needs to coordinate sequential or parallel agent execution, wants workflow visualization and control, or mentions automating repetitive multi-agent processes - guides discovery and usage of the orchestration system
Use when working with error debugging multi agent review
Fully autonomous epic execution. Runs until ALL children are CLOSED. Local mode uses /swarm with runtime-native spawning (Codex sub-agents or Claude teams). Distributed mode uses /swarm --mode=distributed (tmux + Agent Mail) for persistence and coordination. NO human prompts, NO stopping.
Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.
Automated multi-agent orchestrator that spawns CLI subagents in parallel, coordinates via MCP Memory, and monitors progress