[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75A4QJMZRASXGFFVKR3WKKK":3,"skill-same:01M75A4QJMZRASXGFFVKR3WKKK":46},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M75A4QJMZRASXGFFVKR3WKKK","specdev-t-tickets",null,"把清晰规格拆成可独立实施和验收的切片，保留真实依赖与协作边界。","NAMEWTA\u002FSpeculo","NAMEWTA","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F67400687?v=4","01M759ZZGH866DH8PWNX7NVE4T","Anner","01M759ZZH780N5CQRBCQEMYKAF",2,"MIT","https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Fspecdev-t-tickets\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: specdev-t-tickets\ndescription: 把清晰规格拆成可独立实施和验收的切片，保留真实依赖与协作边界。\n---\n\n# 实施切片与 Tickets\n\n先判断是否需要独立票据。一次可完成的改动在现有记录中列小清单即可；用户要求拆票、内容过大或协作需要时，再创建可独立阅读的 Ticket。\n\n## 从行为切分\n\n读取规格、采用的设计版本、关键接口与现有测试，按可验证的用户结果拆分。优先让一块工作贯穿所需界面、服务、数据和检查，不按“先所有后端、再所有前端”机械切割。\n\n准备性重构只有确实降低实施风险时单列，并明确它支撑哪个结果。数据或公共接口迁移可按扩展、迁移、收缩安排必要顺序；不是所有任务都需要这三阶段。\n\n每块说明目标、相关背景与来源、预计修改范围、完成条件和真实依赖。涉及 UI 时保留同一已确认版本中负责页面\u002F状态的 [原型证据引用](..\u002Fspecdev-p-prototype\u002Freferences\u002Fdesign-evidence.md)，包括适用的结构、样式与交互源码定位；引用 DESIGN 时保留相关章节及其直接源码链接，不把它们压缩成一句视觉描述。涉及数据时说明迁移与恢复责任。只有确实需要的技术约束写入票中，不复制全项目规范。\n\n## 支持独立协作\n\n检查是否存在未覆盖的规格、重复责任、循环依赖和共享修改点。接口两端、数据模型、配置、生产调用方与文档的变化应有明确承接；可并行的判断来自这些事实。\n\n准备独立上下文时，提供足够的来源路径、当前事实、预期结果与验证入口。无需固定 TASK\u002FREPORT、角色名称、执行工具或每票创建工作区。\n\n用户指定交付数量或拆分粒度时保留；确有冲突说明原因，不静默少交付。新的未知会改变产品行为时先澄清，局部工程细节可留给实施者。\n\n## 交付与继续\n\n用现有 release 记录维护简短顺序与链接，各票只负责自己的细节；状态和结果尽量写在原条目，避免 Map、Goal 与 Evidence 多处同步。\n\n展示每块带来的结果、依赖与风险。已有完整实施请求时直接接续 [实施](..\u002Fspecdev-i-implement\u002FSKILL.md)；只要求规划时返回可用票据。整体验收仍检查原规格和跨块集成，不能由所有票“完成”自动推导。\n","# 实施切片与 Tickets\n\n先判断是否需要独立票据。一次可完成的改动在现有记录中列小清单即可；用户要求拆票、内容过大或协作需要时，再创建可独立阅读的 Ticket。\n\n## 从行为切分\n\n读取规格、采用的设计版本、关键接口与现有测试，按可验证的用户结果拆分。优先让一块工作贯穿所需界面、服务、数据和检查，不按“先所有后端、再所有前端”机械切割。\n\n准备性重构只有确实降低实施风险时单列，并明确它支撑哪个结果。数据或公共接口迁移可按扩展、迁移、收缩安排必要顺序；不是所有任务都需要这三阶段。\n\n每块说明目标、相关背景与来源、预计修改范围、完成条件和真实依赖。涉及 UI 时保留同一已确认版本中负责页面\u002F状态的 [原型证据引用](..\u002Fspecdev-p-prototype\u002Freferences\u002Fdesign-evidence.md)，包括适用的结构、样式与交互源码定位；引用 DESIGN 时保留相关章节及其直接源码链接，不把它们压缩成一句视觉描述。涉及数据时说明迁移与恢复责任。只有确实需要的技术约束写入票中，不复制全项目规范。\n\n## 支持独立协作\n\n检查是否存在未覆盖的规格、重复责任、循环依赖和共享修改点。接口两端、数据模型、配置、生产调用方与文档的变化应有明确承接；可并行的判断来自这些事实。\n\n准备独立上下文时，提供足够的来源路径、当前事实、预期结果与验证入口。无需固定 TASK\u002FREPORT、角色名称、执行工具或每票创建工作区。\n\n用户指定交付数量或拆分粒度时保留；确有冲突说明原因，不静默少交付。新的未知会改变产品行为时先澄清，局部工程细节可留给实施者。\n\n## 交付与继续\n\n用现有 release 记录维护简短顺序与链接，各票只负责自己的细节；状态和结果尽量写在原条目，避免 Map、Goal 与 Evidence 多处同步。\n\n展示每块带来的结果、依赖与风险。已有完整实施请求时直接接续 [实施](..\u002Fspecdev-i-implement\u002FSKILL.md)；只要求规划时返回可用票据。整体验收仍检查原规格和跨块集成，不能由所有票“完成”自动推导。\n",{"name":5,"description":7},"main","994a64427a6784053dd092a86713870062cfde2f","template\u002Fworkflows\u002Fspecdev\u002Fspecdev-t-tickets",0,"https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo","https:\u002F\u002Fgithub.com\u002FNAMEWTA","I am a tech enthusiast.","2026-11-13 22:04:53",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add NAMEWTA\u002FSpeculo --skill specdev-t-tickets",{"tool":38,"command":39},"bunx","bunx skills add NAMEWTA\u002FSpeculo --skill specdev-t-tickets",{"tool":41,"command":42},"pnpm","pnpm dlx skills add NAMEWTA\u002FSpeculo --skill specdev-t-tickets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Fspecdev-t-tickets\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M75A4XGMYZF33V25QB3V90PH","specdev-w-wayfinder","当大型需求的边界、可行路线或子问题尚不清楚时进行目标导向探索，形成可实施范围与关键证据。","https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Fspecdev-w-wayfinder\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M75A4V5MTVPJH83B1CZ2HB07","specdev-v-inventory-view","查看服务器、项目、共享服务和部署版本的对应关系，区分已有配置、最新观测与未知状态。","https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Fspecdev-v-inventory-view\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M75A4SM63M24HRDTN1V4G5NV","specdev-t-triage","收集多渠道需求、浏览待办并评估 issue、PR 或本地请求，形成有依据的优先级和可继续实施的简报。","https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Fspecdev-t-triage\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M75A4P07CWM6VSCS0BM5SD69","specdev-s-spec","综合需求、已确认设计、代码事实与关键决定，形成可实施、可验证的行为规格。","https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Fspecdev-s-spec\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M75A4K8JZNS6HBXMHBP2MTQY","specdev-s-server-connect","接入指定本地或远程服务器，核实身份、账号、权限与部署根，保存可复用连接信息。","https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Fspecdev-s-server-connect\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M75A4HCX8MKWXES43FQJY7P0","specdev-r-review-architecture","评估代码结构与维护成本、深入选定重构方案，或测量真实用户操作的性能并给出有依据的改进。","https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Fspecdev-r-review-architecture\u002FSKILL.md",[],[]]