Claude Cursor Skill

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-

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download aaaaqwq-agi-super-team-skills_agent-patterns-cdb04e8.zip · 2 KB

aaaaqwq/agi-super-team 98 23 forks MIT Updated 8d ago

Part of aaaaqwq/agi-super-team — 46 skills

Install

skills CLI npx skills add https://github.com/aAAaqwq/AGI-Super-Team/tree/main/skills/agent-patterns

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install aaaaqwq-agi-super-team@llmmart

Git git clone https://github.com/aAAaqwq/AGI-Super-Team.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole aaaaqwq/agi-super-team collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

Define tasks — break work into independent units suitable for parallel execution
Spawn agents — send SPAWN REQUEST for each task with clear context
Monitor status — track agent reports as they complete
Handle failures — retry failed agents or reassign blocked tasks
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 (agi-super-team)

references

errors.md 165 B

# Error Handling Reference

- Invalid input: Prompts for correction
- Missing dependencies: Lists required components
- Permission errors: Suggests remediation steps

examples.md 67 B

# Examples

Example usage patterns will be demonstrated in context.

ui-test-report.md 672 B

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

SKILL.md 2.1 KB

---
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.