agent-patterns

$npx mdskill add aAAaqwq/AGI-Super-Team/agent-patterns

Coordinate parallel agents with structured spawn requests and reports.

  • Enables launching multiple agents simultaneously with clear task definitions.
  • Depends on the sprint system for inter-agent communication protocols.
  • Decides execution by parsing task requirements into standardized request formats.
  • Delivers status updates via structured reports tracking progress and blockers.

SKILL.md

.github/skills/agent-patternsView on GitHub ↗
---
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 <[email protected]>
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.

More from aAAaqwq/AGI-Super-Team

SkillDescription
a-fund-monitor监控 A 股基金实时估值与盘后净值,自动判断交易日并生成提醒或分析。
add-leadAdd company/person/relationship to CRM
ads-agentAI-агент для управления Facebook рекламой. Вызывай для анализа, оптимизации, создания кампаний и отчётов.
afrexai-compliance-auditRun internal compliance audits against major governance and security
afrexai-personal-financeComplete personal finance system — budgeting, debt payoff, investing, tax optimization, net worth tracking, and financial independence planning. Use when managing money, building wealth, paying off debt, planning retirement, or optimizing taxes. Zero dependencies.
after-salesUse when managing post-purchase experience, building customer loyalty, or increasing repeat purchases
agent-contactsAI agent contacts — add, list, remove MCP contacts. Use when someone gives an agent URL, or when you need to view/remove contacts.
agent-model-switcher批量查看和切换子 agent 的模型配置,用于统一调整多 agent 的 provider/model 设置。
agent-task-confirmUse when confirming whether a dispatched agent task was actually received, activated, and progressing after sessions_send or other task handoff actions.
agent-team-orchestrationOrchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.