[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E5TCQBJTYM8SXD3BJV5QG5":3,"skill-same:01M6E5TCQBJTYM8SXD3BJV5QG5":51},{"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":17,"publishedAt":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":13,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M6E5TCQBJTYM8SXD3BJV5QG5","team-reset",null,"Transparent agent reset — shut down unresponsive agents and re-orient the implicit team, reporting roster changes","parametrization\u002F2real-team-framework","parametrization","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1111097?v=4","01M6E5MC117M94CEXKX3C96PPX","01M6E5MC7YWG5N3VV4792VFK85",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fparametrization\u002F2real-team-framework\u002Fblob\u002Fmain\u002Fintake\u002Fnoorinalabs-2026-06\u002Fcandidates\u002Fskills\u002Fteam-reset\u002FSKILL.md",[],[18,19,20,21,22,23,24],"team","reset","team reset","reporting","orient","name","roster","2026-11-10 10:12:30",false,"---\nname: team-reset\ndescription: Transparent agent reset — shut down unresponsive agents and re-orient the implicit team, reporting roster changes\nargs: team_name\n---\n\nHandle the agent reset lifecycle for the `{team_name}` team.\n\n> **Harness note (2026-06-16):** the current Claude Code harness has **no `TeamCreate`\u002F`TeamDelete` tools**. The session runs on a **single implicit team** — there is nothing to delete or recreate. \"Team reset\" in this harness therefore means **shutting down running agents and re-orienting**, not tearing a team config down and rebuilding it. The steps below have been updated accordingly; the old TeamDelete\u002FTeamCreate\u002Fconfig-file steps no longer apply.\n\n## Instructions\n\n### 1. Report current team state\n\nRead the current team roster from `.claude\u002Fteam\u002Froster\u002F` and report to the user:\n\n```\n**Current team: {team_name}**\n| Role | Name | Status |\n|------|------|--------|\n| Manager | Fatima Okonkwo | Active |\n| ... | ... | ... |\n```\n\nList all active roster members with their roles and status.\n\n### 2. Send shutdown requests\n\nSend a `shutdown_request` message via `SendMessage` to ALL agents you spawned this session:\n\n```json\n{\"type\": \"shutdown_request\", \"reason\": \"Team reset initiated\"}\n```\n\nSend one message per agent (structured messages cannot be broadcast). Wait ~5–30 seconds for agents to acknowledge and terminate.\n\n### 3. Handle unresponsive agents\n\nThere is no `TeamDelete` to force in this harness, so a stuck agent cannot be cleared by deleting a team config. If an agent does not acknowledge its shutdown request:\n\n1. Report to user: \"{N} agent(s) unresponsive: {names}.\"\n2. Re-send the `shutdown_request` once more.\n3. If it still does not terminate, surface it to the user — a lingering agent is a UI\u002Fresource annoyance, not a blocker; spawning fresh agents is unaffected because the team is implicit. Do NOT attempt to edit or delete any `~\u002F.claude\u002Fteams\u002F...` config (that mechanism is gone).\n\n### 4. Re-orient (no recreate needed)\n\nThe implicit `{team_name}` team persists for the session — there is nothing to recreate. Re-read the roster files in `.claude\u002Fteam\u002Froster\u002F` so you have the current roster in context for the next round of spawns.\n\nReport to user:\n\n```\n**Implicit team re-oriented:** {team_name}\n| Role | Name | Status |\n|------|------|--------|\n| Manager | Fatima Okonkwo | Active |\n| ... | ... | ... |\n```\n\n### 5. Highlight roster changes\n\nIf there are differences between the prior roster and the current roster files (hires, departures, role changes), explicitly report them:\n\n```\n**Roster changes:**\n- DEPARTED: {name} ({role}) — {reason}\n- HIRED: {name} ({role}) — replacing {departed name}\n- ROLE CHANGE: {name} — {old role} → {new role}\n```\n\nIf no changes: \"Roster unchanged from previous round.\"\n\n### 6. Ready confirmation\n\nConfirm the team is ready for work:\n\n```\nTeam `{team_name}` is ready ({N} roster members). Spawn agents via the Agent tool\n(team_name: {team_name}) when ready — the orchestrator is the sole spawner.\n```\n\n## What remains manual\n\n- The orchestrating Claude instance must still spawn individual agents via the `Agent` tool (agents cannot self-spawn)\n- Roster file changes (hires\u002Ffires) must be committed separately\n","Handle the agent reset lifecycle for the `{team_name}` team.\n\n> **Harness note (2026-06-16):** the current Claude Code harness has **no `TeamCreate`\u002F`TeamDelete` tools**. The session runs on a **single implicit team** — there is nothing to delete or recreate. \"Team reset\" in this harness therefore means **shutting down running agents and re-orienting**, not tearing a team config down and rebuilding it. The steps below have been updated accordingly; the old TeamDelete\u002FTeamCreate\u002Fconfig-file steps no longer apply.\n\n## Instructions\n\n### 1. Report current team state\n\nRead the current team roster from `.claude\u002Fteam\u002Froster\u002F` and report to the user:\n\n```\n**Current team: {team_name}**\n| Role | Name | Status |\n|------|------|--------|\n| Manager | Fatima Okonkwo | Active |\n| ... | ... | ... |\n```\n\nList all active roster members with their roles and status.\n\n### 2. Send shutdown requests\n\nSend a `shutdown_request` message via `SendMessage` to ALL agents you spawned this session:\n\n```json\n{\"type\": \"shutdown_request\", \"reason\": \"Team reset initiated\"}\n```\n\nSend one message per agent (structured messages cannot be broadcast). Wait ~5–30 seconds for agents to acknowledge and terminate.\n\n### 3. Handle unresponsive agents\n\nThere is no `TeamDelete` to force in this harness, so a stuck agent cannot be cleared by deleting a team config. If an agent does not acknowledge its shutdown request:\n\n1. Report to user: \"{N} agent(s) unresponsive: {names}.\"\n2. Re-send the `shutdown_request` once more.\n3. If it still does not terminate, surface it to the user — a lingering agent is a UI\u002Fresource annoyance, not a blocker; spawning fresh agents is unaffected because the team is implicit. Do NOT attempt to edit or delete any `~\u002F.claude\u002Fteams\u002F...` config (that mechanism is gone).\n\n### 4. Re-orient (no recreate needed)\n\nThe implicit `{team_name}` team persists for the session — there is nothing to recreate. Re-read the roster files in `.claude\u002Fteam\u002Froster\u002F` so you have the current roster in context for the next round of spawns.\n\nReport to user:\n\n```\n**Implicit team re-oriented:** {team_name}\n| Role | Name | Status |\n|------|------|--------|\n| Manager | Fatima Okonkwo | Active |\n| ... | ... | ... |\n```\n\n### 5. Highlight roster changes\n\nIf there are differences between the prior roster and the current roster files (hires, departures, role changes), explicitly report them:\n\n```\n**Roster changes:**\n- DEPARTED: {name} ({role}) — {reason}\n- HIRED: {name} ({role}) — replacing {departed name}\n- ROLE CHANGE: {name} — {old role} → {new role}\n```\n\nIf no changes: \"Roster unchanged from previous round.\"\n\n### 6. Ready confirmation\n\nConfirm the team is ready for work:\n\n```\nTeam `{team_name}` is ready ({N} roster members). Spawn agents via the Agent tool\n(team_name: {team_name}) when ready — the orchestrator is the sole spawner.\n```\n\n## What remains manual\n\n- The orchestrating Claude instance must still spawn individual agents via the `Agent` tool (agents cannot self-spawn)\n- Roster file changes (hires\u002Ffires) must be committed separately\n",{"args":30,"name":5,"description":7},"team_name","main","53ec1032b93d41533a48603e8fae7a92f56cc66c","intake\u002Fnoorinalabs-2026-06\u002Fcandidates\u002Fskills\u002Fteam-reset","https:\u002F\u002Fgithub.com\u002Fparametrization\u002F2real-team-framework","https:\u002F\u002Fgithub.com\u002Fparametrization","2026-09-21 01:06:30",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add parametrization\u002F2real-team-framework --skill team-reset",{"tool":43,"command":44},"bunx","bunx skills add parametrization\u002F2real-team-framework --skill team-reset",{"tool":46,"command":47},"pnpm","pnpm dlx skills add parametrization\u002F2real-team-framework --skill team-reset","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fparametrization\u002F2real-team-framework\u002Fblob\u002Fmain\u002Fintake\u002Fnoorinalabs-2026-06\u002Fcandidates\u002Fskills\u002Fteam-reset\u002FSKILL.md",true,[],[52,72,89,105,120,133],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":25},"01M6E5VG1R7FF1025BZAV6BDTS","wave-wrapup","Finalize a wave — PR review, merge sequencing, issue cleanup, worktree cleanup, and handoff to retro","https:\u002F\u002Fgithub.com\u002Fparametrization\u002F2real-team-framework\u002Fblob\u002Fmain\u002Fintake\u002Fnoorinalabs-2026-06\u002Fcandidates\u002Fskills\u002Fwave-wrapup\u002FSKILL.md",[],[59,60,61,62,63,64,65,66,67,68,18,69,70,23,71],"wave wrapup","wrapup","review","handoff","merge","pr review","pr","cleanup","worktree","retro","issue","worktree cleanup","sequencing",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":25},"01M6E5V9GDF75GV4YD2WPSH912","wave-start","Initialize a new wave — worktree cleanup, branch creation, label setup, status file update","https:\u002F\u002Fgithub.com\u002Fparametrization\u002F2real-team-framework\u002Fblob\u002Fmain\u002Fintake\u002Fnoorinalabs-2026-06\u002Fcandidates\u002Fskills\u002Fwave-start\u002FSKILL.md",[],[79,80,81,66,82,67,83,18,84,85,86,70,87,23,88],"wave start","start","setup","update","file","branch","file update","initialize","creation","status",{"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":95,"publishedAt":25},"01M6E5V4VXEJ39V87VHN1A3AW9","wave-scope","Reconcile declared-vs-labeled wave scope between \u002Fwave-retro and \u002Fwave-kickoff — collect dispositions, fold in retro carry-forwards and memory must-includes, and refresh the meta-issue","https:\u002F\u002Fgithub.com\u002Fparametrization\u002F2real-team-framework\u002Fblob\u002Fmain\u002Fintake\u002Fnoorinalabs-2026-06\u002Fcandidates\u002Fskills\u002Fwave-scope\u002FSKILL.md",[],[96,97,98,99,100,68,101,102,103,69,104],"wave scope","scope","memory","collect","Meta","refresh","reconcile","Fold","kickoff",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":25},"01M6E5TZNPGG5EXZEN1FKJJT6K","wave-retro","Automated wave retrospective — PR analysis, assessments, trust matrix updates, feedback log, charter change proposals","https:\u002F\u002Fgithub.com\u002Fparametrization\u002F2real-team-framework\u002Fblob\u002Fmain\u002Fintake\u002Fnoorinalabs-2026-06\u002Fcandidates\u002Fskills\u002Fwave-retro\u002FSKILL.md",[],[112,68,113,114,65,115,116,18,117,118,119,23],"wave retro","log","change","retrospective","analysis","feedback","proposals","trust",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":25},"01M6E5TR8XB3Z10A9SD4ZYNV45","wave-kickoff","Automated wave planning — branch creation, label management, issue labeling, kickoff comments, and execution plan","https:\u002F\u002Fgithub.com\u002Fparametrization\u002F2real-team-framework\u002Fblob\u002Fmain\u002Fintake\u002Fnoorinalabs-2026-06\u002Fcandidates\u002Fskills\u002Fwave-kickoff\u002FSKILL.md",[],[127,104,128,69,87,23,129,18,130,84,131,132],"wave kickoff","management","plan","execution","planning","execution plan",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":25},"01M6E5TMZAFB6MTVYT750FZDVY","wave-audit","Audit open issues against merged PRs — find and close orphaned issues with proper comments","https:\u002F\u002Fgithub.com\u002Fparametrization\u002F2real-team-framework\u002Fblob\u002Fmain\u002Fintake\u002Fnoorinalabs-2026-06\u002Fcandidates\u002Fskills\u002Fwave-audit\u002FSKILL.md",[],[140,141,142,143,144,145],"audit","wave audit","close","find","open","issues"]