Skip to content
Skills Library
AI & agents · Automation

agent-patterns

/agent-patterns

Format SPAWN REQUEST messages to launch parallel agents, generate structured agent status reports, and define communication protocols within the sprint system. Use when the user needs to coordinate multiple agents, format spawn requests, produce agent reports, or establish inter-agent communication patterns.

Licence
MIT
Last repository change
20.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 20.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Format SPAWN REQUEST messages to launch parallel agents, generate structured agent status reports, and define communication protocols within the sprint system. Use when the user needs to coordinate multiple agents, format spawn requests, produce agent reports, or establish inter-agent communication patterns.

Original author description

Format SPAWN REQUEST messages to launch parallel agents, generate structured agent status reports, and define communication protocols within the sprint system. Use when the user needs to coordinate multiple agents, format spawn requests, produce agent reports, or establish inter-agent communication patterns.

How it works

  1. Spawn Request Format
  2. Agent Report Format
  3. Coordination Workflow
  4. Communication Rules
  5. Error Handling
  6. Examples
Original SKILL.md headings · 56 lines, 232 words
SKILL.md preview
---
name: agent-patterns
description: "Format SPAWN REQUEST messages to launch parallel agents, generate structured agent status reports, and define communication protocols within the sprint system. Use when the user needs to coordinate multiple agents, format spawn requests, produce agent reports, or establish inter-agent communication patterns."
allowed-tools: Read
version: 1.0.0
author: Damien Laine <damien.laine@gmail.com>
license: MIT
---

# 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:

```markdown
## 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:

```markdown
## 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.
Files in this package (4)
  • SKILL.md 2 KB
  • references/errors.md 1 KB
  • references/examples.md 1 KB
  • references/ui-test-report.md 1 KB

Versions

RepositoryScoreLicence
This page · aAAaqwq/AGI-Super-Team100MIT
jeremylongshore/tons-of-skills-marketplace100MIT

Database snapshot: 13.11.2026 · package version 113f74c85159 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100agent-protocol
    Design AI agent communication protocols: MCP tool schemas, A2A, function calling, and inter- agent messaging. Use when building multi-agent systems, defining tool interfaces, or implementing agent-to-agent communication.
  • 100agent-spawn
    Use when launching parallel tmux agents with optional isolated Git worktrees under Oh My Harness.
  • 100agent-protocol
    Defines and validates standard communication protocols between agents (A2A). Use when: protocol, handshake, ipc, agent-messaging, a2a.
  • 90agent-communication
    Establish Agent-to-Agent (A2A) communication channels and topologies. Use when: setup swarm communication, implement a2a protocol, connect agents using mcp, design gossip protocol.
  • 95clawteam
    Multi-agent swarm coordination via the ClawTeam CLI. Use when the user wants to create agent teams, spawn multiple agents to work in parallel, coordinate tasks with dependencies, broadcast messages between agents, monitor progress via kanban board, or launch pre-built team…
  • 100a2a-protocols
    Implement Agent-to-Agent (A2A) communication for cross-framework interoperability. Use this skill when building multi-agent communication, implementing agent protocols, connecting agents across frameworks, or standardizing agent interfaces. Activate when: agent to agent, A2A,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.