mumucc 0.4.4 → 0.4.10

package/defaults/plugin-seed/marketplaces/claude-code-workflows/plugins/agent-teams/skills/task-coordination-strategies/references/dependency-graphs.md

@@ -0,0 +1,97 @@
+# Dependency Graph Patterns
+
+Visual patterns for task dependency design with trade-offs.
+
+## Pattern 1: Fully Independent (Maximum Parallelism)
+
+```
+Task A ─┐
+Task B ─┼─→ Final Integration
+Task C ─┘
+```
+
+- **Parallelism**: Maximum — all tasks run simultaneously
+- **Risk**: Integration may reveal incompatibilities late
+- **Use when**: Tasks operate on completely separate files/modules
+- **TaskCreate**: No blockedBy relationships; integration task blocked by all
+
+## Pattern 2: Sequential Chain (No Parallelism)
+
+```
+Task A → Task B → Task C → Task D
+```
+
+- **Parallelism**: None — each task waits for the previous
+- **Risk**: Bottleneck at each step; one delay cascades
+- **Use when**: Each task depends on the output of the previous (avoid if possible)
+- **TaskCreate**: Each task blockedBy the previous
+
+## Pattern 3: Diamond (Shared Foundation)
+
+```
+           ┌→ Task B ─┐
+Task A ──→ ┤          ├→ Task D
+           └→ Task C ─┘
+```
+
+- **Parallelism**: B and C run in parallel after A completes
+- **Risk**: A is a bottleneck; D must wait for both B and C
+- **Use when**: B and C both need output from A (e.g., shared types)
+- **TaskCreate**: B and C blockedBy A; D blockedBy B and C
+
+## Pattern 4: Fork-Join (Phased Parallelism)
+
+```
+Phase 1:  A1, A2, A3  (parallel)
+          ────────────
+Phase 2:  B1, B2      (parallel, after phase 1)
+          ────────────
+Phase 3:  C1          (after phase 2)
+```
+
+- **Parallelism**: Within each phase, tasks are parallel
+- **Risk**: Phase boundaries add synchronization delays
+- **Use when**: Natural phases with dependencies (build → test → deploy)
+- **TaskCreate**: Phase 2 tasks blockedBy all Phase 1 tasks
+
+## Pattern 5: Pipeline (Streaming)
+
+```
+Task A ──→ Task B ──→ Task C
+  └──→ Task D ──→ Task E
+```
+
+- **Parallelism**: Two parallel chains
+- **Risk**: Chains may diverge in approach
+- **Use when**: Two independent feature branches from a common starting point
+- **TaskCreate**: B blockedBy A; D blockedBy A; C blockedBy B; E blockedBy D
+
+## Anti-Patterns
+
+### Circular Dependency (Deadlock)
+
+```
+Task A → Task B → Task C → Task A  ✗ DEADLOCK
+```
+
+**Fix**: Extract shared dependency into a separate task that all three depend on.
+
+### Unnecessary Dependencies
+
+```
+Task A → Task B → Task C
+(where B doesn't actually need A's output)
+```
+
+**Fix**: Remove the blockedBy relationship; let B run independently.
+
+### Star Pattern (Single Bottleneck)
+
+```
+     ┌→ B
+A →  ├→ C  → F
+     ├→ D
+     └→ E
+```
+
+**Fix**: If A is slow, all downstream tasks are delayed. Try to parallelize A's work.

package/defaults/plugin-seed/marketplaces/claude-code-workflows/plugins/agent-teams/skills/task-coordination-strategies/references/task-decomposition.md

