[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76P4VMFP4ZAV7QVJ5QNHG8R":3,"skill-same:01M76P4VMFP4ZAV7QVJ5QNHG8R":104},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M76P4VMFP4ZAV7QVJ5QNHG8R","speclite-implementation-readiness-check",null,"执行 SpecLite Check Implementation Readiness workflow，验证 PRD、UX、Architecture 与 Epics 是否可进入实现。用于用户要求 check implementation readiness、readiness gate、实施就绪检查或运行 IR。核心能力：配置驱动激活、读取规划产物、按步骤审计、输出 readiness 报告。","flanliulf\u002FSpecLite","flanliulf","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3830171?v=4","01M752MYG3GGEADW105E2F6154","Fancy Liu","01M752MYGXQ0R06TYQG3BVVABS",4,"MIT","https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-implementation-readiness-check\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: speclite-implementation-readiness-check\ndescription: \"执行 SpecLite Check Implementation Readiness workflow，验证 PRD、UX、Architecture 与 Epics 是否可进入实现。用于用户要求 check implementation readiness、readiness gate、实施就绪检查或运行 IR。核心能力：配置驱动激活、读取规划产物、按步骤审计、输出 readiness 报告。\"\nallowed-tools: Read, Write, Bash, Grep, Glob, WebSearch\nmetadata:\n  version: \"1.0.0\"\n  author: \"fancyliu\"\n  catalog: \"speclite\"\n---\n\n[技能说明]\n    Check Implementation Readiness 是 Speclite 方案与架构准备工作流 Skill，用于在目标项目中按配置语言、输出语言和工作流步骤完成对应制品或交付动作。\n\n    源入口说明：Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says \"check implementation readiness\".\n\n[核心能力]\n    - **UX 单一路径发现**：通过 Planning root resolver evidence 优先消费 `{planning_artifacts}\u002Fux\u002Fux-design-specification.md`，仅在其缺失时只读消费 exact legacy fallback，并记录 `resolvedRoot`、`resolutionMode`、`actualConsumedPath`。\n    - **Whole\u002Fsharded 单一发现契约**：PRD、Epics、Architecture 只通过 `speclite resolve artifact-documents` 的 `consumedPaths` 消费；block 必须保持 zero artifact write 与 zero progress mutation，selection 只作用于当前 invocation。\n    - **Readiness 输出与历史发现**：新报告固定写入 `{solutioning_artifacts}\u002Fimplementation-readiness-report\u002Fgrill-consistency\u002Fimplementation-readiness-report-{yyyy-MM-dd}.md`；既有 Planning root readiness reports 与 `{planning_artifacts}\u002Fir-grill\u002F` 仅作为历史 evidence 原位发现，不迁移、重命名或删除。\n    - **Speclite 激活解析**：解析三层 customize（base→team→user）、`workflow.persistent_facts` 和 `workflow.on_complete`，并通过 `speclite resolve config --project-root {project-root}` 加载 merged runtime config。\n    - **源制品发现与上下文加载**：按 workflow 规约读取项目制品、配置字段、历史上下文和必要数据文件，保持源流程的输入发现语义。\n    - **步骤化工作流执行**：按 `references\u002Fworkflow-details.md` 与拆分后的 reference\u002Fstep 文件逐步执行，遵守顺序、HALT 条件、菜单等待和状态推进规则。\n    - **模板化输出生成**：使用 assets 中的模板或示例骨架生成文档、报告、规格或交付产物，输出语言服从 `document_output_language`。\n    - **质量校验与交接**：执行清单、报告、状态同步或 completion handoff，并在退出前解析和执行 `workflow.on_complete`。\n    - **迁移一致性约束**：当前运行规约只依赖 Speclite runtime，不读取旧运行目录、旧配置文件或旧命令命名空间。\n\n[约定]\n    裸路径相对于 `{skill-root}` 解析；`{project-root}` 是目标项目工作目录；`{speclite-runtime-root}` 是 `{project-root}\u002F_speclite`；`{skill-name}` 是目录 basename。\n\n[激活流程]\n    触发后先解析 `workflow`，执行 `activation_steps_prepend`，加载 `persistent_facts`，运行 `speclite resolve config --project-root {project-root}`，按 `communication_language` 与用户沟通，并执行 `activation_steps_append`。配置文件缺失或关键字段为空时必须 HALT；`config.toml.example` 只说明字段结构，不作为 runtime fallback。\n\n    customization 必须通过 `speclite resolve customization --skill {skill-root} --project-root {project-root}` 读取 merged JSON；`workflow.on_complete` 使用 `speclite resolve customization --skill {skill-root} --project-root {project-root} --key workflow.on_complete` 解析。默认 activation 不手写 TOML merge，不使用 `--human` 作为 machine input。\n\n[执行流程]\n    1. 先完整阅读 `references\u002Fworkflow-details.md`；该文件是从源入口转换后的权威工作流规约。随后按需读取 `references\u002Fworkflow-details.md`、`references\u002Fsteps\u002Fstep-01-document-discovery.md`、`references\u002Fsteps\u002Fstep-02-prd-analysis.md`、`references\u002Fsteps\u002Fstep-03-epic-coverage-validation.md`、`references\u002Fsteps\u002Fstep-04-ux-alignment.md`、`references\u002Fsteps\u002Fstep-05-epic-quality-review.md` 等 reference 文件。\n    2. 执行工作流前，确认 `{skill-root}`、`{project-root}`、`{speclite-runtime-root}`、`{skill-name}` 四个路径变量均已明确。\n    3. 若 workflow 指向 step 文件，必须一次只读取当前 step，完整执行后再进入下一步；遇到菜单或用户确认点时 HALT 等待。\n    4. 生成或更新产物时，按源 workflow 的模板、清单、状态字段和输出位置要求执行，不得因为迁移而改变核心需求。\n    5. 收尾前运行 checklist 或质量检查，解析 `workflow.on_complete`，并在输出文档末尾追加本 Skill 的生成标注。\n\n[注意事项]\n    - 名称、目录与 YAML `name` 字段保持 kebab-case 一致：`speclite-implementation-readiness-check`。\n    - `references\u002Fworkflow-details.md` 和配套 reference 文件均为有效执行规约，不是背景资料。\n    - 模板或示例骨架位于 `assets\u002Freadiness-report-template.md`。\n    - 如工作流需要项目配置，必须读取目标项目运行时配置。\n    - `config.toml.example` 仅作字段结构参考，不作为 runtime fallback。\n    - 当前运行规约不得依赖旧运行目录、旧 YAML 配置或旧命令命名空间。\n    - 输出文档末尾必须追加 `*本文档由 speclite-implementation-readiness-check Skill 自动生成*` 标注。\n\n[生成信息]\n    本 Skill 由 speclite-skill-creator 自动生成。\n","[技能说明]\n    Check Implementation Readiness 是 Speclite 方案与架构准备工作流 Skill，用于在目标项目中按配置语言、输出语言和工作流步骤完成对应制品或交付动作。\n\n    源入口说明：Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says \"check implementation readiness\".\n\n[核心能力]\n    - **UX 单一路径发现**：通过 Planning root resolver evidence 优先消费 `{planning_artifacts}\u002Fux\u002Fux-design-specification.md`，仅在其缺失时只读消费 exact legacy fallback，并记录 `resolvedRoot`、`resolutionMode`、`actualConsumedPath`。\n    - **Whole\u002Fsharded 单一发现契约**：PRD、Epics、Architecture 只通过 `speclite resolve artifact-documents` 的 `consumedPaths` 消费；block 必须保持 zero artifact write 与 zero progress mutation，selection 只作用于当前 invocation。\n    - **Readiness 输出与历史发现**：新报告固定写入 `{solutioning_artifacts}\u002Fimplementation-readiness-report\u002Fgrill-consistency\u002Fimplementation-readiness-report-{yyyy-MM-dd}.md`；既有 Planning root readiness reports 与 `{planning_artifacts}\u002Fir-grill\u002F` 仅作为历史 evidence 原位发现，不迁移、重命名或删除。\n    - **Speclite 激活解析**：解析三层 customize（base→team→user）、`workflow.persistent_facts` 和 `workflow.on_complete`，并通过 `speclite resolve config --project-root {project-root}` 加载 merged runtime config。\n    - **源制品发现与上下文加载**：按 workflow 规约读取项目制品、配置字段、历史上下文和必要数据文件，保持源流程的输入发现语义。\n    - **步骤化工作流执行**：按 `references\u002Fworkflow-details.md` 与拆分后的 reference\u002Fstep 文件逐步执行，遵守顺序、HALT 条件、菜单等待和状态推进规则。\n    - **模板化输出生成**：使用 assets 中的模板或示例骨架生成文档、报告、规格或交付产物，输出语言服从 `document_output_language`。\n    - **质量校验与交接**：执行清单、报告、状态同步或 completion handoff，并在退出前解析和执行 `workflow.on_complete`。\n    - **迁移一致性约束**：当前运行规约只依赖 Speclite runtime，不读取旧运行目录、旧配置文件或旧命令命名空间。\n\n[约定]\n    裸路径相对于 `{skill-root}` 解析；`{project-root}` 是目标项目工作目录；`{speclite-runtime-root}` 是 `{project-root}\u002F_speclite`；`{skill-name}` 是目录 basename。\n\n[激活流程]\n    触发后先解析 `workflow`，执行 `activation_steps_prepend`，加载 `persistent_facts`，运行 `speclite resolve config --project-root {project-root}`，按 `communication_language` 与用户沟通，并执行 `activation_steps_append`。配置文件缺失或关键字段为空时必须 HALT；`config.toml.example` 只说明字段结构，不作为 runtime fallback。\n\n    customization 必须通过 `speclite resolve customization --skill {skill-root} --project-root {project-root}` 读取 merged JSON；`workflow.on_complete` 使用 `speclite resolve customization --skill {skill-root} --project-root {project-root} --key workflow.on_complete` 解析。默认 activation 不手写 TOML merge，不使用 `--human` 作为 machine input。\n\n[执行流程]\n    1. 先完整阅读 `references\u002Fworkflow-details.md`；该文件是从源入口转换后的权威工作流规约。随后按需读取 `references\u002Fworkflow-details.md`、`references\u002Fsteps\u002Fstep-01-document-discovery.md`、`references\u002Fsteps\u002Fstep-02-prd-analysis.md`、`references\u002Fsteps\u002Fstep-03-epic-coverage-validation.md`、`references\u002Fsteps\u002Fstep-04-ux-alignment.md`、`references\u002Fsteps\u002Fstep-05-epic-quality-review.md` 等 reference 文件。\n    2. 执行工作流前，确认 `{skill-root}`、`{project-root}`、`{speclite-runtime-root}`、`{skill-name}` 四个路径变量均已明确。\n    3. 若 workflow 指向 step 文件，必须一次只读取当前 step，完整执行后再进入下一步；遇到菜单或用户确认点时 HALT 等待。\n    4. 生成或更新产物时，按源 workflow 的模板、清单、状态字段和输出位置要求执行，不得因为迁移而改变核心需求。\n    5. 收尾前运行 checklist 或质量检查，解析 `workflow.on_complete`，并在输出文档末尾追加本 Skill 的生成标注。\n\n[注意事项]\n    - 名称、目录与 YAML `name` 字段保持 kebab-case 一致：`speclite-implementation-readiness-check`。\n    - `references\u002Fworkflow-details.md` 和配套 reference 文件均为有效执行规约，不是背景资料。\n    - 模板或示例骨架位于 `assets\u002Freadiness-report-template.md`。\n    - 如工作流需要项目配置，必须读取目标项目运行时配置。\n    - `config.toml.example` 仅作字段结构参考，不作为 runtime fallback。\n    - 当前运行规约不得依赖旧运行目录、旧 YAML 配置或旧命令命名空间。\n    - 输出文档末尾必须追加 `*本文档由 speclite-implementation-readiness-check Skill 自动生成*` 标注。\n\n[生成信息]\n    本 Skill 由 speclite-skill-creator 自动生成。\n",{"name":5,"metadata":24,"description":7,"allowed-tools":28},{"author":25,"catalog":26,"version":27},"fancyliu","speclite","1.0.0","Read, Write, Bash, Grep, Glob, WebSearch","main","73fff74748dc0e27169d3ae76818d545bdbe8591","assets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-implementation-readiness-check",0,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite","https:\u002F\u002Fgithub.com\u002Fflanliulf","2026-11-12 11:47:29",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add flanliulf\u002FSpecLite --skill speclite-implementation-readiness-check",{"tool":42,"command":43},"bunx","bunx skills add flanliulf\u002FSpecLite --skill speclite-implementation-readiness-check",{"tool":45,"command":46},"pnpm","pnpm dlx skills add flanliulf\u002FSpecLite --skill speclite-implementation-readiness-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-implementation-readiness-check\u002FSKILL.md",true,[50,56,62,68,72,76,80,84,88,92,96,100],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Freadiness-report-template.md","ASSET","资产文件",95,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-implementation-readiness-check\u002Fassets\u002Freadiness-report-template.md",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"CHANGELOG.md","REFERENCE","参考文档",351,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-implementation-readiness-check\u002FCHANGELOG.md",{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"config.toml.example","OTHER","其他",917,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-implementation-readiness-check\u002Fconfig.toml.example",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"customize.toml",1639,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-implementation-readiness-check\u002Fcustomize.toml",{"path":73,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fsteps\u002Fstep-01-document-discovery.md",8911,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-implementation-readiness-check\u002Freferences\u002Fsteps\u002Fstep-01-document-discovery.md",{"path":77,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fsteps\u002Fstep-02-prd-analysis.md",4473,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-implementation-readiness-check\u002Freferences\u002Fsteps\u002Fstep-02-prd-analysis.md",{"path":81,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fsteps\u002Fstep-03-epic-coverage-validation.md",4111,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-implementation-readiness-check\u002Freferences\u002Fsteps\u002Fstep-03-epic-coverage-validation.md",{"path":85,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fsteps\u002Fstep-04-ux-alignment.md",3972,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-implementation-readiness-check\u002Freferences\u002Fsteps\u002Fstep-04-ux-alignment.md",{"path":89,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fsteps\u002Fstep-05-epic-quality-review.md",6769,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-implementation-readiness-check\u002Freferences\u002Fsteps\u002Fstep-05-epic-quality-review.md",{"path":93,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fsteps\u002Fstep-06-final-assessment.md",3608,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-implementation-readiness-check\u002Freferences\u002Fsteps\u002Fstep-06-final-assessment.md",{"path":97,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fworkflow-details.md",5319,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-implementation-readiness-check\u002Freferences\u002Fworkflow-details.md",{"path":101,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":102,"sourceHtmlUrl":103},"SKILL.en.md",4864,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-implementation-readiness-check\u002FSKILL.en.md",[105,111,118,125,132,139],{"skillNo":106,"name":107,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M76P89DWEDZ1JG6DSCQQPRPN","speclite-dev-story","https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fsource-integrity\u002Flocal-source-snapshot-unverified\u002Finput\u002Fsource\u002Fcore-skills\u002Fspeclite-dev-story\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"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":19},"01M76P87XBP3W1CZY0AJWPFSGE","speclite-code-review-01-reviewer","Fixture-owned installed skill entry for the minimal artifact loop.","https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fskill-artifact-loop\u002Finput\u002F.claude\u002Fskills\u002Fspeclite-code-review-01-reviewer\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M76P8507WMXJVZ17BFKADNWV","speclite-skill-lint","只读检查 Skill 定义；用于 lint skill、check skill、检查技能或评估 Skill 规范。区分基础格式、Codex 适配和 SpecLite 约定，报告证据及未检查项；Agent 定义包转交 speclite-agent-lint。","https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsupport-skills\u002Fspeclite-skill-lint\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"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":19},"01M76P82YCP8G07G0DFBB6VZGE","speclite-skill-creator","创建或迭代 SpecLite workflow Skill；用于 create skill、新建技能、生成技能包或封装工作流。设计入口、辅助资源和验证用例；Agent 定义包转交 speclite-agent-creator。","https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsupport-skills\u002Fspeclite-skill-creator\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":19},"01M76P7ZVEPVECYC258WNSD9XC","speclite-html-ppt-generator","生成 SpecLite-owned 单文件 HTML PPT。用于用户要求创建 docs presentation、HTML PPT、网页 slides、Swiss Style deck、杂志风 deck，或其他可直接浏览器打开的介绍\u002F分享型 deck。核心能力：使用本 Skill 内置模板、主题、layout 和 validator 生成横向翻页 HTML，并避免依赖外部个人 skill 路径。","https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsupport-skills\u002Fspeclite-html-ppt-generator\u002FSKILL.md",[],[],{"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":145,"publishedAt":19},"01M76P7WQ9NZDFZ306HKP8J6QX","speclite-docs-intro-ppt-creator","生成 SpecLite docs 下的介绍型 HTML PPT。用于用户要求把某个项目体系、系统设计、治理机制、理念或工作流总结成 docs presentation、HTML PPT、网页 slides、介绍 deck。核心能力：限定输出目录、基于事实材料规划叙事、调用 speclite-html-ppt-generator 生成单 HTML deck，并用确定性检查和浏览器抽样收口。","https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsupport-skills\u002Fspeclite-docs-intro-ppt-creator\u002FSKILL.md",[],[]]