[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76P4HFBRCSFRQFGVR0HP86J":3,"skill-same:01M76P4HFBRCSFRQFGVR0HP86J":84},{"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},"01M76P4HFBRCSFRQFGVR0HP86J","speclite-create-epics-and-stories",null,"把 PRD、Architecture 与 UX 输入拆解为 Epic 和可实现 Story。用于用户要求 create epics and stories、生成 Epic、拆分需求、创建 `epics.md` 或准备开发 backlog。核心能力：提取需求、设计 Epic、顺序生成 Story、校验覆盖并写出 `epics.md`。","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-create-epics-and-stories\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: speclite-create-epics-and-stories\ndescription: \"把 PRD、Architecture 与 UX 输入拆解为 Epic 和可实现 Story。用于用户要求 create epics and stories、生成 Epic、拆分需求、创建 `epics.md` 或准备开发 backlog。核心能力：提取需求、设计 Epic、顺序生成 Story、校验覆盖并写出 `epics.md`。\"\nallowed-tools: Read, Write, Grep, Glob, Bash\nmetadata:\n  version: \"1.0.0\"\n  author: \"fancyliu\"\n  catalog: \"speclite\"\n---\n\n[技能说明]\n    # Create Epics and Stories Workflow\n\n    **Goal:** 将 PRD、Architecture 与可选 UX Design 中的需求，拆解为按用户价值组织的 Epics 和可交付 Stories，并生成完整 `epics.md`。\n\n    **Your Role:** 产品策略师与技术规格撰写者，和产品负责人平等协作。\n    - 使用 `{communication_language}` 沟通，使用 `{document_output_language}` 生成文档。\n    - 你负责需求抽取、用户价值分组、故事粒度控制、验收标准和覆盖校验。\n    - 用户负责产品愿景、业务优先级、上下文确认和阶段性审批。\n    - 这是强交互工作流：禁止跳步，必须在菜单点 HALT 并等待用户选择。\n\n[核心能力]\n    - **UX 输入路径治理**：优先读取 `{planning_artifacts}\u002Fux\u002Fux-design-specification.md`，canonical 缺失时才使用 exact legacy fallback，并记录 Planning root resolver evidence 与 no-migration 边界。\n    - **Whole\u002Fsharded 单一发现契约**：PRD、Epics、Architecture 只通过 `speclite resolve artifact-documents` 的 `consumedPaths` 消费；block 必须保持 zero artifact write 与 zero progress mutation，selection 只作用于当前 invocation。\n    - **配置与激活解析**：解析三层 customize（base→team→user）和 `workflow` 块，加载 `persistent_facts`、`config.toml`、激活前置\u002F后置步骤和 `workflow.on_complete`。\n    - **输入制品发现与需求抽取**：通过 shared resolver 从 `{planning_artifacts}\u002Fprd\u002F` 与 `{solutioning_artifacts}\u002Farchitecture\u002F` 发现 PRD、Architecture，并从 Planning 发现可选 UX Design，抽取 FR、NFR、技术要求和 UX Design Requirements。\n    - **Epic 设计协作**：按用户价值而非技术层组织 Epic，显式处理 FR 覆盖、自然依赖、文件反复改动风险和合并边界。\n    - **Story 顺序生成**：逐个 Epic、逐个 Story 生成，确保每个 Story 可由单个开发智能体完成，且只依赖前置 Story。\n    - **模板化输出**：从 `assets\u002Fepics-template.md` 初始化 `{planning_artifacts}\u002Fepics\u002Fepics.md`，用 frontmatter 记录 `stepsCompleted` 与 `inputDocuments`。\n    - **最终覆盖校验**：校验全部 FR、UX-DR、架构约束、实体创建时机、Epic 独立性与 Story 前向依赖。\n\n[执行流程]\n    1. 先完整阅读 `references\u002Factivation.md` 与 `references\u002Fworkflow-steps.md`；二者是完整操作规约，不能跳过或缩写执行。\n    2. 激活时解析 `workflow`、三层 customize、`workflow.persistent_facts` 与运行项目根下的 merged runtime config；本 Skill 目录中的 `config.toml.example` 仅作字段结构参考。\n    3. 使用 `assets\u002Fepics-template.md` 初始化输出文件，并严格按 `references\u002Fworkflow-steps.md` 的 Step 1 → Step 4 顺序推进。\n    4. 每个步骤必须完整读取、顺序执行、保存状态；遇到菜单必须 HALT，只有用户选择 `C` 才能进入下一步。\n    5. 完成时保存 `{planning_artifacts}\u002Fepics\u002Fepics.md`，执行 `workflow.on_complete`（若非空），并给出后续开发、Story 创建或评审建议。\n\n[注意事项]\n    - 名称、目录与 YAML `name` 字段保持 kebab-case 一致：`speclite-create-epics-and-stories`。\n    - `{speclite-runtime-root}` 固定表示 `{project-root}\u002F_speclite`；项目运行配置只通过 `speclite resolve config --project-root {project-root}` 读取 merged runtime config 中的。\n    - `config.toml.example` 只是参考示例，禁止作为 runtime fallback。\n    - `customize.toml` 只承载 `[workflow]` 默认定制面；团队和个人覆盖位于 `{speclite-runtime-root}\u002Fcustom\u002F{skill-name}.toml` 与 `{skill-name}.user.toml`。\n    - 不得替用户凭空生成需求；必须基于已发现文档和用户确认推进。\n    - Epic 必须按用户价值组织；Story 不得依赖同 Epic 中未来 Story，实体和表只在首次需要时创建。\n    - `epics.md` 末尾必须追加 `*本文档由 speclite-create-epics-and-stories Skill 自动生成*` 标注。\n\n[生成信息]\n    本 Skill 由 speclite-skill-creator 自动生成。如需修改，建议同步更新 forge\u002F 和 .claude\u002Fskills\u002F 两份副本，或通过 skills-upgrade 管理版本。\n","[技能说明]\n    # Create Epics and Stories Workflow\n\n    **Goal:** 将 PRD、Architecture 与可选 UX Design 中的需求，拆解为按用户价值组织的 Epics 和可交付 Stories，并生成完整 `epics.md`。\n\n    **Your Role:** 产品策略师与技术规格撰写者，和产品负责人平等协作。\n    - 使用 `{communication_language}` 沟通，使用 `{document_output_language}` 生成文档。\n    - 你负责需求抽取、用户价值分组、故事粒度控制、验收标准和覆盖校验。\n    - 用户负责产品愿景、业务优先级、上下文确认和阶段性审批。\n    - 这是强交互工作流：禁止跳步，必须在菜单点 HALT 并等待用户选择。\n\n[核心能力]\n    - **UX 输入路径治理**：优先读取 `{planning_artifacts}\u002Fux\u002Fux-design-specification.md`，canonical 缺失时才使用 exact legacy fallback，并记录 Planning root resolver evidence 与 no-migration 边界。\n    - **Whole\u002Fsharded 单一发现契约**：PRD、Epics、Architecture 只通过 `speclite resolve artifact-documents` 的 `consumedPaths` 消费；block 必须保持 zero artifact write 与 zero progress mutation，selection 只作用于当前 invocation。\n    - **配置与激活解析**：解析三层 customize（base→team→user）和 `workflow` 块，加载 `persistent_facts`、`config.toml`、激活前置\u002F后置步骤和 `workflow.on_complete`。\n    - **输入制品发现与需求抽取**：通过 shared resolver 从 `{planning_artifacts}\u002Fprd\u002F` 与 `{solutioning_artifacts}\u002Farchitecture\u002F` 发现 PRD、Architecture，并从 Planning 发现可选 UX Design，抽取 FR、NFR、技术要求和 UX Design Requirements。\n    - **Epic 设计协作**：按用户价值而非技术层组织 Epic，显式处理 FR 覆盖、自然依赖、文件反复改动风险和合并边界。\n    - **Story 顺序生成**：逐个 Epic、逐个 Story 生成，确保每个 Story 可由单个开发智能体完成，且只依赖前置 Story。\n    - **模板化输出**：从 `assets\u002Fepics-template.md` 初始化 `{planning_artifacts}\u002Fepics\u002Fepics.md`，用 frontmatter 记录 `stepsCompleted` 与 `inputDocuments`。\n    - **最终覆盖校验**：校验全部 FR、UX-DR、架构约束、实体创建时机、Epic 独立性与 Story 前向依赖。\n\n[执行流程]\n    1. 先完整阅读 `references\u002Factivation.md` 与 `references\u002Fworkflow-steps.md`；二者是完整操作规约，不能跳过或缩写执行。\n    2. 激活时解析 `workflow`、三层 customize、`workflow.persistent_facts` 与运行项目根下的 merged runtime config；本 Skill 目录中的 `config.toml.example` 仅作字段结构参考。\n    3. 使用 `assets\u002Fepics-template.md` 初始化输出文件，并严格按 `references\u002Fworkflow-steps.md` 的 Step 1 → Step 4 顺序推进。\n    4. 每个步骤必须完整读取、顺序执行、保存状态；遇到菜单必须 HALT，只有用户选择 `C` 才能进入下一步。\n    5. 完成时保存 `{planning_artifacts}\u002Fepics\u002Fepics.md`，执行 `workflow.on_complete`（若非空），并给出后续开发、Story 创建或评审建议。\n\n[注意事项]\n    - 名称、目录与 YAML `name` 字段保持 kebab-case 一致：`speclite-create-epics-and-stories`。\n    - `{speclite-runtime-root}` 固定表示 `{project-root}\u002F_speclite`；项目运行配置只通过 `speclite resolve config --project-root {project-root}` 读取 merged runtime config 中的。\n    - `config.toml.example` 只是参考示例，禁止作为 runtime fallback。\n    - `customize.toml` 只承载 `[workflow]` 默认定制面；团队和个人覆盖位于 `{speclite-runtime-root}\u002Fcustom\u002F{skill-name}.toml` 与 `{skill-name}.user.toml`。\n    - 不得替用户凭空生成需求；必须基于已发现文档和用户确认推进。\n    - Epic 必须按用户价值组织；Story 不得依赖同 Epic 中未来 Story，实体和表只在首次需要时创建。\n    - `epics.md` 末尾必须追加 `*本文档由 speclite-create-epics-and-stories Skill 自动生成*` 标注。\n\n[生成信息]\n    本 Skill 由 speclite-skill-creator 自动生成。如需修改，建议同步更新 forge\u002F 和 .claude\u002Fskills\u002F 两份副本，或通过 skills-upgrade 管理版本。\n",{"name":5,"metadata":24,"description":7,"allowed-tools":28},{"author":25,"catalog":26,"version":27},"fancyliu","speclite","1.0.0","Read, Write, Grep, Glob, Bash","main","73fff74748dc0e27169d3ae76818d545bdbe8591","assets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-create-epics-and-stories",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-create-epics-and-stories",{"tool":42,"command":43},"bunx","bunx skills add flanliulf\u002FSpecLite --skill speclite-create-epics-and-stories",{"tool":45,"command":46},"pnpm","pnpm dlx skills add flanliulf\u002FSpecLite --skill speclite-create-epics-and-stories","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-create-epics-and-stories\u002FSKILL.md",true,[50,56,62,68,72,76,80],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Fepics-template.md","ASSET","资产文件",1183,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-create-epics-and-stories\u002Fassets\u002Fepics-template.md",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"CHANGELOG.md","REFERENCE","参考文档",1260,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-create-epics-and-stories\u002FCHANGELOG.md",{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"config.toml.example","OTHER","其他",938,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-create-epics-and-stories\u002Fconfig.toml.example",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"customize.toml",2306,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-create-epics-and-stories\u002Fcustomize.toml",{"path":73,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Factivation.md",4272,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-create-epics-and-stories\u002Freferences\u002Factivation.md",{"path":77,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fworkflow-steps.md",18586,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-create-epics-and-stories\u002Freferences\u002Fworkflow-steps.md",{"path":81,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":82,"sourceHtmlUrl":83},"SKILL.en.md",4957,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsdlc-skills\u002F3-solutioning\u002Fspeclite-create-epics-and-stories\u002FSKILL.en.md",[85,91,98,105,112,119],{"skillNo":86,"name":87,"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":88,"categories":89,"keywords":90,"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"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",[],[]]