@@ -0,0 +1,98 @@
+# Task Decomposition Examples
+
+Practical examples of decomposing features into parallelizable tasks with clear ownership.
+
+## Example 1: User Authentication Feature
+
+### Feature Description
+
+Add email/password authentication with login, registration, and profile pages.
+
+### Decomposition (Vertical Slices)
+
+**Stream 1: Login Flow** (implementer-1)
+
+- Owned files: `src/pages/login.tsx`, `src/api/login.ts`, `tests/login.test.ts`
+- Requirements: Login form, API endpoint, input validation, error handling
+- Interface: Imports `AuthResponse` from `src/types/auth.ts`
+
+**Stream 2: Registration Flow** (implementer-2)
+
+- Owned files: `src/pages/register.tsx`, `src/api/register.ts`, `tests/register.test.ts`
+- Requirements: Registration form, API endpoint, email validation, password strength
+- Interface: Imports `AuthResponse` from `src/types/auth.ts`
+
+**Stream 3: Shared Infrastructure** (implementer-3)
+
+- Owned files: `src/types/auth.ts`, `src/middleware/auth.ts`, `src/utils/jwt.ts`
+- Requirements: Type definitions, JWT middleware, token utilities
+- Dependencies: None (other streams depend on this)
+
+### Dependency Graph
+
+```
+Stream 3 (types/middleware) ──→ Stream 1 (login)
+                             └→ Stream 2 (registration)
+```
+
+## Example 2: REST API Endpoints
+
+### Feature Description
+
+Add CRUD endpoints for a new "Projects" resource.
+
+### Decomposition (By Layer)
+
+**Stream 1: Data Layer** (implementer-1)
+
+- Owned files: `src/models/project.ts`, `src/migrations/add-projects.ts`, `src/repositories/project-repo.ts`
+- Requirements: Schema definition, migration, repository pattern
+- Dependencies: None
+
+**Stream 2: Business Logic** (implementer-2)
+
+- Owned files: `src/services/project-service.ts`, `src/validators/project-validator.ts`
+- Requirements: CRUD operations, validation rules, business logic
+- Dependencies: Blocked by Stream 1 (needs model/repository)
+
+**Stream 3: API Layer** (implementer-3)
+
+- Owned files: `src/routes/projects.ts`, `src/controllers/project-controller.ts`
+- Requirements: REST endpoints, request parsing, response formatting
+- Dependencies: Blocked by Stream 2 (needs service layer)
+
+## Task Template
+
+```markdown
+## Task: {Stream Name}
+
+### Objective
+
+{1-2 sentence description of what to build}
+
+### Owned Files
+
+- {file1} — {purpose}
+- {file2} — {purpose}
+
+### Requirements
+
+1. {Specific deliverable 1}
+2. {Specific deliverable 2}
+3. {Specific deliverable 3}
+
+### Interface Contract
+
+- Exports: {types/functions this stream provides}
+- Imports: {types/functions this stream consumes from other streams}
+
+### Acceptance Criteria
+
+- [ ] {Verifiable criterion 1}
+- [ ] {Verifiable criterion 2}
+- [ ] {Verifiable criterion 3}
+
+### Out of Scope
+
+- {Explicitly excluded work}
+```

package/defaults/plugin-seed/marketplaces/claude-code-workflows/plugins/agent-teams/skills/team-communication-protocols/SKILL.md

