[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BSB2Q6B5AEPF45P89EGKF":3,"skill-same:01M69BSB2Q6B5AEPF45P89EGKF":63},{"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":23,"publishedAt":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M69BSB2Q6B5AEPF45P89EGKF","iterative-retrieval",null,"Max-3-cycle protocol for agent sub-tasks with WHY context and coordinator validation. Use when spawning sub-agents to complete scoped work.","microsoft\u002Fgithub-vteam-industry-demos","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BGH3MXP66NFFBGHRCSQ5D",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fgithub-vteam-industry-demos\u002Fblob\u002Fmain\u002Findustries\u002Fprofessional-services\u002Fai-proposal-factory\u002F.github\u002Fskills\u002Fiterative-retrieval\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26],"iterative retrieval","tasks","validation","2026-11-10 10:12:30",false,"---\nname: \"iterative-retrieval\"\ndescription: \"Max-3-cycle protocol for agent sub-tasks with WHY context and coordinator validation. Use when spawning sub-agents to complete scoped work.\"\ndomain: \"agent-coordination\"\nconfidence: \"high\"\nlicense: MIT\n---\n\n# Iterative Retrieval Skill\n\nSquad agents frequently spawn sub-agents to complete scoped work. Without structure, these\nhandoffs become vague, cycles multiply, and outputs land without being checked. The\n**Iterative Retrieval Pattern** caps cycles at 3, mandates WHY context in every spawn, and\nrequires the coordinator to validate agent output before closing an issue.\n\n---\n\n## Spawn Prompt Template\n\nEvery agent spawn must include the following four sections. Copy and fill in the template:\n\n```\n## Task\n{What you need done — concrete and bounded}\n\n## WHY this matters\n{The motivation and context. What system or user goal does this serve? What breaks if skipped?}\n\n## Success criteria\n{How you will know the output is correct. Be explicit — list acceptance criteria, not vibes.}\nExample:\n- [ ] File X exists and contains Y\n- [ ] No regressions in existing tests\n- [ ] PR is open targeting main with description matching the issue\n\n## Escalation path\n{What the agent should do if uncertain or stuck. \"Stop and ask me\" is valid.}\nExample:\n- If requirements are ambiguous → stop, comment on the issue, set label status:needs-decision\n- If blocked by a dependency → label status:blocked, explain in a comment\n- If 3 cycles exhausted without resolution → write a summary to inbox and surface to coordinator\n```\n\n---\n\n## 3-Cycle Protocol\n\n| Cycle | Description | Exit condition |\n|-------|-------------|----------------|\n| **1** | Initial attempt | Done → coordinator validates. Incomplete → surface delta. |\n| **2** | Targeted retry with specific corrections | Done → coordinator validates. Incomplete → one more. |\n| **3** | Final attempt with all context from cycles 1–2 | Done or escalate — no cycle 4. |\n\n### Rules\n\n1. **After each cycle**, the coordinator evaluates the output against the success criteria\n   before accepting it or spawning the next cycle.\n2. **Objective context forward**: each subsequent spawn includes a summary of what was tried\n   and what is still missing — not just a repeat of the original task.\n3. **Cycle 3 exhausted** → escalate: write a summary to `.squad\u002Fdecisions\u002Finbox\u002F`, label the\n   issue `status:needs-decision`, and notify the user.\n\n---\n\n## Coordinator Validation Checklist\n\nBefore accepting agent output and closing an issue, the coordinator must check:\n\n- [ ] All success criteria from the spawn prompt are met\n- [ ] PR exists and description matches the issue (if code work)\n- [ ] No obvious regressions (grep for TODO\u002FFIXME introduced, build passes)\n- [ ] Agent did not silently skip parts of the task\n- [ ] If the agent reported uncertainty — was it resolved or escalated?\n\nIf any item fails → do **not** accept. Spawn cycle N+1 (up to cycle 3) with specific deltas.\n\n---\n\n## When to Escalate vs Retry\n\n**Retry (cycle N+1)** when:\n- Output is structurally correct but missing specific items\n- Agent misunderstood scope (provide more context and re-run)\n- Partial success — clearly identified remaining delta\n\n**Escalate** when:\n- Requirements are fundamentally unclear (decision needed)\n- 3 cycles complete without convergence\n- Agent returned conflicting results across cycles\n- Task requires elevated permissions or external action\n- The work depends on another issue that isn't done yet\n\n---\n\n## Issue Dedup Check (Mandatory)\n\nBefore any agent creates a GitHub issue, it **must** search for existing open issues to avoid\nduplicates.\n\n```bash\n# Check for existing open issues before creating a new one\ngh issue list --search \"\u003Ckeywords from your issue title>\" --state open\n```\n\n- If an open issue already covers the same problem → **comment on it** instead of creating a new one.\n- If no duplicate → proceed to create the issue.\n- Use 2–3 representative keywords from the planned issue title as the search query.\n\n---\n\n## Mandatory Output Requirement (Research-Then-Execute)\n\nEvery research or analysis task completed under this protocol **MUST** end with at least one\nconcrete action before the cycle is closed. Acceptable follow-up actions:\n\n- GitHub issue created documenting the findings and next steps\n- PR opened implementing a recommendation\n- Decision recorded in `.squad\u002Fdecisions\u002Finbox\u002F`\n- Documented recommendation with a named assignee and due date\n\n**Pure analysis reports without actionable follow-up will be rejected during triage.**\nIf no action is warranted, the agent must explicitly state why and get coordinator sign-off.\n\n---\n\n## Anti-Patterns\n\n- **Spawning without WHY** — agents can't prioritise trade-offs without motivation context.\n- **Accepting output without validating** — one failed check avoids merging broken work.\n- **Cycle 4+** — if 3 cycles haven't converged, the problem is in the requirements, not the agent.\n- **Vague success criteria** — \"looks good\" is not a criterion. Use checkboxes.\n- **Forwarding WHAT without delta** — cycle 2+ prompts must include what cycle 1 got wrong.\n- **Creating issues without dedup check** — always search before creating.\n- **Research without action** — delivering analysis with no issue, PR, decision, or assignee is incomplete work.\n\n---\n\n## Examples\n\n### Good spawn prompt\n```\n## Task\nAdd an \"Iterative Retrieval Protocol\" section to `.squad\u002Fagents\u002Fcoordinator\u002Fcharter.md` explaining\nthe 3-cycle rule, WHY format, and validation checklist.\n\n## WHY this matters\nThe coordinator spawns sub-agents on every round. Without a documented protocol, agents run unbounded\ncycles and outputs go unvalidated — leading to stale issues and silent failures.\n\n## Success criteria\n- [ ] Section \"Iterative Retrieval Protocol\" exists in charter.md\n- [ ] Section documents max-3-cycles rule\n- [ ] Section documents WHY format requirement\n- [ ] Section contains validation checklist (at least 4 items)\n- [ ] No other sections of charter.md are modified\n\n## Escalation path\nIf the charter.md format is unclear, check another agent charter as a reference.\nIf uncertain about content, stop and surface to coordinator.\n```\n\n### Bad spawn prompt (don't do this)\n```\nUpdate the coordinator charter with the iterative retrieval stuff.\n```\n","# Iterative Retrieval Skill\n\nSquad agents frequently spawn sub-agents to complete scoped work. Without structure, these\nhandoffs become vague, cycles multiply, and outputs land without being checked. The\n**Iterative Retrieval Pattern** caps cycles at 3, mandates WHY context in every spawn, and\nrequires the coordinator to validate agent output before closing an issue.\n\n---\n\n## Spawn Prompt Template\n\nEvery agent spawn must include the following four sections. Copy and fill in the template:\n\n```\n## Task\n{What you need done — concrete and bounded}\n\n## WHY this matters\n{The motivation and context. What system or user goal does this serve? What breaks if skipped?}\n\n## Success criteria\n{How you will know the output is correct. Be explicit — list acceptance criteria, not vibes.}\nExample:\n- [ ] File X exists and contains Y\n- [ ] No regressions in existing tests\n- [ ] PR is open targeting main with description matching the issue\n\n## Escalation path\n{What the agent should do if uncertain or stuck. \"Stop and ask me\" is valid.}\nExample:\n- If requirements are ambiguous → stop, comment on the issue, set label status:needs-decision\n- If blocked by a dependency → label status:blocked, explain in a comment\n- If 3 cycles exhausted without resolution → write a summary to inbox and surface to coordinator\n```\n\n---\n\n## 3-Cycle Protocol\n\n| Cycle | Description | Exit condition |\n|-------|-------------|----------------|\n| **1** | Initial attempt | Done → coordinator validates. Incomplete → surface delta. |\n| **2** | Targeted retry with specific corrections | Done → coordinator validates. Incomplete → one more. |\n| **3** | Final attempt with all context from cycles 1–2 | Done or escalate — no cycle 4. |\n\n### Rules\n\n1. **After each cycle**, the coordinator evaluates the output against the success criteria\n   before accepting it or spawning the next cycle.\n2. **Objective context forward**: each subsequent spawn includes a summary of what was tried\n   and what is still missing — not just a repeat of the original task.\n3. **Cycle 3 exhausted** → escalate: write a summary to `.squad\u002Fdecisions\u002Finbox\u002F`, label the\n   issue `status:needs-decision`, and notify the user.\n\n---\n\n## Coordinator Validation Checklist\n\nBefore accepting agent output and closing an issue, the coordinator must check:\n\n- [ ] All success criteria from the spawn prompt are met\n- [ ] PR exists and description matches the issue (if code work)\n- [ ] No obvious regressions (grep for TODO\u002FFIXME introduced, build passes)\n- [ ] Agent did not silently skip parts of the task\n- [ ] If the agent reported uncertainty — was it resolved or escalated?\n\nIf any item fails → do **not** accept. Spawn cycle N+1 (up to cycle 3) with specific deltas.\n\n---\n\n## When to Escalate vs Retry\n\n**Retry (cycle N+1)** when:\n- Output is structurally correct but missing specific items\n- Agent misunderstood scope (provide more context and re-run)\n- Partial success — clearly identified remaining delta\n\n**Escalate** when:\n- Requirements are fundamentally unclear (decision needed)\n- 3 cycles complete without convergence\n- Agent returned conflicting results across cycles\n- Task requires elevated permissions or external action\n- The work depends on another issue that isn't done yet\n\n---\n\n## Issue Dedup Check (Mandatory)\n\nBefore any agent creates a GitHub issue, it **must** search for existing open issues to avoid\nduplicates.\n\n```bash\n# Check for existing open issues before creating a new one\ngh issue list --search \"\u003Ckeywords from your issue title>\" --state open\n```\n\n- If an open issue already covers the same problem → **comment on it** instead of creating a new one.\n- If no duplicate → proceed to create the issue.\n- Use 2–3 representative keywords from the planned issue title as the search query.\n\n---\n\n## Mandatory Output Requirement (Research-Then-Execute)\n\nEvery research or analysis task completed under this protocol **MUST** end with at least one\nconcrete action before the cycle is closed. Acceptable follow-up actions:\n\n- GitHub issue created documenting the findings and next steps\n- PR opened implementing a recommendation\n- Decision recorded in `.squad\u002Fdecisions\u002Finbox\u002F`\n- Documented recommendation with a named assignee and due date\n\n**Pure analysis reports without actionable follow-up will be rejected during triage.**\nIf no action is warranted, the agent must explicitly state why and get coordinator sign-off.\n\n---\n\n## Anti-Patterns\n\n- **Spawning without WHY** — agents can't prioritise trade-offs without motivation context.\n- **Accepting output without validating** — one failed check avoids merging broken work.\n- **Cycle 4+** — if 3 cycles haven't converged, the problem is in the requirements, not the agent.\n- **Vague success criteria** — \"looks good\" is not a criterion. Use checkboxes.\n- **Forwarding WHAT without delta** — cycle 2+ prompts must include what cycle 1 got wrong.\n- **Creating issues without dedup check** — always search before creating.\n- **Research without action** — delivering analysis with no issue, PR, decision, or assignee is incomplete work.\n\n---\n\n## Examples\n\n### Good spawn prompt\n```\n## Task\nAdd an \"Iterative Retrieval Protocol\" section to `.squad\u002Fagents\u002Fcoordinator\u002Fcharter.md` explaining\nthe 3-cycle rule, WHY format, and validation checklist.\n\n## WHY this matters\nThe coordinator spawns sub-agents on every round. Without a documented protocol, agents run unbounded\ncycles and outputs go unvalidated — leading to stale issues and silent failures.\n\n## Success criteria\n- [ ] Section \"Iterative Retrieval Protocol\" exists in charter.md\n- [ ] Section documents max-3-cycles rule\n- [ ] Section documents WHY format requirement\n- [ ] Section contains validation checklist (at least 4 items)\n- [ ] No other sections of charter.md are modified\n\n## Escalation path\nIf the charter.md format is unclear, check another agent charter as a reference.\nIf uncertain about content, stop and surface to coordinator.\n```\n\n### Bad spawn prompt (don't do this)\n```\nUpdate the coordinator charter with the iterative retrieval stuff.\n```\n",{"name":5,"domain":32,"license":15,"confidence":33,"description":7},"agent-coordination","high","main","52a1e8c92456b3469b9a4afdc06d3f2cc4ab6796","industries\u002Fprofessional-services\u002Fai-proposal-factory\u002F.github\u002Fskills\u002Fiterative-retrieval",0,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fgithub-vteam-industry-demos","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-12 13:12:35",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add microsoft\u002Fgithub-vteam-industry-demos --skill iterative-retrieval",{"tool":49,"command":50},"bunx","bunx skills add microsoft\u002Fgithub-vteam-industry-demos --skill iterative-retrieval",{"tool":52,"command":53},"pnpm","pnpm dlx skills add microsoft\u002Fgithub-vteam-industry-demos --skill iterative-retrieval","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fgithub-vteam-industry-demos\u002Fblob\u002Fmain\u002Findustries\u002Fprofessional-services\u002Fai-proposal-factory\u002F.github\u002Fskills\u002Fiterative-retrieval\u002FSKILL.md",true,[57],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fminillm.md","REFERENCE","参考文档",9117,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Femerging-techniques-knowledge-distillation\u002Freferences\u002Fminillm.md",[64,73,82,87,93,104],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":27},"01M69BSDG009WVDPMVMEPS2YSF","reflect","Learning capture system that extracts HIGH\u002FMED\u002FLOW confidence patterns from conversations to prevent repeating mistakes. Use after user corrections (\"no\", \"wrong\"), praise (\"perfect\", \"exactly\"), or when discovering edge cases. Complements .squad\u002Fagents\u002F{agent}\u002Fhistory.md and .squad\u002Fdecisions.md.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fgithub-vteam-industry-demos\u002Fblob\u002Fmain\u002Findustries\u002Fprofessional-services\u002Fai-proposal-factory\u002F.github\u002Fskills\u002Freflect\u002FSKILL.md",[],[66,71,72],"squad","memory",{"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":27},"01M69BS5HM295AZ6QNFZQNP46N","error-recovery","Standard recovery patterns for all squad agents. When something fails, adapt — don't just report the failure.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fgithub-vteam-industry-demos\u002Fblob\u002Fmain\u002Findustries\u002Fprofessional-services\u002Fai-proposal-factory\u002F.github\u002Fskills\u002Ferror-recovery\u002FSKILL.md",[],[80,81,71],"error recovery","report",{"skillNo":83,"name":66,"nameZh":6,"description":67,"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":27},"01M69BQAXVB7E270QGBQ9W4VFW","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fgithub-vteam-industry-demos\u002Fblob\u002Fmain\u002Findustries\u002Fhealthcare-life-sciences\u002Fclaim-processing\u002F.squad\u002Ftemplates\u002Fskills\u002Freflect\u002FSKILL.md",[],[66,71,72],{"skillNo":88,"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":89,"categories":90,"keywords":92,"publishedAt":27},"01M69BPJ5RC4M16E6518P4QWXD","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fgithub-vteam-industry-demos\u002Fblob\u002Fmain\u002Findustries\u002Fhealthcare-life-sciences\u002Fclaim-processing\u002F.squad\u002Ftemplates\u002Fskills\u002Fiterative-retrieval\u002FSKILL.md",[91],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[24,26,25],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":27},"01M69BNYABTXGDSYR7VN91WKE3","fact-checking","Review and validate claims using counter-hypothesis testing. Use when verifying technical content, checking references, validating API endpoints, or performing quality assurance on deliverables.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fgithub-vteam-industry-demos\u002Fblob\u002Fmain\u002Findustries\u002Fhealthcare-life-sciences\u002Fclaim-processing\u002F.squad\u002Ftemplates\u002Fskills\u002Ffact-checking\u002FSKILL.md",[],[100,71,101,102,103],"fact checking","validate","review","testing",{"skillNo":105,"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":106,"categories":107,"keywords":108,"publishedAt":27},"01M69BNRF68PHZWCPKMW365N5R","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fgithub-vteam-industry-demos\u002Fblob\u002Fmain\u002Findustries\u002Fhealthcare-life-sciences\u002Fclaim-processing\u002F.squad\u002Ftemplates\u002Fskills\u002Ferror-recovery\u002FSKILL.md",[],[80,81,71]]