Agent Patterns
- 22 installs
- 82 repo stars
- Updated August 2, 2026
- aaaaqwq/claude-code-skills
agent-patterns is a Claude Code skill that provides structured SPAWN REQUEST and AGENT REPORT formats plus communication rules for coordinating multiple parallel agents.
About
agent-patterns is a Claude Code skill that defines structured message formats and communication protocols for coordinating multiple agents. A developer uses it to format SPAWN REQUEST messages, produce standardized AGENT REPORT status reports, and run a spawn-monitor-merge coordination workflow. It targets multi-agent sprint systems where agents must communicate traceably.
- Defines SPAWN REQUEST and AGENT REPORT message formats for coordinating parallel agents
- Specifies a 5-step coordination workflow: define tasks, spawn agents, monitor status, handle failures, merge results
- Establishes structured communication rules so agents message by ID rather than free-form text
Agent Patterns by the numbers
- 22 all-time installs (skills.sh)
- Ranked #10,123 of 16,556 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
agent-patterns capabilities & compatibility
free
- Capabilities
- agent orchestration · spawn formatting · status reporting · multi agent coordination
- Use cases
- orchestration
- Pricing
- Free
What agent-patterns says it does
Coordinate multi-agent workflows using structured communication protocols. Covers spawn requests, status reports, and inter-agent messaging within the sprint system.
Agents communicate through structured reports, not free-form text
npx skills add https://github.com/aaaaqwq/claude-code-skills --skill agent-patternsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 22 |
|---|---|
| repo stars | ★ 82 |
| Last updated | August 2, 2026 |
| Repository | aaaaqwq/claude-code-skills ↗ |
What it does
A developer uses it to coordinate parallel agents with standardized spawn requests, status reports, and messaging protocols.
Who is it for?
Standardizing how parallel agents are spawned, report status, and hand off results
Skip if: Single-agent tasks with no coordination
When should I use this skill?
The user needs to coordinate multiple agents, format spawn requests, produce agent reports, or establish inter-agent communication patterns
What you get
- spawn request messages
- agent status reports
- coordination workflow
By the numbers
- 5-step coordination workflow (define, spawn, monitor, handle failures, merge)
Files
Agent Patterns
Coordinate multi-agent workflows using structured communication protocols. Covers spawn requests, status reports, and inter-agent messaging within the sprint system.
Spawn Request Format
When launching a parallel agent, use this structure:
## SPAWN REQUEST
- **Agent ID**: <unique-id>
- **Role**: <role-name>
- **Task**: <one-line description>
- **Context**: <relevant files or state>
- **Expected Output**: <deliverable format>
- **Timeout**: <max duration>Agent Report Format
Each agent reports back using:
## AGENT REPORT
- **Agent ID**: <id>
- **Status**: completed | failed | blocked
- **Summary**: <one-line result>
- **Output**: <deliverable or file path>
- **Issues**: <blockers or warnings, if any>
- **Duration**: <time taken>Coordination Workflow
1. Define tasks — break work into independent units suitable for parallel execution 2. Spawn agents — send SPAWN REQUEST for each task with clear context 3. Monitor status — track agent reports as they complete 4. Handle failures — retry failed agents or reassign blocked tasks 5. Merge results — combine agent outputs into final deliverable, resolving conflicts
Communication Rules
- Agents communicate through structured reports, not free-form text
- Each message includes agent ID for traceability
- Blocked agents must report immediately rather than waiting silently
- The coordinator agent reviews all reports before merging
Error Handling
See references/errors.md for common failure modes and recovery steps.
Examples
See references/examples.md for complete spawn-and-report workflows.
Error Handling Reference
- Invalid input: Prompts for correction
- Missing dependencies: Lists required components
- Permission errors: Suggests remediation steps
Examples
Example usage patterns will be demonstrated in context.
Ui Test Report
UI TEST REPORT
MODE
AUTOMATED
SUMMARY
- Total tests run: 8
- Passed: 7
- Failed: 1
- Session duration: 45s
COVERAGE
- Scenarios covered:
- Login with valid credentials
- Login with invalid password
- Registration flow
- Password reset request
- Not covered (yet):
- Email verification flow (requires email testing setup)
FAILURES
- Scenario: Registration validation
- Path/URL: /register
- Symptom: Error message not displayed
- Expected: "Email already exists" message
- Actual: Form submits without feedback
CONSOLE ERRORS
None.
NOTES FOR ARCHITECT
- Registration error handling needs frontend fix
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10FAQ
What message formats does it define?
A SPAWN REQUEST format (agent ID, role, task, context, expected output, timeout) and an AGENT REPORT format (agent ID, status, summary, output, issues, duration).
What are its communication rules?
Agents communicate through structured reports not free-form text, each message includes an agent ID for traceability, and blocked agents must report immediately.