@@ -0,0 +1,177 @@
+---
+name: team-communication-protocols
+description: Structured messaging protocols for agent team communication including message type selection, plan approval, shutdown procedures, and anti-patterns to avoid. Use this skill when establishing communication norms for a newly spawned team, when deciding whether to send a direct message or a broadcast, when a team-lead needs to review and approve an implementer's plan before work begins, when orchestrating a graceful team shutdown after all tasks are complete, or when debugging why teammates are not coordinating correctly at integration points.
+version: 1.0.2
+---
+
+# Team Communication Protocols
+
+Protocols for effective communication between agent teammates, including message type selection, plan approval workflows, shutdown procedures, and common anti-patterns to avoid.
+
+## When to Use This Skill
+
+- Establishing communication norms for a new team
+- Choosing between message types (message, broadcast, shutdown_request)
+- Handling plan approval workflows
+- Managing graceful team shutdown
+- Discovering teammate identities and capabilities
+
+## Message Type Selection
+
+### `message` (Direct Message) — Default Choice
+
+Send to a single specific teammate:
+
+```json
+{
+  "type": "message",
+  "recipient": "implementer-1",
+  "content": "Your API endpoint is ready. You can now build the frontend form.",
+  "summary": "API endpoint ready for frontend"
+}
+```
+
+**Use for**: Task updates, coordination, questions, integration notifications.
+
+### `broadcast` — Use Sparingly
+
+Send to ALL teammates simultaneously:
+
+```json
+{
+  "type": "broadcast",
+  "content": "Critical: shared types file has been updated. Pull latest before continuing.",
+  "summary": "Shared types updated"
+}
+```
+
+**Use ONLY for**: Critical blockers affecting everyone, major changes to shared resources.
+
+**Why sparingly?**: Each broadcast sends N separate messages (one per teammate), consuming API resources proportional to team size.
+
+### `shutdown_request` — Graceful Termination
+
+Request a teammate to shut down:
+
+```json
+{
+  "type": "shutdown_request",
+  "recipient": "reviewer-1",
+  "content": "Review complete, shutting down team."
+}
+```
+
+The teammate responds with `shutdown_response` (approve or reject with reason).
+
+## Communication Anti-Patterns
+
+| Anti-Pattern                            | Problem                                  | Better Approach                        |
+| --------------------------------------- | ---------------------------------------- | -------------------------------------- |
+| Broadcasting routine updates            | Wastes resources, noise                  | Direct message to affected teammate    |
+| Sending JSON status messages            | Not designed for structured data         | Use TaskUpdate to update task status   |
+| Not communicating at integration points | Teammates build against stale interfaces | Message when your interface is ready   |
+| Micromanaging via messages              | Overwhelms teammates, slows work         | Check in at milestones, not every step |
+| Using UUIDs instead of names            | Hard to read, error-prone                | Always use teammate names              |
+| Ignoring idle teammates                 | Wasted capacity                          | Assign new work or shut down           |
+
+## Plan Approval Workflow
+
+When a teammate is spawned with `plan_mode_required`:
+
+1. Teammate creates a plan using read-only exploration tools
+2. Teammate calls `ExitPlanMode` which sends a `plan_approval_request` to the lead
+3. Lead reviews the plan
+4. Lead responds with `plan_approval_response`:
+
+**Approve**:
+
+```json
+{
+  "type": "plan_approval_response",
+  "request_id": "abc-123",
+  "recipient": "implementer-1",
+  "approve": true
+}
+```
+
+**Reject with feedback**:
+
+```json
+{
+  "type": "plan_approval_response",
+  "request_id": "abc-123",
+  "recipient": "implementer-1",
+  "approve": false,
+  "content": "Please add error handling for the API calls"
+}
+```
+
+## Shutdown Protocol
+
+### Graceful Shutdown Sequence
+
+1. **Lead sends shutdown_request** to each teammate
+2. **Teammate receives request** as a JSON message with `type: "shutdown_request"`
+3. **Teammate responds** with `shutdown_response`:
+   - `approve: true` — Teammate saves state and exits
+   - `approve: false` + reason — Teammate continues working
+4. **Lead handles rejections** — Wait for teammate to finish, then retry
+5. **After all teammates shut down** — Call `TeamDelete` to remove team resources
+
+### Handling Rejections
+
+If a teammate rejects shutdown:
+
+- Check their reason (usually "still working on task")
+- Wait for their current task to complete
+- Retry shutdown request
+- If urgent, user can force shutdown
+
+## Teammate Discovery
+
+Find team members by reading the config file:
+
+**Location**: `~/.claude/teams/{team-name}/config.json`
+
+**Structure**:
+
+```json
+{
+  "members": [
+    {
+      "name": "security-reviewer",
+      "agentId": "uuid-here",
+      "agentType": "team-reviewer"
+    },
+    {
+      "name": "perf-reviewer",
+      "agentId": "uuid-here",
+      "agentType": "team-reviewer"
+    }
+  ]
+}
+```
+
+**Always use `name`** for messaging and task assignment. Never use `agentId` directly.
+
+## Troubleshooting
+
+**A teammate is not responding to messages.**
+Check the teammate's task status. If it is idle, it may have completed its task and is waiting to be assigned new work or shut down. If it is still active, it may be mid-execution and will process messages once the current operation finishes.
+
+**The lead is sending broadcasts for every status update.**
+This is a common anti-pattern. Broadcasts are expensive — each one sends N messages. Use direct messages (`type: "message"`) for point-to-point updates. Reserve broadcasts for critical shared-resource changes like an updated interface contract.
+
+**A teammate rejected a shutdown request unexpectedly.**
+The teammate is still working. Check the rejection reason in the `shutdown_response` content field, wait for the work to finish, then retry. Never force-terminate a teammate that has unsaved work.
+
+**A plan_approval_request arrived but the request_id is missing.**
+The teammate called `ExitPlanMode` without the required request context. Have the teammate re-enter plan mode, complete exploration, and call `ExitPlanMode` again. The `request_id` is generated automatically by the plan mode system.
+
+**Two teammates are waiting on each other and neither is making progress.**
+This is a deadlock: both are blocked waiting for the other to finish first. The lead should send a direct message to one teammate with a stub or partial result so it can unblock and proceed.
+
+## Related Skills
+
+- [team-composition-patterns](../team-composition-patterns/SKILL.md) — Select agent types and team size before establishing communication norms
+- [parallel-feature-development](../parallel-feature-development/SKILL.md) — Use communication protocols to coordinate integration handoffs between parallel implementers

