Menu
Knowledge for launching, managing, and monitoring cowork sessions that orchestrate multiple plugin agents in parallel
| name | cowork-sessions |
| description | Knowledge for launching, managing, and monitoring cowork sessions that orchestrate multiple plugin agents in parallel |
| allowed-tools | ["Read","Bash","Task","Glob","Grep"] |
| triggers | ["launch cowork session","start session","run cowork","parallel agents","session management","cowork orchestration"] |
Domain knowledge for launching and managing cowork sessions that coordinate multiple plugin agents.
1. INITIALIZING
- Validate item is installed
- Check plugin dependencies
- Parse task description
2. PLANNING
- Break task into subtasks
- Match subtasks to available agents
- Determine execution order and parallelism
3. RUNNING
- Dispatch agents with their subtasks
- Monitor progress (polling every 3-5 seconds)
- Collect intermediate outputs
4. COMPLETING
- Merge outputs from all agents
- Generate session summary
- Record metrics (tokens, cost, duration)
5. COMPLETED / FAILED
- Present final outputs
- Archive session for history
Sessions use the Agent tool to spawn sub-agents. Key patterns:
For dependent tasks (e.g., "generate code then write tests"):
Agent 1 completes → output feeds Agent 2 → Agent 2 completes
For independent tasks (e.g., "review security AND check performance"):
Agent 1 ─────────────→ output ─┐
Agent 2 ─────────────→ output ─┤─→ merge
Agent 3 ─────────────→ output ─┘
Common pattern for comprehensive analysis:
Coordinator decomposes task
├──→ Specialist Agent A
├──→ Specialist Agent B
└──→ Specialist Agent C
↓
Coordinator merges results
Each marketplace item defines defaults:
maxParallelAgents - How many agents run simultaneously (1-10)estimatedDuration - Expected session lengthavgSessionMinutes - Historical averagecompletionRate - Success rate (0.0-1.0)Sessions track:
If an agent fails during a session:
| Action | When to Use |
|---|---|
| Pause | Long-running session, need to step away |
| Resume | Continue a paused session from where it stopped |
| Cancel | Task is no longer needed, stop all agents |
Syncfusion Blazor component library with DataGrid, Charts, Scheduler, PDF, and 80+ components
Enhanced plan-authoring skill with Pre-Writing context gathering, task metadata, non-TDD templates, Red Flags, telemetry, and an automated plan linter. Use when you have a spec or requirements for a multi-step task, before touching code.
Select and coordinate multi-agent teams (topology kits, role-based squads, lifecycle, worktree isolation). Use this skill whenever launching parallel agents, designing a review board, running a debug council, scheduling an orchestrator-workers team, configuring agent tool restrictions, or deciding between solo and team execution. Triggers on: "launch a team", "parallel agents", "review board", "debug council", "architect-implementer-reviewer", "swarm", "multi-agent", "subagents for X", "team topology", "agent lifecycle".
Design, install, and debug Claude Code hooks across the full lifecycle (PreToolUse, PostToolUse, PostToolUseFailure, UserPromptSubmit, Notification, Stop, SessionStart, SessionEnd, PreCompact, SubagentStart, SubagentStop, TeammateIdle, PermissionRequest, Setup). Use this skill whenever a user asks to "install hooks", "add a pre-tool hook", "format on save", "block dangerous commands", "protect sensitive files", "restore context after compact", "enforce tests before stop", capture subagent telemetry, or runs /cc-hooks. Also triggers on "hooks not firing", "hook keeps blocking", or any configuration of .claude/settings.json hook sections.
Configure MCP servers for Claude Code — stdio vs HTTP, authentication, Tools/Resources/Prompts distinction, channels (CI webhook, mobile relay, Discord bridge, fakechat), and cost of always-loaded tools. Use this skill whenever adding an MCP server, debugging connection issues, choosing between MCP Tools vs Prompts vs Resources, installing channel servers, or managing .mcp.json. Triggers on: "MCP server", "mcp config", "add Obsidian MCP", "install context7", "channels", "webhook receiver", "mobile approval", "Discord bridge", "mcp not connecting".
Pick the right Claude model (Opus, Sonnet, Haiku) for a task and manage cost — decision matrix, cost tables, budget planning, cascading strategy. Use this skill whenever choosing a model, setting a token budget, optimizing session cost, or deciding whether to upgrade/downgrade mid-task. Triggers on: "which model", "cost", "budget", "haiku vs sonnet", "opus for this", "save tokens", "model cascading", "/cc-budget".