[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GGQRVS1MBP5F6ZMMPGV7VG":3,"skill-same:01M6GGQRVS1MBP5F6ZMMPGV7VG":66},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6GGQRVS1MBP5F6ZMMPGV7VG","discussion-continuity",null,"When a design discussion or evaluation is interrupted by a task or workflow, or when the user says \"present the discussion,\" \"where were we,\" \"show me the discussion,\" or \"resume\" — save or resurface the discussion state using Session Notes.","ahmadulhoq\u002Fagentskel","ahmadulhoq","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3884252?v=4","01M6GGC32SQTQ52FY4JB14FYSY","Ahmadul Hoq","01M6GGC37CJEYM63V3WEHY4Y8V",13,"MIT","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdiscussion-continuity\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"continuity","discussion continuity","design","workflow","notes","state","Evaluation","save","show me","user","session","resume","show","task","me","present","2026-11-10 10:12:30",false,"---\nname: discussion-continuity\nlicense: MIT\ndescription: When a design discussion or evaluation is interrupted by a task or workflow, or when the user says \"present the discussion,\" \"where were we,\" \"show me the discussion,\" or \"resume\" — save or resurface the discussion state using Session Notes.\n---\n\n# Skill: Discussion Continuity\n\nDiscussions have no formal lifecycle. This skill gives them one — a save point\nbefore interruption and a defined retrieval on return.\n\n---\n\n## Operation A — PAUSE (save before switching)\n\n**Trigger:** Agent has an open unanswered gate question AND the user redirects\nto a different task or workflow.\n\nExecute as the **first action** before switching — before any file edits,\nbefore any workflow steps.\n\n1. Write a structured entry to `.memory\u002FRESUME.md` Session Notes:\n\n   ```\n   DISCUSSION PAUSED: [topic]\n   Agreed: [bullet — one line per agreed decision, or \"none yet\"]\n   Open: [bullet — each pending decision with its options]\n   Gate: [exact unanswered question the agent was waiting on]\n   ```\n\n2. Confirm to the user: \"Discussion state saved. Switching to [task].\"\n3. Then execute the interrupting task.\n\n**Important:** The gate field is what prevents treating the return phrase as\nimplementation approval. If the gate is recorded, the agent re-asks it on\nresume instead of assuming approval.\n\n---\n\n## Operation B — RESUME (resurface on return)\n\n**Trigger:** Any of:\n- User says \"present the discussion,\" \"where were we,\" \"show me the discussion,\"\n  \"back to [topic],\" or \"resume\"\n- task-completion Step 6c detects a `DISCUSSION PAUSED:` entry in Session Notes\n\nSteps:\n1. Read `.memory\u002FRESUME.md` Session Notes.\n2. Find any entries prefixed `DISCUSSION PAUSED:`.\n3. Re-present with full structure — topic, agreed decisions, open decisions\n   with options, and the gate question.\n4. Re-ask the gate question explicitly. Do NOT treat the return phrase as an\n   answer to the gate.\n5. Remove the `DISCUSSION PAUSED:` entry from Session Notes only after the\n   gate is answered and discussion is resolved or explicitly parked.\n\n---\n\n## Format example\n\n```\nDISCUSSION PAUSED: BACKLOG.md design\nAgreed: single flat table with Priority column; ID format BL-NNN; Done capped at 5\nOpen: (1) Backlog Mode field for Jira? options: column vs config field vs none\n      (2) Name — BACKLOG vs TODO?\n      (3) Capture convention — how \"add to todo\" maps to a file\nGate: \"Want to proceed with implementation, or adjust the design first?\"\n```\n\n---\n\n## What this does NOT solve\n\n- Agent failing to detect the interruption moment — the PAUSE operation still\n  relies on the agent recognizing an open gate + redirect. This is the weakest\n  link. task-completion Step 6c provides the safety net for missed saves.\n- Multiple simultaneous paused discussions — if two discussions are paused,\n  resurface both and ask the user which to resolve first.\n","# Skill: Discussion Continuity\n\nDiscussions have no formal lifecycle. This skill gives them one — a save point\nbefore interruption and a defined retrieval on return.\n\n---\n\n## Operation A — PAUSE (save before switching)\n\n**Trigger:** Agent has an open unanswered gate question AND the user redirects\nto a different task or workflow.\n\nExecute as the **first action** before switching — before any file edits,\nbefore any workflow steps.\n\n1. Write a structured entry to `.memory\u002FRESUME.md` Session Notes:\n\n   ```\n   DISCUSSION PAUSED: [topic]\n   Agreed: [bullet — one line per agreed decision, or \"none yet\"]\n   Open: [bullet — each pending decision with its options]\n   Gate: [exact unanswered question the agent was waiting on]\n   ```\n\n2. Confirm to the user: \"Discussion state saved. Switching to [task].\"\n3. Then execute the interrupting task.\n\n**Important:** The gate field is what prevents treating the return phrase as\nimplementation approval. If the gate is recorded, the agent re-asks it on\nresume instead of assuming approval.\n\n---\n\n## Operation B — RESUME (resurface on return)\n\n**Trigger:** Any of:\n- User says \"present the discussion,\" \"where were we,\" \"show me the discussion,\"\n  \"back to [topic],\" or \"resume\"\n- task-completion Step 6c detects a `DISCUSSION PAUSED:` entry in Session Notes\n\nSteps:\n1. Read `.memory\u002FRESUME.md` Session Notes.\n2. Find any entries prefixed `DISCUSSION PAUSED:`.\n3. Re-present with full structure — topic, agreed decisions, open decisions\n   with options, and the gate question.\n4. Re-ask the gate question explicitly. Do NOT treat the return phrase as an\n   answer to the gate.\n5. Remove the `DISCUSSION PAUSED:` entry from Session Notes only after the\n   gate is answered and discussion is resolved or explicitly parked.\n\n---\n\n## Format example\n\n```\nDISCUSSION PAUSED: BACKLOG.md design\nAgreed: single flat table with Priority column; ID format BL-NNN; Done capped at 5\nOpen: (1) Backlog Mode field for Jira? options: column vs config field vs none\n      (2) Name — BACKLOG vs TODO?\n      (3) Capture convention — how \"add to todo\" maps to a file\nGate: \"Want to proceed with implementation, or adjust the design first?\"\n```\n\n---\n\n## What this does NOT solve\n\n- Agent failing to detect the interruption moment — the PAUSE operation still\n  relies on the agent recognizing an open gate + redirect. This is the weakest\n  link. task-completion Step 6c provides the safety net for missed saves.\n- Multiple simultaneous paused discussions — if two discussions are paused,\n  resurface both and ask the user which to resolve first.\n",{"name":5,"license":15,"description":7},"main","d94c109a4fad51623dc6048315860e53b32673fb","core\u002Fskills\u002Fdiscussion-continuity",3,"https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel","https:\u002F\u002Fgithub.com\u002Fahmadulhoq","2026-11-07 00:53:22",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add ahmadulhoq\u002Fagentskel --skill discussion-continuity",{"tool":58,"command":59},"bunx","bunx skills add ahmadulhoq\u002Fagentskel --skill discussion-continuity",{"tool":61,"command":62},"pnpm","pnpm dlx skills add ahmadulhoq\u002Fagentskel --skill discussion-continuity","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdiscussion-continuity\u002FSKILL.md",true,[],[67,86,113,139,163,177],{"skillNo":68,"name":69,"nameZh":6,"description":70,"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":40},"01M6GGSN2D57Y8BR50X08Y695H","setup-project","When setting up agentskel on a new project that does not yet have .memory\u002F or .agents\u002F. Use when the user says \"set up agentskel\", \"install agentskel\", or \"add agent memory to this project\".","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Fskills\u002Fsetup-project\u002FSKILL.md",[],[74,75,76,77,78,79,80,81,82,33,83,84,85],"setup project","project","setup","memory","add","up","use","install","add agent","new project","SET","agent memory",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":40},"01M6GGSJ6HD2DFVZQTESJ81GYM","using-git-worktrees","When running long feature implementations, parallel branch work, or build\u002Ftest scripts that must not interfere with the user's active working directory. Creates isolated execution environments via git worktrees in sibling directories.","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112],"git worktrees","worktrees","git","using git worktrees","Using git","test","directory","execution","parallel","work","branch","directories","environments","with","via","long","scripts","feature","active","build",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":124,"publishedAt":40},"01M6GGSCFPK7MDSZH96XTNZR9B","test-engineer","When designing test strategy, analysing coverage, or writing tests outside the TDD cycle. Also use when working with CI pipelines or validating changes end-to-end.","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Ftest-engineer\u002FSKILL.md",[119],{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[125,126,98,127,128,129,130,131,132,80,133,106,134,135,136,137,138],"test engineer","engineer","tests","tdd cycle","cycle","end","test strategy","pipelines","tdd","strategy","ci","writing tests","writing","coverage",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":149,"publishedAt":40},"01M6GGS8YA9XZB6DWV22JC0YTB","test-driven-development","When implementing logic changes during develop-feature or implement-task. Use the Red-Green-Refactor cycle to write a failing test before any production code.","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[145,148],{"categoryNo":146,"categoryName":147,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},[150,151,98,152,37,153,110,154,155,129,156,80,157,158,159,160,161,162],"development","test driven development","driven","red","logic","green","red-green-refactor","write","develop","refactor","Production","code","implement",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":40},"01M6GGS61D41ZJG4D8XAS97H62","task-planner","When decomposing a feature or spec into implementable subtasks, estimating scope, or orchestrating multi-step work across subagents.","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Ftask-planner\u002FSKILL.md",[],[170,37,171,110,172,173,102,174,175,176],"task planner","planner","across","subagents","spec","scope","multi",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":40},"01M6GGS30NJW4Q7QN4KVT0CV08","systematic-debugger","When applying debugging techniques during any investigation — root cause tracing, bisect, defense-in-depth. Enforces hypothesis-first analysis and prohibits guess-and-check changes. Use standalone or inside the debug-issue workflow.","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Fsystematic-debugger\u002FSKILL.md",[],[184,185,186,187,188,189,190,191,80,192,193,194,195,196,197,198,199,200,201,27],"systematic debugger","systematic","debugger","check","standalone","root","issue workflow","issue","bisect","investigation","analysis","first","defense","hypothesis","defense-in-depth","tracing","debugging","debug"]