package/defaults/plugin-seed/marketplaces/claude-code-workflows/plugins/agent-teams/skills/team-communication-protocols/references/messaging-patterns.md

@@ -0,0 +1,112 @@
+# Messaging Pattern Templates
+
+Ready-to-use message templates for common team communication scenarios.
+
+## Task Assignment
+
+```
+You've been assigned task #{id}: {subject}.
+
+Owned files:
+- {file1}
+- {file2}
+
+Key requirements:
+- {requirement1}
+- {requirement2}
+
+Interface contract:
+- Import {types} from {shared-file}
+- Export {types} for {other-teammate}
+
+Let me know if you have questions or blockers.
+```
+
+## Integration Point Notification
+
+```
+My side of the {interface-name} interface is complete.
+
+Exported from {file}:
+- {function/type 1}
+- {function/type 2}
+
+You can now import these in your owned files. The contract matches what we agreed on.
+```
+
+## Blocker Report
+
+```
+I'm blocked on task #{id}: {subject}.
+
+Blocker: {description of what's preventing progress}
+Impact: {what can't be completed until this is resolved}
+
+Options:
+1. {option 1}
+2. {option 2}
+
+Waiting for your guidance.
+```
+
+## Task Completion Report
+
+```
+Task #{id} complete: {subject}
+
+Changes made:
+- {file1}: {what changed}
+- {file2}: {what changed}
+
+Integration notes:
+- {any interface changes or considerations for other teammates}
+
+Ready for next assignment.
+```
+
+## Review Finding Summary
+
+```
+Review complete for {target} ({dimension} dimension).
+
+Summary:
+- Critical: {count}
+- High: {count}
+- Medium: {count}
+- Low: {count}
+
+Top finding: {brief description of most important finding}
+
+Full findings attached to task #{id}.
+```
+
+## Investigation Report Summary
+
+```
+Investigation complete for hypothesis: {hypothesis summary}
+
+Verdict: {Confirmed | Falsified | Inconclusive}
+Confidence: {High | Medium | Low}
+
+Key evidence:
+- {file:line}: {what was found}
+- {file:line}: {what was found}
+
+{If confirmed}: Recommended fix: {brief fix description}
+{If falsified}: Contradicting evidence: {brief description}
+
+Full report attached to task #{id}.
+```
+
+## Shutdown Acknowledgment
+
+When you receive a shutdown request, respond with the shutdown_response tool. But you may also want to send a final status message:
+
+```
+Wrapping up. Current status:
+- Task #{id}: {completed/in-progress}
+- Files modified: {list}
+- Pending work: {none or description}
+
+Ready for shutdown.
+```

