[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BBSX73N3W5SWJ9XHVVJQ4":3,"skill-same:01M69BBSX73N3W5SWJ9XHVVJQ4":56},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M69BBSX73N3W5SWJ9XHVVJQ4","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\u002Ffsi-banking-payments-dispute-resolution-accelerator","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BAVFSPPF5KP50DCBC2R4Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fiterative-retrieval\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25],"iterative retrieval","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":31,"license":15,"confidence":32,"description":7},"agent-coordination","high","main","5494201db9619bc6c0de7999caa5ae7ae315e6be",".github\u002Fskills\u002Fiterative-retrieval",3,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-10-27 01:08:00",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add microsoft\u002Ffsi-banking-payments-dispute-resolution-accelerator --skill iterative-retrieval",{"tool":48,"command":49},"bunx","bunx skills add microsoft\u002Ffsi-banking-payments-dispute-resolution-accelerator --skill iterative-retrieval",{"tool":51,"command":52},"pnpm","pnpm dlx skills add microsoft\u002Ffsi-banking-payments-dispute-resolution-accelerator --skill iterative-retrieval","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fiterative-retrieval\u002FSKILL.md",true,[],[57,68,75,81,95,109],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":64,"publishedAt":26},"01M69BCQ2R27TFYA8Q03XFNFWM","{skill-name}","{what this skill teaches agents}","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskill.md",[63],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[65,66,67],"{skill name}","testing","design",{"skillNo":69,"name":70,"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":71,"categories":72,"keywords":73,"publishedAt":26},"01M69BCNFGJTKKASKWDB0MM668","azd-seed-hook","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.squad\u002Fskills\u002Fazd-seed-hook\u002FSKILL.md",[],[74],"azd seed hook",{"skillNo":76,"name":59,"nameZh":6,"description":60,"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":80,"publishedAt":26},"01M69BCDES6M5FRTCMY7214B94","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.squad\u002Fskill.md",[79],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[65,66,67],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":91,"publishedAt":26},"01M69BCBAGT24AD5SBDP876P09","tiered-memory","Three-tier agent memory model (hot\u002Fcold\u002Fwiki) for context reduction per spawn","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftiered-memory\u002FSKILL.md",[87,90],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[92,93,67,94],"memory","tiered memory","performance",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":104,"publishedAt":26},"01M69BC9SWSK7ZX02AKTVT16E9","test-discipline","Update tests when changing APIs — no exceptions","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftest-discipline\u002FSKILL.md",[101],{"categoryNo":102,"categoryName":103,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[105,106,107,108],"test discipline","test","sync","update",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":26},"01M69BC7MR12QTSH97DCQYB81N","squad","Squad's command catalog and interactive menu. Invoke via \u002Fsquad (slash command) or natural language (\"squad commands\", \"what can squad do\", \"show me squad options\"). Presents categorized operations (Install & Upgrade, Team Management, Issues & PRs, Plugins & Skills, Model & Cost, Sessions & State) as an interactive picker. Routes to the right squad CLI command or the Squad coordinator agent.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsquad\u002FSKILL.md",[],[111,116,117,118],"cli","squad commands","sessions"]