[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WZVX2CB62P50HDZBAP0Y9G":3,"skill-same:01M6WZVX2CB62P50HDZBAP0Y9G":73},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6WZVX2CB62P50HDZBAP0Y9G","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\u002Fwaza","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6WZT4PAP160SPCF851532KH",1511,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fiterative-retrieval\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"retrieval","iterative retrieval","max","when","scoped","for","high","with","coordinator","complete","cycle","use","context","work","coordination","why","protocol","validation","tasks","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":48,"license":15,"confidence":30,"description":7},"agent-coordination","main","116214a33b5e07766539f64c0ea21521467829bf",".github\u002Fskills\u002Fiterative-retrieval",101,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza","https:\u002F\u002Fmicrosoft.github.io\u002Fwaza\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-15 04:18:35",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add microsoft\u002Fwaza --skill iterative-retrieval",{"tool":65,"command":66},"bunx","bunx skills add microsoft\u002Fwaza --skill iterative-retrieval",{"tool":68,"command":69},"pnpm","pnpm dlx skills add microsoft\u002Fwaza --skill iterative-retrieval","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fiterative-retrieval\u002FSKILL.md",true,[],[74,105,131,158,178,191],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":84,"publishedAt":43},"01M6X00A438VG96V20V1VMDHCM","waza-runner","Run evaluations on Agent Skills to measure their effectiveness. \nUSE FOR: \"run skill evals\", \"evaluate my skill\", \"test skill quality\", \n\"check skill triggers\", \"skill compliance check\", \"measure skill performance\",\n\"run evals on [skill-name]\", \"grade skill execution\".\nDO NOT USE FOR: writing skills (use skill-authoring), improving frontmatter \n(use sensei), or general testing unrelated to skills.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fblob\u002Fmain\u002Fwaza-runner\u002FSKILL.md",[80,83],{"categoryNo":81,"categoryName":82,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[85,86,87,88,89,90,91,92,93,29,94,95,96,97,98,99,100,101,102,103,104],"waza runner","runner","waza","frontmatter","run","triggers","do","my","general","evals","unrelated","writing skills","my skill","sensei","Test Skill","run evals","performance","writing","testing","authoring",{"skillNo":106,"name":87,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":112,"publishedAt":43},"01M6X003ZZKY5WQ5SWPAQ3MJMS","**WORKFLOW SKILL** - Evaluate AI agent skills using structured benchmarks with YAML specs, fixture isolation, and pluggable validators. USE FOR: run waza, waza help, run eval, run benchmark, evaluate skill, test agent, generate eval suite, init eval, compare results, score agent, agent evaluation, skill testing, cross-model comparison. DO NOT USE FOR: improving skill frontmatter (use waza dev), creating new skills from scratch (use skill-creator), token counting or budget checks (use waza tokens). INVOKES: Copilot SDK executor, mock engine, code\u002Fregex validators. FOR SINGLE OPERATIONS: use waza run directly for a single benchmark.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fblob\u002Fmain\u002Fskills\u002Fwaza\u002FSKILL.md",[110,111],{"categoryNo":81,"categoryName":82,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[87,89,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,103,128,129,130],"workflow skill","executor","fixture","eval","compare results","model","Evaluation","evaluate skill","code","eval suite","generate","copilot","init","workflow","ai agent","counting","new","skill-creator",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":146,"publishedAt":43},"01M6WZZZHCTPZ8YF9564J3QJVT","waza-interactive","Interactive workflow partner for creating, testing, and improving AI agent skills with waza. USE FOR: run my evals, check my skill, compare models, create eval suite, debug failing tests, is my skill ready, ship readiness, interpret results, improve score. DO NOT USE FOR: general coding, non-skill work, writing skill content (use skill-authoring), improving frontmatter only (use sensei).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fblob\u002Fmain\u002Fskills\u002Fwaza-interactive\u002FSKILL.md",[137,138,143],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":144,"categoryName":145,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000036","内容创作者",[147,87,148,149,102,103,127,35,150,122,29,104,91,93,94,151,152,153,116,37,154,97,89,155,156,98,157,126],"waza interactive","interactive","tests","general coding","ready","only","failing","improve","create","debug","create eval",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":165,"publishedAt":43},"01M6WZZTQR955SVJ02J33DGQYK","code-explainer","Explains code snippets in plain English, breaking down what the code does step by step. Perfect for learning, code reviews, or documentation.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fblob\u002Fmain\u002Fskills\u002Fcode-explainer\u002FSKILL.md",[164],{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},[166,167,121,168,169,170,29,171,172,173,174,175,176,177],"code explainer","explainer","learning","plain","down","reviews","step by step","english","snippets","what the","plain english","documentation",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":43},"01M6WZZR27J4RE4J10M38ECM26","compatibility-skill","Read fixture status and report whether it is ready.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fblob\u002Fmain\u002Finternal\u002Ftestdata\u002Fcompatibility\u002Fv1\u002FSKILL.md",[],[185,186,187,115,151,188,189,190],"compatibility skill","compatibility","it","read","report","status",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":197,"publishedAt":43},"01M6WZZMYWAKWE36WD4PHQK8V2","evidence-judge","Read a supplied report and summarize its recorded status and numeric items.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fwaza\u002Fblob\u002Fmain\u002Fexamples\u002Fevidence-judge\u002FSKILL.md",[],[198,199,200,188,189,190,201],"evidence","evidence judge","judge","summarize"]