package/defaults/plugin-seed/marketplaces/claude-code-workflows/plugins/agent-teams/skills/team-composition-patterns/SKILL.md

@@ -0,0 +1,141 @@
+---
+name: team-composition-patterns
+description: Design optimal agent team compositions with sizing heuristics, preset configurations, and agent type selection. Use this skill when deciding how many agents to spawn for a task, when choosing between a review team versus a feature team versus a debug team, when selecting the correct subagent_type for each role to ensure agents have the tools they need, when configuring display modes (tmux, iTerm2, in-process) for a CI or local environment, or when building a custom team composition for a non-standard workflow such as a migration or security audit.
+version: 1.0.2
+---
+
+# Team Composition Patterns
+
+Best practices for composing multi-agent teams, selecting team sizes, choosing agent types, and configuring display modes for Claude Code's Agent Teams feature.
+
+## When to Use This Skill
+
+- Deciding how many teammates to spawn for a task
+- Choosing between preset team configurations
+- Selecting the right agent type (subagent_type) for each role
+- Configuring teammate display modes (tmux, iTerm2, in-process)
+- Building custom team compositions for non-standard workflows
+
+## Team Sizing Heuristics
+
+| Complexity   | Team Size | When to Use                                                 |
+| ------------ | --------- | ----------------------------------------------------------- |
+| Simple       | 1-2       | Single-dimension review, isolated bug, small feature        |
+| Moderate     | 2-3       | Multi-file changes, 2-3 concerns, medium features           |
+| Complex      | 3-4       | Cross-cutting concerns, large features, deep debugging      |
+| Very Complex | 4-5       | Full-stack features, comprehensive reviews, systemic issues |
+
+**Rule of thumb**: Start with the smallest team that covers all required dimensions. Adding teammates increases coordination overhead.
+
+## Preset Team Compositions
+
+### Review Team
+
+- **Size**: 3 reviewers
+- **Agents**: 3x `team-reviewer`
+- **Default dimensions**: security, performance, architecture
+- **Use when**: Code changes need multi-dimensional quality assessment
+
+### Debug Team
+
+- **Size**: 3 investigators
+- **Agents**: 3x `team-debugger`
+- **Default hypotheses**: 3 competing hypotheses
+- **Use when**: Bug has multiple plausible root causes
+
+### Feature Team
+
+- **Size**: 3 (1 lead + 2 implementers)
+- **Agents**: 1x `team-lead` + 2x `team-implementer`
+- **Use when**: Feature can be decomposed into parallel work streams
+
+### Fullstack Team
+
+- **Size**: 4 (1 lead + 3 implementers)
+- **Agents**: 1x `team-lead` + 1x frontend `team-implementer` + 1x backend `team-implementer` + 1x test `team-implementer`
+- **Use when**: Feature spans frontend, backend, and test layers
+
+### Research Team
+
+- **Size**: 3 researchers
+- **Agents**: 3x `general-purpose`
+- **Default areas**: Each assigned a different research question, module, or topic
+- **Capabilities**: Codebase search (Grep, Glob, Read), web search (WebSearch, WebFetch)
+- **Use when**: Need to understand a codebase, research libraries, compare approaches, or gather information from code and web sources in parallel
+
+### Security Team
+
+- **Size**: 4 reviewers
+- **Agents**: 4x `team-reviewer`
+- **Default dimensions**: OWASP/vulnerabilities, auth/access control, dependencies/supply chain, secrets/configuration
+- **Use when**: Comprehensive security audit covering multiple attack surfaces
+
+### Migration Team
+
+- **Size**: 4 (1 lead + 2 implementers + 1 reviewer)
+- **Agents**: 1x `team-lead` + 2x `team-implementer` + 1x `team-reviewer`
+- **Use when**: Large codebase migration (framework upgrade, language port, API version bump) requiring parallel work with correctness verification
+
+## Agent Type Selection
+
+When spawning teammates with the `Agent` tool, choose `subagent_type` based on what tools the teammate needs:
+
+| Agent Type                     | Tools Available                           | Use For                                                    |
+| ------------------------------ | ----------------------------------------- | ---------------------------------------------------------- |
+| `general-purpose`              | All tools (Read, Write, Edit, Bash, etc.) | Implementation, debugging, any task requiring file changes |
+| `Explore`                      | Read-only tools (Read, Grep, Glob)        | Research, code exploration, analysis                       |
+| `Plan`                         | Read-only tools                           | Architecture planning, task decomposition                  |
+| `agent-teams:team-reviewer`    | All tools                                 | Code review with structured findings                       |
+| `agent-teams:team-debugger`    | All tools                                 | Hypothesis-driven investigation                            |
+| `agent-teams:team-implementer` | All tools                                 | Building features within file ownership boundaries         |
+| `agent-teams:team-lead`        | All tools                                 | Team orchestration and coordination                        |
+
+**Key distinction**: Read-only agents (Explore, Plan) cannot modify files. Never assign implementation tasks to read-only agents.
+
+## Display Mode Configuration
+
+Configure in `~/.claude/settings.json`:
+
+```json
+{
+  "teammateMode": "tmux"
+}
+```
+
+| Mode           | Behavior                       | Best For                                          |
+| -------------- | ------------------------------ | ------------------------------------------------- |
+| `"tmux"`       | Each teammate in a tmux pane   | Development workflows, monitoring multiple agents |
+| `"iterm2"`     | Each teammate in an iTerm2 tab | macOS users who prefer iTerm2                     |
+| `"in-process"` | All teammates in same process  | Simple tasks, CI/CD environments                  |
+
+## Custom Team Guidelines
+
+When building custom teams:
+
+1. **Every team needs a coordinator** — Either designate a `team-lead` or have the user coordinate directly
+2. **Match roles to agent types** — Use specialized agents (reviewer, debugger, implementer) when available
+3. **Avoid duplicate roles** — Two agents doing the same thing wastes resources
+4. **Define boundaries upfront** — Each teammate needs clear ownership of files or responsibilities
+5. **Keep it small** — 2-4 teammates is the sweet spot; 5+ requires significant coordination overhead
+
+## Troubleshooting
+
+**A teammate was spawned as `Explore` but needs to write files.**
+`Explore` and `Plan` are read-only agents. Change the `subagent_type` to `general-purpose` or an appropriate specialized agent type. Never assign implementation tasks to read-only agents.
+
+**The team is growing too large and coordination is slowing everything down.**
+Each additional teammate adds communication overhead. Consolidate roles: can one agent cover two dimensions? A 4-person team doing 6 independent tasks is usually better served by 3 agents covering 2 tasks each.
+
+**tmux mode is not showing panes.**
+Ensure tmux is installed and a session is already running before spawning teammates. The `in-process` mode works without tmux and is suitable for CI or scripted environments.
+
+**Two reviewers are flagging the same issues.**
+The review dimensions overlap. Redefine each reviewer's focus area: one on correctness/logic, one on security, one on performance/scalability. Overlapping coverage wastes tokens and produces duplicate findings.
+
+**A `team-lead` is spawning teammates but they are not receiving tasks.**
+Verify that the lead is using the `Agent` tool to spawn teammates and passing complete context in the prompt. Teammates start fresh with no prior conversation history — they need all relevant information in their initial prompt.
+
+## Related Skills
+
+- [parallel-feature-development](../parallel-feature-development/SKILL.md) — Decompose work streams and assign file ownership once the team is composed
+- [team-communication-protocols](../team-communication-protocols/SKILL.md) — Establish messaging norms and shutdown procedures for the assembled team