[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H4RGTRKBF7F5JBMZJ5A3AV":3,"skill-same:01M6H4RGTRKBF7F5JBMZJ5A3AV":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6H4RGTRKBF7F5JBMZJ5A3AV","agent-patterns",null,"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. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fcommunity\u002Fsprint\u002Fskills\u002Fagent-patterns\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"agent patterns","patterns","reports","with","about","agent coordination","relevant","sprint","trigger","coordinate","codex","agent communication","use","spawn","parallel","coordination","system","how","communication","code","2026-11-10 10:12:30",false,"---\nname: agent-patterns\ndescription: |\n  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. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.\nallowed-tools: Read\nversion: 1.0.0\nauthor: Damien Laine \u003Cdamien.laine@gmail.com>\nlicense: MIT\ncompatible-with: claude-code, codex, openclaw\n---\n# Agent Patterns\n\n## Overview\n\nAgent 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.\n\n## Prerequisites\n\n- Sprint plugin installed and configured (`\u002Fplugin install sprint`)\n- Sprint directory initialized at `.claude\u002Fsprint\u002F[N]\u002F`\n- `specs.md` written with clear scope and testing configuration\n- Familiarity with the sprint phase lifecycle (see the `sprint-workflow` skill)\n\n## Instructions\n\n1. Structure every agent spawn using the SPAWN REQUEST format. Include the agent name, the specification file it should read, and any scope constraints:\n   ```\n   SPAWN REQUEST\n   Agent: python-dev\n   Specs: .claude\u002Fsprint\u002F1\u002Fbackend-specs.md\n   Contract: .claude\u002Fsprint\u002F1\u002Fapi-contract.md\n   Scope: Authentication endpoints only\n   ```\n2. 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.\n3. Collect structured reports from every agent upon completion. Each report must include: work completed, files modified, tests added, and conformity status against the specification.\n4. When running agents in parallel, partition work by domain boundary (e.g., backend vs. frontend vs. CI\u002FCD). Never assign overlapping file paths to concurrent agents.\n5. 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.\n6. For testing agents, pass the UI test report format shown in `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fui-test-report.md` so results follow a consistent schema including test counts, coverage, failures, and console errors.\n\n## Output\n\n- SPAWN REQUEST blocks consumed by the sprint orchestrator to launch agents\n- Structured agent reports containing: summary, files changed, test results, and conformity status\n- UI test reports with pass\u002Ffail counts, coverage details, failure descriptions, and console error logs\n- Updated `status.md` reflecting completed and remaining work after each iteration\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Agent receives wrong specification file | Incorrect path in SPAWN REQUEST | Verify the sprint directory number and file name before spawning |\n| Overlapping file modifications from parallel agents | Scope boundaries not clearly defined | Partition work by domain; assign distinct directories to each agent |\n| Agent report missing required fields | Agent instructions lack report format | Include the structured report template in the agent prompt |\n| Infinite iteration loop | Specs never fully satisfied | Check `status.md` for blocking issues; the orchestrator pauses after 5 iterations |\n| Agent not found | Misspelled agent name in SPAWN REQUEST | Verify agent markdown files exist in `agents\u002F` directory |\n\n## Examples\n\n**Spawning parallel implementation agents:**\n```\nSPAWN REQUEST\nAgent: python-dev\nSpecs: .claude\u002Fsprint\u002F1\u002Fbackend-specs.md\nContract: .claude\u002Fsprint\u002F1\u002Fapi-contract.md\n\nSPAWN REQUEST\nAgent: nextjs-dev\nSpecs: .claude\u002Fsprint\u002F1\u002Ffrontend-specs.md\nContract: .claude\u002Fsprint\u002F1\u002Fapi-contract.md\n```\nBoth agents share the same `api-contract.md` to ensure API compatibility.\n\n**Structured agent report format:**\n```\nAGENT REPORT\nAgent: python-dev\nStatus: COMPLETE\nFiles Modified: src\u002Fauth\u002Froutes.py, src\u002Fauth\u002Fmodels.py, tests\u002Ftest_auth.py\nTests: 12 passed, 0 failed\nConformity: All backend-specs requirements implemented\nNotes: JWT token expiry set to 24h per spec\n```\n\n**Testing agent coordination:**\n```\nSPAWN REQUEST\nAgent: qa-test-agent\nSpecs: .claude\u002Fsprint\u002F1\u002Fspecs.md\nRun After: python-dev, nextjs-dev\n\nSPAWN REQUEST\nAgent: ui-test-agent\nSpecs: .claude\u002Fsprint\u002F1\u002Fspecs.md\nRun After: qa-test-agent\n```\n\n## Resources\n\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fui-test-report.md` -- Structured UI test report format with coverage and failure tracking\n- Sprint workflow skill for phase lifecycle context\n- API contract skill for shared interface design\n- Sprint plugin README for agent architecture overview","# Agent Patterns\n\n## Overview\n\nAgent 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.\n\n## Prerequisites\n\n- Sprint plugin installed and configured (`\u002Fplugin install sprint`)\n- Sprint directory initialized at `.claude\u002Fsprint\u002F[N]\u002F`\n- `specs.md` written with clear scope and testing configuration\n- Familiarity with the sprint phase lifecycle (see the `sprint-workflow` skill)\n\n## Instructions\n\n1. Structure every agent spawn using the SPAWN REQUEST format. Include the agent name, the specification file it should read, and any scope constraints:\n   ```\n   SPAWN REQUEST\n   Agent: python-dev\n   Specs: .claude\u002Fsprint\u002F1\u002Fbackend-specs.md\n   Contract: .claude\u002Fsprint\u002F1\u002Fapi-contract.md\n   Scope: Authentication endpoints only\n   ```\n2. 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.\n3. Collect structured reports from every agent upon completion. Each report must include: work completed, files modified, tests added, and conformity status against the specification.\n4. When running agents in parallel, partition work by domain boundary (e.g., backend vs. frontend vs. CI\u002FCD). Never assign overlapping file paths to concurrent agents.\n5. 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.\n6. For testing agents, pass the UI test report format shown in `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fui-test-report.md` so results follow a consistent schema including test counts, coverage, failures, and console errors.\n\n## Output\n\n- SPAWN REQUEST blocks consumed by the sprint orchestrator to launch agents\n- Structured agent reports containing: summary, files changed, test results, and conformity status\n- UI test reports with pass\u002Ffail counts, coverage details, failure descriptions, and console error logs\n- Updated `status.md` reflecting completed and remaining work after each iteration\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Agent receives wrong specification file | Incorrect path in SPAWN REQUEST | Verify the sprint directory number and file name before spawning |\n| Overlapping file modifications from parallel agents | Scope boundaries not clearly defined | Partition work by domain; assign distinct directories to each agent |\n| Agent report missing required fields | Agent instructions lack report format | Include the structured report template in the agent prompt |\n| Infinite iteration loop | Specs never fully satisfied | Check `status.md` for blocking issues; the orchestrator pauses after 5 iterations |\n| Agent not found | Misspelled agent name in SPAWN REQUEST | Verify agent markdown files exist in `agents\u002F` directory |\n\n## Examples\n\n**Spawning parallel implementation agents:**\n```\nSPAWN REQUEST\nAgent: python-dev\nSpecs: .claude\u002Fsprint\u002F1\u002Fbackend-specs.md\nContract: .claude\u002Fsprint\u002F1\u002Fapi-contract.md\n\nSPAWN REQUEST\nAgent: nextjs-dev\nSpecs: .claude\u002Fsprint\u002F1\u002Ffrontend-specs.md\nContract: .claude\u002Fsprint\u002F1\u002Fapi-contract.md\n```\nBoth agents share the same `api-contract.md` to ensure API compatibility.\n\n**Structured agent report format:**\n```\nAGENT REPORT\nAgent: python-dev\nStatus: COMPLETE\nFiles Modified: src\u002Fauth\u002Froutes.py, src\u002Fauth\u002Fmodels.py, tests\u002Ftest_auth.py\nTests: 12 passed, 0 failed\nConformity: All backend-specs requirements implemented\nNotes: JWT token expiry set to 24h per spec\n```\n\n**Testing agent coordination:**\n```\nSPAWN REQUEST\nAgent: qa-test-agent\nSpecs: .claude\u002Fsprint\u002F1\u002Fspecs.md\nRun After: python-dev, nextjs-dev\n\nSPAWN REQUEST\nAgent: ui-test-agent\nSpecs: .claude\u002Fsprint\u002F1\u002Fspecs.md\nRun After: qa-test-agent\n```\n\n## Resources\n\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fui-test-report.md` -- Structured UI test report format with coverage and failure tracking\n- Sprint workflow skill for phase lifecycle context\n- API contract skill for shared interface design\n- Sprint plugin README for agent architecture overview",{"name":5,"author":48,"license":14,"version":49,"description":50,"allowed-tools":51,"compatible-with":52},"Damien Laine \u003Cdamien.laine@gmail.com>","1.0.0","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. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.\n","Read","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fcommunity\u002Fsprint\u002Fskills\u002Fagent-patterns",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add micsapp\u002Fmicstec-skills --skill agent-patterns",{"tool":66,"command":67},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill agent-patterns",{"tool":69,"command":70},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill agent-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fcommunity\u002Fsprint\u002Fskills\u002Fagent-patterns\u002FSKILL.md",true,[74,80,84],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Ferrors.md","REFERENCE","参考文档",165,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fcommunity\u002Fsprint\u002Fskills\u002Fagent-patterns\u002Freferences\u002Ferrors.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fexamples.md",8110,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fcommunity\u002Fsprint\u002Fskills\u002Fagent-patterns\u002Freferences\u002Fexamples.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fui-test-report.md",672,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fcommunity\u002Fsprint\u002Fskills\u002Fagent-patterns\u002Freferences\u002Fui-test-report.md",[89,124,151,171,191,216],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":103,"publishedAt":43},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[95,98],{"categoryNo":96,"categoryName":97,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":136,"publishedAt":43},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[130,131,134,135],{"categoryNo":96,"categoryName":97,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":132,"categoryName":133,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},[137,138,139,140,105,141,42,142,143,144,145,146,113,114,120,147,148,121,149,150],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":43},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[157],{"categoryNo":96,"categoryName":97,"taxonomyType":20,"taxonomyTypeDesc":21},[159,160,161,162,105,108,113,114,163,35,164,165,166,167,168,121,169,170,150,123],"policy","authoring","apim policy authoring","security","access","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":179,"publishedAt":43},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[177,178],{"categoryNo":96,"categoryName":97,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},[180,162,181,113,165,182,105,137,183,184,185,186,114,187,121,188,189,190,122,123],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":197,"publishedAt":43},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[198,199,200,139,201,202,203,204,113,205,206,207,208,209,210,211,212,213,214,215],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":222,"publishedAt":43},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[218,223,224,225,226,227,228,35,229,230],"npm","js","calculate","node","math","user","compute","errors"]