[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AMPASP7Q1C8E2AE1TJJZ4":3,"skill-same:01M71AMPASP7Q1C8E2AE1TJJZ4":65},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M71AMPASP7Q1C8E2AE1TJJZ4","technical-plan-guard",null,"Use this skill when the user introduces a new requirement, feature request, scope change, or implementation direction for this repository. Before coding, create a technical plan in docs using the required naming convention docs\u002Ftech-plan-\u003Ctopic>-\u003CYYYYMMDD>-session-\u003Csession-id>.md, then align the implementation to that plan.","xigua-wang\u002Fskill-doctor","xigua-wang","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F66240400?v=4","01M71AMMSA5F86M0GPPR71F3T1","xiguawang","01M71AMMSY5ZBYP9CN9GDD98MT",272,"MIT","https:\u002F\u002Fgithub.com\u002Fxigua-wang\u002Fskill-doctor\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftechnical-plan-guard\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"technical","guard","plan","technical plan","technical plan guard","request","naming","change","create","id","when","use","new","session","align","for","scope","direction","feature","tech","2026-11-10 10:12:30",false,"---\nname: technical-plan-guard\ndescription: Use this skill when the user introduces a new requirement, feature request, scope change, or implementation direction for this repository. Before coding, create a technical plan in docs using the required naming convention docs\u002Ftech-plan-\u003Ctopic>-\u003CYYYYMMDD>-session-\u003Csession-id>.md, then align the implementation to that plan.\n---\n\n# Technical Plan Guard\n\nFor this repository, any new requirement should start with a technical plan document under `docs\u002F` before implementation work begins.\n\n## When to use\n\nUse this skill when the user:\n\n- asks to add a new feature or workflow\n- changes product or technical direction\n- requests a non-trivial refactor\n- asks for a new skill, rule, or repository convention\n\nSkip this skill only for:\n\n- typo or wording fixes\n- trivial one-line bug fixes\n- purely exploratory questions with no requested change\n\n## Required output\n\nCreate a technical plan file in `docs\u002F` with this filename pattern:\n\n`docs\u002Ftech-plan-\u003Ctopic>-\u003CYYYYMMDD>-session-\u003Csession-id>.md`\n\nRules:\n\n- use lowercase kebab-case for `\u003Ctopic>`\n- keep `\u003Ctopic>` short and specific, usually 2 to 6 words\n- use the current local date in `YYYYMMDD`\n- keep the literal segment `session`\n- use a short session identifier in `\u003Csession-id>`, such as `001`, `alpha`, or `new-skill`\n\nExample:\n\n`docs\u002Ftech-plan-new-skill-doc-rule-20260417-session-001.md`\n\n## Working procedure\n\n1. Infer a concise topic from the request.\n2. Pick a session id that distinguishes the planning round.\n3. Create the new plan file from `docs\u002Ftechnical-plan-template.md` if available.\n4. Fill in scope, constraints, implementation steps, risks, and validation.\n5. Only then proceed with code or content changes needed by the request.\n\n## Plan content\n\nThe plan should cover:\n\n- background\n- goal and non-goals\n- proposed approach\n- file or module impact\n- risks and tradeoffs\n- validation steps\n\nIf the repository already contains a broader strategy document such as `docs\u002Ftechnical-plan.md`, treat it as context, not as the per-request plan file.\n","# Technical Plan Guard\n\nFor this repository, any new requirement should start with a technical plan document under `docs\u002F` before implementation work begins.\n\n## When to use\n\nUse this skill when the user:\n\n- asks to add a new feature or workflow\n- changes product or technical direction\n- requests a non-trivial refactor\n- asks for a new skill, rule, or repository convention\n\nSkip this skill only for:\n\n- typo or wording fixes\n- trivial one-line bug fixes\n- purely exploratory questions with no requested change\n\n## Required output\n\nCreate a technical plan file in `docs\u002F` with this filename pattern:\n\n`docs\u002Ftech-plan-\u003Ctopic>-\u003CYYYYMMDD>-session-\u003Csession-id>.md`\n\nRules:\n\n- use lowercase kebab-case for `\u003Ctopic>`\n- keep `\u003Ctopic>` short and specific, usually 2 to 6 words\n- use the current local date in `YYYYMMDD`\n- keep the literal segment `session`\n- use a short session identifier in `\u003Csession-id>`, such as `001`, `alpha`, or `new-skill`\n\nExample:\n\n`docs\u002Ftech-plan-new-skill-doc-rule-20260417-session-001.md`\n\n## Working procedure\n\n1. Infer a concise topic from the request.\n2. Pick a session id that distinguishes the planning round.\n3. Create the new plan file from `docs\u002Ftechnical-plan-template.md` if available.\n4. Fill in scope, constraints, implementation steps, risks, and validation.\n5. Only then proceed with code or content changes needed by the request.\n\n## Plan content\n\nThe plan should cover:\n\n- background\n- goal and non-goals\n- proposed approach\n- file or module impact\n- risks and tradeoffs\n- validation steps\n\nIf the repository already contains a broader strategy document such as `docs\u002Ftechnical-plan.md`, treat it as context, not as the per-request plan file.\n",{"name":5,"description":7},"main","ccff2fa78f80e78b947ff692cd54e4d3826b6089",".codex\u002Fskills\u002Ftechnical-plan-guard",2,"https:\u002F\u002Fgithub.com\u002Fxigua-wang\u002Fskill-doctor","https:\u002F\u002Fgithub.com\u002Fxigua-wang","2026-04-22 20:35:26",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add xigua-wang\u002Fskill-doctor --skill technical-plan-guard",{"tool":57,"command":58},"bunx","bunx skills add xigua-wang\u002Fskill-doctor --skill technical-plan-guard",{"tool":60,"command":61},"pnpm","pnpm dlx skills add xigua-wang\u002Fskill-doctor --skill technical-plan-guard","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fxigua-wang\u002Fskill-doctor\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftechnical-plan-guard\u002FSKILL.md",true,[],[66,77,96,112,126,136],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":39},"01M71AN7JVJMM779NWTXVAM9N5","Release Guard","OpenClaw workspace-level release guard that should win over lower-precedence copies.","https:\u002F\u002Fgithub.com\u002Fxigua-wang\u002Fskill-doctor\u002Fblob\u002Fmain\u002Fexamples\u002Fdemo-workspace\u002Fskills\u002Frelease-guard\u002FSKILL.md",[],[20,68,73,74,75,76],"release","openclaw workspace","openclaw","workspace",{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":88,"publishedAt":39},"01M71AN660YMCKTP57GCTZHWR3","Workflow Surgeon","Repairs broken GitHub workflow behavior and action sequencing.","https:\u002F\u002Fgithub.com\u002Fxigua-wang\u002Fskill-doctor\u002Fblob\u002Fmain\u002Fexamples\u002Fdemo-workspace\u002F.github\u002Fskills\u002Fworkflow-surgeon\u002FSKILL.md",[83],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[79,89,90,91,92,93,94,95],"workflow","sequencing","action","broken","github","github workflow","behavior",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":39},"01M71AN54M0646ZEDQEMC5Z2VP","Doc Gateway","Indexes project docs and links contributors to the right workflow notes.","https:\u002F\u002Fgithub.com\u002Fxigua-wang\u002Fskill-doctor\u002Fblob\u002Fmain\u002Fexamples\u002Fdemo-workspace\u002F.copilot\u002Fskills\u002Fdoc-gateway\u002FSKILL.md",[],[98,103,104,105,106,107,108,109,110,111,89],"doc","gateway","project docs","indexes","project","contributors","notes","links","docs",{"skillNo":113,"name":68,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":39},"01M71AN3H5DV3TGW4FKJW0FY1N","Reviews release automation and handles deploy prep with strict safety rails.","https:\u002F\u002Fgithub.com\u002Fxigua-wang\u002Fskill-doctor\u002Fblob\u002Fmain\u002Fexamples\u002Fdemo-workspace\u002F.codex\u002Fskills\u002Frelease-guard\u002FSKILL.md",[],[20,68,73,118,119,120,121,122,123,124,125],"rails","with","Safety","reviews","release automation","prep","deploy","automation",{"skillNo":127,"name":68,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":39},"01M71AN24DG4H9BZFPT3NHN0Y2","A second release guard variant used to validate override detection.","https:\u002F\u002Fgithub.com\u002Fxigua-wang\u002Fskill-doctor\u002Fblob\u002Fmain\u002Fexamples\u002Fdemo-workspace\u002F.codex\u002Fskills\u002Frelease-guard-v2\u002FSKILL.md",[],[73,68,20,132,133,134,135],"second","detection","validate","variant",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":145,"publishedAt":39},"01M71AN12WK2XZXBA1BPBSPAVQ","Deploy Router","Routes deploy requests and environment-specific handoffs.","https:\u002F\u002Fgithub.com\u002Fxigua-wang\u002Fskill-doctor\u002Fblob\u002Fmain\u002Fexamples\u002Fdemo-workspace\u002F.codex\u002Fskills\u002Fdeploy-router\u002FSKILL.md",[142],{"categoryNo":143,"categoryName":144,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000011","运维与部署",[124,146,138,147,148],"router","environment","requests"]