[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75A4P07CWM6VSCS0BM5SD69":3,"skill-same:01M75A4P07CWM6VSCS0BM5SD69":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},"01M75A4P07CWM6VSCS0BM5SD69","specdev-s-spec",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-s-spec\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: specdev-s-spec\ndescription: 综合需求、已确认设计、代码事实与关键决定，形成可实施、可验证的行为规格。\n---\n\n# 编写规格\n\n规格串联已经讨论过的来源与设计，让实施者知道应交付什么及如何验证。先读取现有需求、用户决定、相关代码与测试；缺少与本次无关的工件不构成阻塞。\n\n## 明确行为与范围\n\n解释谁遇到什么问题、当前行为是什么、本次改变什么，以及哪些事项暂缓。对主要场景写出触发条件、可观察行为和结果；接口、数据结构、权限、兼容性及性能等内容只在实际影响交付时展开。\n\n对于 UI，将每项行为要求连接到本次确认的原型版本、页面与状态，并保留对应 HTML\u002F组件锚点、CSS token\u002F选择器\u002F媒体查询、JS 事件与状态转换等适用的源码定位，按 [原型证据引用](..\u002Fspecdev-p-prototype\u002Freferences\u002Fdesign-evidence.md) 组织。只有原型首页或 DESIGN 文档入口不足以定位具体行为。\n\n已有 DESIGN 时引用对应章节及其原型证据；编写设计说明时，各节就近指明所依据的源码，文字补充目的与取舍，不能覆盖已确认的 UI、样式和交互。原型已表达清楚的内容直接引用，不再复制成 change 内 DESIGN。尚无原型证据的要求标明缺口或设计决定，不写成已验证事实；纯后端不要求 UI 资料。\n\n工程细节保持可调整空间。确实要固定的接口或约束说明理由；不要锁定无必要的逐文件实现步骤。新设计取舍超出已有共识时聚焦解决，广泛未决问题使用 [决策访谈](..\u002Fspecdev-g-grill-with-docs\u002FSKILL.md)。\n\n## 让完成条件可以判断\n\n为重要结果找实际验证入口，例如产品页面、公共 API\u002FCLI、集成事件或稳定单元接缝。说明怎样触发、应观察到什么，沿用项目已有测试和检查方式；不为了形式把每条要求都编号或规定测试层级。\n\n涉及写入或异步工作时，说明失败、部分成功、超时未知、重试、取消和恢复对用户可见的含义。接口或持久化变化明确兼容、迁移和恢复限制。只有实际需要时才展开 [可靠性与验证](..\u002Freferences\u002Freliability.md)。\n\n区分已确认事实、可逆假设和阻塞决定。高影响缺口不能藏在笼统“按最佳实践处理”中；局部默认值可明确说明并在实现中验证。\n\n## 一个权威位置\n\n通常把规格放在 release 记录内。用户明确需要独立 spec、篇幅较大或多人引用更方便时拆成 `spec.md`，原记录改为链接，避免双份规范。\n\n规格至少足以解释目标、范围、关键行为、重要约束与实际完成条件；按内容组织，不使用强制模板或 JSON schema。来源、设计和重要决定能回读即可。\n\n范围清楚且已有实施请求时直接进入 [实施](..\u002Fspecdev-i-implement\u002FSKILL.md)。只有任务规模或协作需要才 [拆票](..\u002Fspecdev-t-tickets\u002FSKILL.md)；交付目标复杂时可使用 [目标计划](..\u002Fspecdev-p-goal-plan\u002FSKILL.md)。\n","# 编写规格\n\n规格串联已经讨论过的来源与设计，让实施者知道应交付什么及如何验证。先读取现有需求、用户决定、相关代码与测试；缺少与本次无关的工件不构成阻塞。\n\n## 明确行为与范围\n\n解释谁遇到什么问题、当前行为是什么、本次改变什么，以及哪些事项暂缓。对主要场景写出触发条件、可观察行为和结果；接口、数据结构、权限、兼容性及性能等内容只在实际影响交付时展开。\n\n对于 UI，将每项行为要求连接到本次确认的原型版本、页面与状态，并保留对应 HTML\u002F组件锚点、CSS token\u002F选择器\u002F媒体查询、JS 事件与状态转换等适用的源码定位，按 [原型证据引用](..\u002Fspecdev-p-prototype\u002Freferences\u002Fdesign-evidence.md) 组织。只有原型首页或 DESIGN 文档入口不足以定位具体行为。\n\n已有 DESIGN 时引用对应章节及其原型证据；编写设计说明时，各节就近指明所依据的源码，文字补充目的与取舍，不能覆盖已确认的 UI、样式和交互。原型已表达清楚的内容直接引用，不再复制成 change 内 DESIGN。尚无原型证据的要求标明缺口或设计决定，不写成已验证事实；纯后端不要求 UI 资料。\n\n工程细节保持可调整空间。确实要固定的接口或约束说明理由；不要锁定无必要的逐文件实现步骤。新设计取舍超出已有共识时聚焦解决，广泛未决问题使用 [决策访谈](..\u002Fspecdev-g-grill-with-docs\u002FSKILL.md)。\n\n## 让完成条件可以判断\n\n为重要结果找实际验证入口，例如产品页面、公共 API\u002FCLI、集成事件或稳定单元接缝。说明怎样触发、应观察到什么，沿用项目已有测试和检查方式；不为了形式把每条要求都编号或规定测试层级。\n\n涉及写入或异步工作时，说明失败、部分成功、超时未知、重试、取消和恢复对用户可见的含义。接口或持久化变化明确兼容、迁移和恢复限制。只有实际需要时才展开 [可靠性与验证](..\u002Freferences\u002Freliability.md)。\n\n区分已确认事实、可逆假设和阻塞决定。高影响缺口不能藏在笼统“按最佳实践处理”中；局部默认值可明确说明并在实现中验证。\n\n## 一个权威位置\n\n通常把规格放在 release 记录内。用户明确需要独立 spec、篇幅较大或多人引用更方便时拆成 `spec.md`，原记录改为链接，避免双份规范。\n\n规格至少足以解释目标、范围、关键行为、重要约束与实际完成条件；按内容组织，不使用强制模板或 JSON schema。来源、设计和重要决定能回读即可。\n\n范围清楚且已有实施请求时直接进入 [实施](..\u002Fspecdev-i-implement\u002FSKILL.md)。只有任务规模或协作需要才 [拆票](..\u002Fspecdev-t-tickets\u002FSKILL.md)；交付目标复杂时可使用 [目标计划](..\u002Fspecdev-p-goal-plan\u002FSKILL.md)。\n",{"name":5,"description":7},"main","994a64427a6784053dd092a86713870062cfde2f","template\u002Fworkflows\u002Fspecdev\u002Fspecdev-s-spec",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-s-spec",{"tool":38,"command":39},"bunx","bunx skills add NAMEWTA\u002FSpeculo --skill specdev-s-spec",{"tool":41,"command":42},"pnpm","pnpm dlx skills add NAMEWTA\u002FSpeculo --skill specdev-s-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Fspecdev-s-spec\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},"01M75A4QJMZRASXGFFVKR3WKKK","specdev-t-tickets","把清晰规格拆成可独立实施和验收的切片，保留真实依赖与协作边界。","https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Fspecdev-t-tickets\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",[],[]]