[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79BKQDGC1YF11RPCZ6S29K7":3,"skill-same:01M79BKQDGC1YF11RPCZ6S29K7":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79BKQDGC1YF11RPCZ6S29K7","agent-coordination",null,"Agent assignment matrix, blocker escalation, and TDM coordination patterns. Use when assigning work to specialists, managing blockers, or coordinating multi-agent workflows.","sahil-kaushik1\u002FAuditing-Workflow","sahil-kaushik1","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F143880923?v=4","01M79BEEK3947RQYD3WC00K9W3","Sahil Kaushik","01M79BEEKVHPFPTNBDB0GFXBHE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fagent-coordination\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: agent-coordination\ndescription: Agent assignment matrix, blocker escalation, and TDM coordination patterns. Use when assigning work to specialists, managing blockers, or coordinating multi-agent workflows.\nallowed-tools: Read, Grep, Glob\n---\n\n# Agent Coordination Skill\n\n## Purpose\n\nGuide correct agent assignment, blocker escalation, and delivery coordination following the TDM role boundaries.\n\n## When This Skill Applies\n\nInvoke this skill when:\n\n- Assigning work to specialist agents\n- Managing blockers across agents\n- Coordinating multi-agent workflows\n- Escalating issues to ARCHitect\u002FPOPM\n- Verifying pre-implementation gate\n- Updating Linear with evidence\n\n## Stop-the-Line Conditions\n\n### FORBIDDEN Patterns\n\n```text\n# FORBIDDEN: Wrong agent assignment\nDatabase work → BE Developer    # WRONG: Use Data Engineer!\nSecurity validation → QAS       # WRONG: Use Security Engineer!\nDocumentation → BE Developer    # WRONG: Use Tech Writer!\n\n# FORBIDDEN: Skipping pre-implementation gate\nStart coding before BSA spec    # Must have acceptance criteria first\n\n# FORBIDDEN: Unresolved blockers >4 hours\nBlocker exists but not escalated  # Escalate within 1 hour\n```\n\n### CORRECT Patterns\n\n```text\n# CORRECT: Right agent for the job\nDatabase work → Data Engineer\nSecurity validation → Security Engineer\nDocumentation → Tech Writer\nPlanning\u002FSpecs → BSA\nArchitecture review → System Architect\nAPI implementation → BE Developer\nUI implementation → FE Developer\nTesting → QAS\nPR\u002FRelease → RTE\n\n# CORRECT: Pre-implementation gate\n1. BSA creates spec with acceptance criteria\n2. System Architect reviews patterns\n3. THEN specialist executes\n```\n\n## Agent Assignment Matrix (MANDATORY)\n\n| Work Type           | Correct Agent     | Never Use           |\n| ------------------- | ----------------- | ------------------- |\n| Database\u002FMigrations | Data Engineer     | BE Developer        |\n| Security\u002FRLS        | Security Engineer | QAS                 |\n| Documentation       | Tech Writer       | BE\u002FFE Developer     |\n| Specs\u002FPlanning      | BSA               | Any implementation  |\n| Architecture        | System Architect  | Direct to developer |\n| API Routes          | BE Developer      | FE Developer        |\n| UI Components       | FE Developer      | BE Developer        |\n| Testing\u002FQA          | QAS               | Implementation team |\n| PR\u002FReleases         | RTE               | Developers          |\n\n**Reference**: `docs\u002Fworkflow\u002FTDM_AGENT_ASSIGNMENT_MATRIX.md`\n\n## Blocker Escalation Protocol\n\n### When to Escalate\n\n| Condition              | Escalate To | Deadline    |\n| ---------------------- | ----------- | ----------- |\n| Blocker > 1 hour       | TDM         | Immediately |\n| Blocker > 4 hours      | ARCHitect   | Urgent      |\n| Architecture ambiguity | ARCHitect   | Before work |\n| Cross-team dependency  | TDM + POPM  | Same day    |\n| Security concern       | SecEng      | Immediately |\n\n### Escalation Template\n\n```markdown\n**Blocker Escalation**\n\n**Ticket**: {{TICKET_PREFIX}}-XXX\n**Blocked Since**: [timestamp]\n**Agent**: [which specialist is blocked]\n\n**Issue**:\n[Clear description of what's blocking progress]\n\n**Attempts Made**:\n\n1. [What was tried]\n2. [What was tried]\n\n**Request**:\n[Specific ask - decision needed, resource needed, etc.]\n```\n\n## Pre-Implementation Gate\n\n**MANDATORY** before any implementation work:\n\n```text\n1. BSA creates spec with:\n   - [ ] Clear acceptance criteria\n   - [ ] Pattern references for execution\n   - [ ] Success validation command\n\n2. System Architect reviews:\n   - [ ] Pattern compliance\n   - [ ] RLS requirements (if database)\n   - [ ] Security implications\n\n3. THEN implementation can begin\n```\n\n## Evidence Attachment\n\nAll work must include evidence in Linear:\n\n````markdown\n**Implementation Evidence**\n\n**Session ID**: [Claude session ID]\n**Agent**: [which specialist]\n**Ticket**: {{TICKET_PREFIX}}-XXX\n\n**Work Completed**:\n\n- [x] Task 1\n- [x] Task 2\n\n**Validation**:\n\n```bash\nyarn ci:validate\n# All checks passed\n```\n````\n\n**Next Steps**: [if any]\n\n```\n\n## TDM Boundaries\n\n### TDM Does\n\n- ✅ Track delivery progress\n- ✅ Update Linear tickets\n- ✅ Escalate blockers\n- ✅ Attach evidence\n- ✅ React to issues\n\n### TDM Does NOT\n\n- ❌ Orchestrate feature work (ARCHitect's job)\n- ❌ Run CI\u002FCD validation (specialists' job)\n- ❌ Execute technical work (specialists' job)\n- ❌ Proactively assign features (ARCHitect's job)\n\n## Authoritative References\n\n- **Agent Assignment Matrix**: `docs\u002Fworkflow\u002FTDM_AGENT_ASSIGNMENT_MATRIX.md`\n- **Agent Workflow SOP v1.3**: `docs\u002Fsop\u002FAGENT_WORKFLOW_SOP.md`\n- **CONTRIBUTING.md**: Workflow requirements\n- **Linear SOP skill**: Evidence attachment templates\n```\n","# Agent Coordination Skill\n\n## Purpose\n\nGuide correct agent assignment, blocker escalation, and delivery coordination following the TDM role boundaries.\n\n## When This Skill Applies\n\nInvoke this skill when:\n\n- Assigning work to specialist agents\n- Managing blockers across agents\n- Coordinating multi-agent workflows\n- Escalating issues to ARCHitect\u002FPOPM\n- Verifying pre-implementation gate\n- Updating Linear with evidence\n\n## Stop-the-Line Conditions\n\n### FORBIDDEN Patterns\n\n```text\n# FORBIDDEN: Wrong agent assignment\nDatabase work → BE Developer    # WRONG: Use Data Engineer!\nSecurity validation → QAS       # WRONG: Use Security Engineer!\nDocumentation → BE Developer    # WRONG: Use Tech Writer!\n\n# FORBIDDEN: Skipping pre-implementation gate\nStart coding before BSA spec    # Must have acceptance criteria first\n\n# FORBIDDEN: Unresolved blockers >4 hours\nBlocker exists but not escalated  # Escalate within 1 hour\n```\n\n### CORRECT Patterns\n\n```text\n# CORRECT: Right agent for the job\nDatabase work → Data Engineer\nSecurity validation → Security Engineer\nDocumentation → Tech Writer\nPlanning\u002FSpecs → BSA\nArchitecture review → System Architect\nAPI implementation → BE Developer\nUI implementation → FE Developer\nTesting → QAS\nPR\u002FRelease → RTE\n\n# CORRECT: Pre-implementation gate\n1. BSA creates spec with acceptance criteria\n2. System Architect reviews patterns\n3. THEN specialist executes\n```\n\n## Agent Assignment Matrix (MANDATORY)\n\n| Work Type           | Correct Agent     | Never Use           |\n| ------------------- | ----------------- | ------------------- |\n| Database\u002FMigrations | Data Engineer     | BE Developer        |\n| Security\u002FRLS        | Security Engineer | QAS                 |\n| Documentation       | Tech Writer       | BE\u002FFE Developer     |\n| Specs\u002FPlanning      | BSA               | Any implementation  |\n| Architecture        | System Architect  | Direct to developer |\n| API Routes          | BE Developer      | FE Developer        |\n| UI Components       | FE Developer      | BE Developer        |\n| Testing\u002FQA          | QAS               | Implementation team |\n| PR\u002FReleases         | RTE               | Developers          |\n\n**Reference**: `docs\u002Fworkflow\u002FTDM_AGENT_ASSIGNMENT_MATRIX.md`\n\n## Blocker Escalation Protocol\n\n### When to Escalate\n\n| Condition              | Escalate To | Deadline    |\n| ---------------------- | ----------- | ----------- |\n| Blocker > 1 hour       | TDM         | Immediately |\n| Blocker > 4 hours      | ARCHitect   | Urgent      |\n| Architecture ambiguity | ARCHitect   | Before work |\n| Cross-team dependency  | TDM + POPM  | Same day    |\n| Security concern       | SecEng      | Immediately |\n\n### Escalation Template\n\n```markdown\n**Blocker Escalation**\n\n**Ticket**: {{TICKET_PREFIX}}-XXX\n**Blocked Since**: [timestamp]\n**Agent**: [which specialist is blocked]\n\n**Issue**:\n[Clear description of what's blocking progress]\n\n**Attempts Made**:\n\n1. [What was tried]\n2. [What was tried]\n\n**Request**:\n[Specific ask - decision needed, resource needed, etc.]\n```\n\n## Pre-Implementation Gate\n\n**MANDATORY** before any implementation work:\n\n```text\n1. BSA creates spec with:\n   - [ ] Clear acceptance criteria\n   - [ ] Pattern references for execution\n   - [ ] Success validation command\n\n2. System Architect reviews:\n   - [ ] Pattern compliance\n   - [ ] RLS requirements (if database)\n   - [ ] Security implications\n\n3. THEN implementation can begin\n```\n\n## Evidence Attachment\n\nAll work must include evidence in Linear:\n\n````markdown\n**Implementation Evidence**\n\n**Session ID**: [Claude session ID]\n**Agent**: [which specialist]\n**Ticket**: {{TICKET_PREFIX}}-XXX\n\n**Work Completed**:\n\n- [x] Task 1\n- [x] Task 2\n\n**Validation**:\n\n```bash\nyarn ci:validate\n# All checks passed\n```\n````\n\n**Next Steps**: [if any]\n\n```\n\n## TDM Boundaries\n\n### TDM Does\n\n- ✅ Track delivery progress\n- ✅ Update Linear tickets\n- ✅ Escalate blockers\n- ✅ Attach evidence\n- ✅ React to issues\n\n### TDM Does NOT\n\n- ❌ Orchestrate feature work (ARCHitect's job)\n- ❌ Run CI\u002FCD validation (specialists' job)\n- ❌ Execute technical work (specialists' job)\n- ❌ Proactively assign features (ARCHitect's job)\n\n## Authoritative References\n\n- **Agent Assignment Matrix**: `docs\u002Fworkflow\u002FTDM_AGENT_ASSIGNMENT_MATRIX.md`\n- **Agent Workflow SOP v1.3**: `docs\u002Fsop\u002FAGENT_WORKFLOW_SOP.md`\n- **CONTRIBUTING.md**: Workflow requirements\n- **Linear SOP skill**: Evidence attachment templates\n```\n",{"name":5,"description":7,"allowed-tools":24},"Read, Grep, Glob","main","39a25d63191d67efe43cdce5b7507069e2307f0f",".claude\u002Fskills\u002Fagent-coordination","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1","https:\u002F\u002Fdrive.google.com\u002Ffile\u002Fd\u002F1Te4TcrpgcN4j8DsYqVdjPl4QXVbs5XXo\u002Fview?usp=drive_link","Web3 security researcher \u002F developer","2026-10-18 15:17:21",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add sahil-kaushik1\u002FAuditing-Workflow --skill agent-coordination",{"tool":39,"command":40},"bunx","bunx skills add sahil-kaushik1\u002FAuditing-Workflow --skill agent-coordination",{"tool":42,"command":43},"pnpm","pnpm dlx skills add sahil-kaushik1\u002FAuditing-Workflow --skill agent-coordination","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fagent-coordination\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"README.md","REFERENCE","参考文档",1582,"https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fagent-coordination\u002FREADME.md",[54,60,66,73,80,87],{"skillNo":55,"name":56,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79BSEAG0SS9CC2EN1S51K2X","stripe-patterns","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsync\u002Frendertrust\u002F.claude\u002Fskills\u002Fstripe-patterns\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79BSBAZXQBWCPKYJP38A35B","payment-patterns","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsync\u002Fkeryk-ai\u002F.claude\u002Fskills\u002Fpayment-patterns\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79BS8PKZXFGBNQBS2GHNXZW","testing-patterns","Testing patterns for Jest and Playwright. Use when writing tests, setting up test fixtures, or validating RLS enforcement. Routes to existing test conventions.","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Ftesting-patterns\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79BS3PR92A4QNEJAFNDKB2G","team-coordination","Agent Teams orchestration patterns for multi-agent SAFe workflows. Use when spawning agent teams, coordinating teammates, enforcing quality gates via task dependencies, or orchestrating the 11-agent SAFe pipeline. Covers team creation, messaging, shared task lists, and SAFe gate enforcement. Do NOT use for single-agent or simple subagent workflows.","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fteam-coordination\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M79BRZ422QD8D5QHQMXAVPWZ","task-compilation","Compile broad audit goals into structured proof obligations with 9 mandatory fields. Used after decomposition by the Threat Modeler agent.","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Ftask-compilation\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M79BRV2MK2AJZBNSE2BETP28","storage-layout-analysis","Proxy patterns, slot collisions, upgrade safety. Used during decomposition to identify storage-related vulnerabilities in upgradeable contracts.","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fstorage-layout-analysis\u002FSKILL.md",[],[]]