From loophaus
Provides multi-agent orchestration patterns for Claude Code's Loop using Agent tool to spawn parallel subagents for codebase analysis, multi-service changes, and complex tasks.
npx claudepluginhub vcz-gray/loophausThis skill uses the workspace's default tool permissions.
Orchestration patterns optimized for Claude Code's Agent tool. Analyzes tasks and recommends the best combination of sequential loops and parallel subagents.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides agent creation for Claude Code plugins with file templates, frontmatter specs (name, description, model), triggering examples, system prompts, and best practices.
Orchestration patterns optimized for Claude Code's Agent tool. Analyzes tasks and recommends the best combination of sequential loops and parallel subagents.
Agent tool parameters:
- description: "short task description"
- prompt: "detailed instructions"
- subagent_type: "general-purpose" | "Explore" | "Plan" | "coder-fe" | "coder-be"
- isolation: "worktree" (gives agent an isolated repo copy)
- run_in_background: true (for parallel execution)
Best practices:
subagent_type: "Explore" for read-only scanning — faster and saferisolation: "worktree" when agents write to files — prevents merge conflictsrun_in_background: true for truly independent work streamsBest for: Large codebases where you need to understand before you change.
Phase 1 (Parallel Subagents via Agent tool):
├── Agent "fe-scan" (Explore, background): Scan src/frontend/** → .loophaus/reports/frontend.md
├── Agent "be-scan" (Explore, background): Scan src/backend/** → .loophaus/reports/backend.md
└── Agent "db-scan" (Explore, background): Scan src/db/** → .loophaus/reports/db.md
Phase 2 (Loop):
└── Read merged reports → implement fixes story by story via prd.json
Best for: Multi-service changes where files do not overlap.
Spawn agents with isolation: "worktree":
├── Agent "fe-dev" (worktree): ONLY touch src/frontend/** → commit per item
├── Agent "be-dev" (worktree): ONLY touch src/backend/** → commit per item
└── Agent "auth-dev" (worktree): ONLY touch src/auth/** → commit per item
After all complete: merge branches, run integration tests
Best for: Comprehensive analysis before any action.
Fan-Out (parallel Agent calls in single message):
├── Agent "security" (Explore): Audit for OWASP top 10 → findings.md
├── Agent "perf" (Explore): Profile and benchmark → findings.md
└── Agent "a11y" (Explore): Check accessibility → findings.md
Fan-In (Loop):
└── Synthesize all findings → create action plan → implement
Best for: Unfamiliar codebases or risky changes.
Scout (single Agent, Explore type):
└── Map codebase, trace dependencies, identify risks → scout-report.md
Execute (Loop):
└── Use scout report as reference, implement changes
Best for: Complex multi-stage transformations.
Stage 1 (Loop): Parse + validate → intermediate output
checkpoint: verify schema
Stage 2 (Loop): Transform → draft output
checkpoint: run regression tests
Stage 3 (Parallel Agents): Apply to multiple files
checkpoint: final integration test
| Factor | Score |
|---|---|
| Files span 3+ directories | +2 |
| Items are independent | +2 |
| Need full context to decide | -2 |
| Order matters | -2 |
| 10+ similar items | +1 |
| Needs cross-file understanding | -1 |
| Multiple services/repos | +3 |
.loophaus/
└── reports/
├── {agent-name}.md # Individual agent output
├── merged.md # Combined findings
└── plan.md # Action plan
When /loop-plan invokes this skill, provide: