[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75A36BTZGRRJQTCSWKMHNN4":3,"skill-same:01M75A36BTZGRRJQTCSWKMHNN4":64},{"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},"01M75A36BTZGRRJQTCSWKMHNN4","specdev",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\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: specdev\ndescription: 从需求评估、原型、规格和实施，到代码审查、发版部署、环境维护与知识提纯的软件交付；也可直接处理其中一项工作。\n---\n\n# 软件开发与上线\n\n从用户当前要完成的结果开始，复用已有需求、代码、设计和授权。这里的 Work 是可独立调用的方法；按当前问题选择，不要求顺序走完、逐层交接或逐项生成文档。\n\n通常先理解需求并评估；体验不清楚时先做原型，再把确认的行为整理成 spec。内容或协作规模需要时才切片，随后实现、检查、交付与部署。小修复可直接实现，纯后端工作可跳过 UI。\n\n用户主要参与需求取舍和体验方向。只集中询问会改变目标、体验或重要风险且不能自行查明的问题；工程事实先查项目，已有明确决定直接沿用。\n\n## 按任务选择 Work\n\n| 当前任务 | 入口 |\n|---|---|\n| 了解工程、开发环境与验证入口 | [工程初始化](specdev-i-init-setup\u002FSKILL.md) |\n| 收集反馈、浏览待办、评估 issue 或 PR | [需求分诊](specdev-t-triage\u002FSKILL.md) |\n| 大需求边界尚不清楚，先调查可行路线 | [需求探索](specdev-w-wayfinder\u002FSKILL.md) |\n| 对已界定需求澄清产品和架构取舍 | [决策访谈](specdev-g-grill-with-docs\u002FSKILL.md) |\n| 学习代码、外部项目或技术机制 | [学习与图解](specdev-l-learn\u002FSKILL.md) |\n| 验证 UI、交互、规则或状态模型 | [原型设计](specdev-p-prototype\u002FSKILL.md) |\n| 将来源与设计整理成可实施的行为规格 | [编写 Spec](specdev-s-spec\u002FSKILL.md) |\n| 划分可独立验收的实施切片 | [拆分 Tickets](specdev-t-tickets\u002FSKILL.md) |\n| 规划、继续或调整一次较大交付 | [目标计划](specdev-p-goal-plan\u002FSKILL.md) |\n| 修改代码、文档或配置并完成验证 | [实施](specdev-i-implement\u002FSKILL.md) |\n| 复现、定位缺陷或调查一次性事件 | [故障诊断](specdev-d-diagnose-bugs\u002FSKILL.md) |\n| 审查指定文件、commit、区间或 PR | [代码审查](specdev-c-code-review\u002FSKILL.md) |\n| 评估结构维护成本、重构方案或性能 | [架构审查](specdev-r-review-architecture\u002FSKILL.md) |\n| 推送、PR、CI、Issue 回写或版本发布 | [开发交付](specdev-d-delivery\u002FSKILL.md) |\n| 准备发起部署所需的本机工具与环境记录 | [部署环境初始化](specdev-i-environment-setup\u002FSKILL.md) |\n| 接入一台指定服务器并确认部署位置 | [服务器接入](specdev-s-server-connect\u002FSKILL.md) |\n| 维护主机系统、容器运行时与共享入口 | [主机维护](specdev-h-host-manage\u002FSKILL.md) |\n| 将项目或共享服务部署、升级、迁移或回退 | [项目部署](specdev-d-project-deploy\u002FSKILL.md) |\n| 查看环境、服务器、项目与部署关系 | [资产盘点](specdev-v-inventory-view\u002FSKILL.md) |\n| 从开发过程提取具体改进 | [开发复盘](specdev-r-retro\u002FSKILL.md) |\n| 维护长期知识或结束交付并归档 | [提纯与归档](specdev-a-archive-and-consolidate\u002FSKILL.md) |\n\n只打开当前任务需要的入口及它指向的适用参考。用户已要求完整实施时，连续完成已授权工作；不因切换 Work 再问同一批准，也不把这些入口变成固定角色或调度器。\n\n## 一份可接续记录\n\n先使用用户指定的 issue、PR 或项目文档。需要跨会话推进版本交付时，默认在项目根下 `.agents\u002Fspeculo\u002F.speculo\u002Freleases\u002F\u003Cname>\u002FREADME.md` 记录来源、范围、关键决定、当前设计、实际结果与下一步。小改动现有 issue 或提交说明足够就不另建记录。\n\n规格与任务清单可以写在这份记录内；内容太大才拆出 spec 或票据，原记录只链接它们。每项事实保持一个主要维护位置，没有强制模板、字段、状态文件或独立交接报告。保存、恢复或提纯时参考 [持久化](..\u002F..\u002Freferences\u002Fmemory.md)。\n\n## 设计、完成与上线\n\n设计在项目长期位置维护，代码、HTML、组件示例、样式和图像均可作为依据。交付记录引用本次采用的固定版本；候选、已确认设计和当前实现要能分辨。\n\n涉及 UI 的实施和审查，比较同一页面、状态与必要视口。已确认的导航、区域组合和信息层级不能自行当作演示而丢弃；未获接受的结构偏差保持为未完成项。\n\n技术检查、用户验收、PR 合并、版本发布和目标环境上线分别按实际证据判断。任务明确要求的最终用户验收，只能由同一交付范围的真实反馈或明确延期决定满足；原型批准和发版许可不自动代替它。\n\n部署复用已核实的目标、项目现有发布方式和当前有效授权。完成后核对实际版本、服务健康与关键业务路径，按风险验证数据迁移和恢复；当前需求只到 PR 时，就交付可审阅 PR。\n\n中断后先核对现有记录、Git 与实际系统状态，再从未完成处继续。结束时报告成果入口、关键取舍、真实检查和剩余限制，并把仍有复用价值的决定、背景、故障经验或设计提纯到长期位置。\n","# 软件开发与上线\n\n从用户当前要完成的结果开始，复用已有需求、代码、设计和授权。这里的 Work 是可独立调用的方法；按当前问题选择，不要求顺序走完、逐层交接或逐项生成文档。\n\n通常先理解需求并评估；体验不清楚时先做原型，再把确认的行为整理成 spec。内容或协作规模需要时才切片，随后实现、检查、交付与部署。小修复可直接实现，纯后端工作可跳过 UI。\n\n用户主要参与需求取舍和体验方向。只集中询问会改变目标、体验或重要风险且不能自行查明的问题；工程事实先查项目，已有明确决定直接沿用。\n\n## 按任务选择 Work\n\n| 当前任务 | 入口 |\n|---|---|\n| 了解工程、开发环境与验证入口 | [工程初始化](specdev-i-init-setup\u002FSKILL.md) |\n| 收集反馈、浏览待办、评估 issue 或 PR | [需求分诊](specdev-t-triage\u002FSKILL.md) |\n| 大需求边界尚不清楚，先调查可行路线 | [需求探索](specdev-w-wayfinder\u002FSKILL.md) |\n| 对已界定需求澄清产品和架构取舍 | [决策访谈](specdev-g-grill-with-docs\u002FSKILL.md) |\n| 学习代码、外部项目或技术机制 | [学习与图解](specdev-l-learn\u002FSKILL.md) |\n| 验证 UI、交互、规则或状态模型 | [原型设计](specdev-p-prototype\u002FSKILL.md) |\n| 将来源与设计整理成可实施的行为规格 | [编写 Spec](specdev-s-spec\u002FSKILL.md) |\n| 划分可独立验收的实施切片 | [拆分 Tickets](specdev-t-tickets\u002FSKILL.md) |\n| 规划、继续或调整一次较大交付 | [目标计划](specdev-p-goal-plan\u002FSKILL.md) |\n| 修改代码、文档或配置并完成验证 | [实施](specdev-i-implement\u002FSKILL.md) |\n| 复现、定位缺陷或调查一次性事件 | [故障诊断](specdev-d-diagnose-bugs\u002FSKILL.md) |\n| 审查指定文件、commit、区间或 PR | [代码审查](specdev-c-code-review\u002FSKILL.md) |\n| 评估结构维护成本、重构方案或性能 | [架构审查](specdev-r-review-architecture\u002FSKILL.md) |\n| 推送、PR、CI、Issue 回写或版本发布 | [开发交付](specdev-d-delivery\u002FSKILL.md) |\n| 准备发起部署所需的本机工具与环境记录 | [部署环境初始化](specdev-i-environment-setup\u002FSKILL.md) |\n| 接入一台指定服务器并确认部署位置 | [服务器接入](specdev-s-server-connect\u002FSKILL.md) |\n| 维护主机系统、容器运行时与共享入口 | [主机维护](specdev-h-host-manage\u002FSKILL.md) |\n| 将项目或共享服务部署、升级、迁移或回退 | [项目部署](specdev-d-project-deploy\u002FSKILL.md) |\n| 查看环境、服务器、项目与部署关系 | [资产盘点](specdev-v-inventory-view\u002FSKILL.md) |\n| 从开发过程提取具体改进 | [开发复盘](specdev-r-retro\u002FSKILL.md) |\n| 维护长期知识或结束交付并归档 | [提纯与归档](specdev-a-archive-and-consolidate\u002FSKILL.md) |\n\n只打开当前任务需要的入口及它指向的适用参考。用户已要求完整实施时，连续完成已授权工作；不因切换 Work 再问同一批准，也不把这些入口变成固定角色或调度器。\n\n## 一份可接续记录\n\n先使用用户指定的 issue、PR 或项目文档。需要跨会话推进版本交付时，默认在项目根下 `.agents\u002Fspeculo\u002F.speculo\u002Freleases\u002F\u003Cname>\u002FREADME.md` 记录来源、范围、关键决定、当前设计、实际结果与下一步。小改动现有 issue 或提交说明足够就不另建记录。\n\n规格与任务清单可以写在这份记录内；内容太大才拆出 spec 或票据，原记录只链接它们。每项事实保持一个主要维护位置，没有强制模板、字段、状态文件或独立交接报告。保存、恢复或提纯时参考 [持久化](..\u002F..\u002Freferences\u002Fmemory.md)。\n\n## 设计、完成与上线\n\n设计在项目长期位置维护，代码、HTML、组件示例、样式和图像均可作为依据。交付记录引用本次采用的固定版本；候选、已确认设计和当前实现要能分辨。\n\n涉及 UI 的实施和审查，比较同一页面、状态与必要视口。已确认的导航、区域组合和信息层级不能自行当作演示而丢弃；未获接受的结构偏差保持为未完成项。\n\n技术检查、用户验收、PR 合并、版本发布和目标环境上线分别按实际证据判断。任务明确要求的最终用户验收，只能由同一交付范围的真实反馈或明确延期决定满足；原型批准和发版许可不自动代替它。\n\n部署复用已核实的目标、项目现有发布方式和当前有效授权。完成后核对实际版本、服务健康与关键业务路径，按风险验证数据迁移和恢复；当前需求只到 PR 时，就交付可审阅 PR。\n\n中断后先核对现有记录、Git 与实际系统状态，再从未完成处继续。结束时报告成果入口、关键取舍、真实检查和剩余限制，并把仍有复用价值的决定、背景、故障经验或设计提纯到长期位置。\n",{"name":5,"description":7},"main","994a64427a6784053dd092a86713870062cfde2f","template\u002Fworkflows\u002Fspecdev",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",{"tool":38,"command":39},"bunx","bunx skills add NAMEWTA\u002FSpeculo --skill specdev",{"tool":41,"command":42},"pnpm","pnpm dlx skills add NAMEWTA\u002FSpeculo --skill specdev","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002FSKILL.md",true,[46,52,56,60],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fdelivery.md","REFERENCE","参考文档",2702,"https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Freferences\u002Fdelivery.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Foperations.md",3005,"https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Freferences\u002Foperations.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Freliability.md",2556,"https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Freferences\u002Freliability.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fresearch-and-modeling.md",2089,"https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Freferences\u002Fresearch-and-modeling.md",[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M75A4XGMYZF33V25QB3V90PH","specdev-w-wayfinder","当大型需求的边界、可行路线或子问题尚不清楚时进行目标导向探索，形成可实施范围与关键证据。","https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Fspecdev-w-wayfinder\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":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":19},"01M75A4QJMZRASXGFFVKR3WKKK","specdev-t-tickets","把清晰规格拆成可独立实施和验收的切片，保留真实依赖与协作边界。","https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Fspecdev-t-tickets\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M75A4P07CWM6VSCS0BM5SD69","specdev-s-spec","综合需求、已确认设计、代码事实与关键决定，形成可实施、可验证的行为规格。","https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Fspecdev-s-spec\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M75A4K8JZNS6HBXMHBP2MTQY","specdev-s-server-connect","接入指定本地或远程服务器，核实身份、账号、权限与部署根，保存可复用连接信息。","https:\u002F\u002Fgithub.com\u002FNAMEWTA\u002FSpeculo\u002Fblob\u002Fmain\u002Ftemplate\u002Fworkflows\u002Fspecdev\u002Fspecdev-s-server-connect\u002FSKILL.md",[],[]]