jeremylongshore/tons-of-skills-marketplace

agent-patterns

'Execute this skill should be used when the user asks about "SPAWN REQUEST format", "agent reports", "agent coordination", "parallel agents", "report format", "agent communication", or needs to understand how agents coordinate within the sprint system.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill agent-patterns

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Agent Patterns

Overview

Agent Patterns defines the coordination protocol for multi-agent sprint execution within the Sprint plugin. It governs how the project architect spawns implementation and testing agents, how agents communicate results via structured reports, and how parallel agents avoid conflicts.

Prerequisites

  • Sprint plugin installed and configured (/plugin install sprint)
  • Sprint directory initialized at .claude/sprint/[N]/
  • specs.md written with clear scope and testing configuration
  • Familiarity with the sprint phase lifecycle (see the sprint-workflow skill)

Instructions

  1. Structure every agent spawn using the SPAWN REQUEST format. Include the agent name, the specification file it should read, and any scope constraints:
   SPAWN REQUEST
   Agent: python-dev
   Specs: .claude/sprint/1/backend-specs.md
   Contract: .claude/sprint/1/api-contract.md
   Scope: Authentication endpoints only
  1. Ensure each spawned agent receives only the files relevant to its scope. Pass the api-contract.md as a shared interface so backend and frontend agents stay synchronized.
  2. Collect structured reports from every agent upon completion. Each report must include: work completed, files modified, tests added, and conformity status against the specification.
  3. When running agents in parallel, partition work by domain boundary (e.g., backend vs. frontend vs. CI/CD). Never assign overlapping file paths to concurrent agents.
  4. Feed agent reports back to the project architect for review. The architect decides whether to iterate (re-spawn with narrowed specs) or advance to the next phase.
  5. For testing agents, pass the UI test report format shown in ${CLAUDE_SKILL_DIR}/references/ui-test-report.md so results follow a consistent schema including test counts, coverage, failures, and console errors.

Output

  • SPAWN REQUEST blocks consumed by the sprint orchestrator to launch agents
  • Structured agent reports containing: summary, files changed, test results, and conformity status
  • UI test reports with pass/fail counts, coverage details, failure descriptions, and console error logs
  • Updated status.md reflecting completed and remaining work after each iteration

Error Handling

ErrorCauseSolution
Agent receives wrong specification fileIncorrect path in SPAWN REQUESTVerify the sprint directory number and file name before spawning
Overlapping file modifications from parallel agentsScope boundaries not clearly definedPartition work by domain; assign distinct directories to each agent
Agent report missing required fieldsAgent instructions lack report formatInclude the structured report template in the agent prompt
Infinite iteration loopSpecs never fully satisfiedCheck status.md for blocking issues; the orchestrator pauses after 5 iterations
Agent not foundMisspelled agent name in SPAWN REQUESTVerify agent markdown files exist in agents/ directory

Examples

Spawning parallel implementation agents:

SPAWN REQUEST
Agent: python-dev
Specs: .claude/sprint/1/backend-specs.md
Contract: .claude/sprint/1/api-contract.md

SPAWN REQUEST
Agent: nextjs-dev
Specs: .claude/sprint/1/frontend-specs.md
Contract: .claude/sprint/1/api-contract.md

Both agents share the same api-contract.md to ensure API compatibility.

Structured agent report format:

AGENT REPORT
Agent: python-dev
Status: COMPLETE
Files Modified: src/auth/routes.py, src/auth/models.py, tests/test_auth.py
Tests: 12 passed, 0 failed
Conformity: All backend-specs requirements implemented
Notes: JWT token expiry set to 24h per spec

Testing agent coordination:

SPAWN REQUEST
Agent: qa-test-agent
Specs: .claude/sprint/1/specs.md
Run After: python-dev, nextjs-dev

SPAWN REQUEST
Agent: ui-test-agent
Specs: .claude/sprint/1/specs.md
Run After: qa-test-agent

Resources

  • ${CLAUDE_SKILL_DIR}/references/ui-test-report.md -- Structured UI test report format with coverage and failure tracking
  • Sprint workflow skill for phase lifecycle context
  • API contract skill for shared interface design
  • Sprint plugin README for agent architecture overview
同じリポジトリから

関連する Skills

すべての Skills
jeremylongshore
コミュニティ

agent-context-loader

'Execute proactive auto-loading: automatically detects and loads agents.md files. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose. '

1時間の導入数
2
GitHub Stars
2907
更新日
11月8日
jeremylongshore
コミュニティ

agent-creator

'Create production-grade agent .md files aligned with the current Anthropic subagent contract. Also validates existing agents against the marketplace compliance rules. Use when building custom subagents, reviewing agent quality, or creating parallel agent architectures for orchestrator skills. Trigger with "/agent-creator", "create an agent", "build a subagent", or "validate my agent". Make sure to use this skill whenever creating agents/.md files for plugins or standalone use. '

1時間の導入数
2
GitHub Stars
2907
更新日
11月8日
jeremylongshore
コミュニティ

agent-safety-preflight

Generate a local repository risk receipt before Claude Code or other AI-agent edits. Use when the user asks to prepare a repository for agent changes, check for risky hooks or credential-writing automation, or run the /agent-preflight command. Trigger with "run agent preflight", "check this repo before agent edits", or "/agent-preflight".

1時間の導入数
2
GitHub Stars
2907
更新日
11月8日
jeremylongshore
コミュニティ

brand-strategy

Build or review a seven-part brand strategy covering identity, audience, positioning, messaging, visual principles, channels and measurement. Use when creating a brand brief, defining positioning or revising brand messaging. Trigger with "create brand strategy", "build brand brief" or "brand messaging".

1時間の導入数
2
GitHub Stars
2907
更新日
11月8日