Story [NNN]: [title]

发布时间:2026/9/12 21:42:28
Story [NNN]: [title] Story [NNN]: [title]【免费下载链接】Claude-Code-Game-StudiosTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.项目地址: https://gitcode.com/GitHub_Trending/cl/Claude-Code-Game-StudiosEpic: [epic name]Status: ReadyLayer: [Foundation / Core / Feature / Presentation]Type: [Logic | Integration | Visual/Feel | UI | Config/Data]Manifest Version: [date from control-manifest.md header]ContextGDD:design/gdd/[filename].mdRequirement:TR-[system]-NNN(Requirement text lives indocs/architecture/tr-registry.yaml— read fresh at review time)ADR Governing Implementation: [ADR-NNNN: title]ADR Decision Summary: [1-2 sentence summary of what the ADR decided]Engine: [name version] |Risk: [LOW / MEDIUM / HIGH]Engine Notes: [from ADR Engine Compatibility section — post-cutoff APIs, verification required]Control Manifest Rules (this layer):Required: [relevant required pattern]Forbidden: [relevant forbidden pattern]Guardrail: [relevant performance guardrail]Acceptance CriteriaFrom GDDdesign/gdd/[filename].md, scoped to this story:[criterion 1 — directly from GDD][criterion 2][performance criterion if applicable]Implementation NotesDerived from ADR-NNNN Implementation Guidelines:[Specific, actionable guidance from the ADR. Do not paraphrase in ways that change meaning. This is what the programmer reads instead of the ADR.]Out of ScopeHandled by neighbouring stories — do not implement here:[Story NNN1]: [what it handles]QA Test CasesWritten by qa-lead at story creation. The developer implements against these — do not invent new test cases during implementation.[For Logic / Integration stories — automated test specs]:AC-1: [criterion text]Given: [precondition]When: [action]Then: [assertion]Edge cases: [boundary values / failure states][For Visual/Feel / UI stories — manual verification steps]:AC-1: [criterion text]Setup: [how to reach the state]Verify: [what to look for]Pass condition: [unambiguous pass description]Test EvidenceStory Type: [type]Required evidence:Logic:tests/unit/[system]/[story-slug]_test.[ext]— must exist and passIntegration:tests/integration/[system]/[story-slug]_test.[ext]OR playtest docVisual/Feel:production/qa/evidence/[story-slug]-evidence.md sign-offUI:production/qa/evidence/[story-slug]-evidence.mdor interaction testConfig/Data: smoke check pass (production/qa/smoke-*.md)Status: [ ] Not yet createdDependenciesDepends on: [Story NNN-1 must be DONE, or None]Unlocks: [Story NNN1, or None]### 8.1 模板设计要点解读 - **Info 区块frontmatter 式引用块**携带 Epic、Layer、Type、Manifest Version 五个元字段。Manifest Version 直接取 control manifest 头部日期——这一字段在 /story-readiness 中会被比对版本陈旧会导致 NEEDS WORK 判定见 [story-readiness 测试规格](https://link.gitcode.com/i/2946fc72e69619337cfb0e74857de1d4) Case 4Manifest Version: 2026-01-15 与当前 2026-03-10 不匹配即被标记 ADVISORY 问题。 - **Context 区**TR-ID 只写 ID 不写需求原文评审时从注册表实时读取保证永远引用最新需求文本Engine Notes 专门搬运 ADR Engine Compatibility 章节中的 post-cutoff APIs 与验证要求。 - **Implementation Notes**直接摘自 ADR Implementation Guidelines**禁止以改变原意的方式转述**——程序员读它时读到的就是 ADR 原文的精髓。 - **Out of Scope**明确邻接故事负责的范围防止边界蔓延。 - **Test Evidence**按 Story 类型给出差异化的证据路径Status: [ ] Not yet created 表示证据尚未产出由 /dev-story 在实现阶段填充。 ### 8.2 同步更新 EPIC.md 写完全部 Story 文件后需把 production/epics/[epic-slug]/EPIC.md 中 Stories: Not yet created 一行替换为填充好的表格 markdown ## Stories | # | Story | Type | Status | ADR | |---|-------|------|--------|-----| | 001 | [title] | Logic | Ready | ADR-NNNN | | 002 | [title] | Integration | Ready | ADR-MMMM |九、写盘后的收尾与下一步交接Step 7所有文件写入完成后使用AskUserQuestion结合上下文给出下一步选项。检查逻辑检查production/epics/中是否还有其他没有 Story 的 Epic并列出它们若当前是最后一个 Epic则把/sprint-plan加入选项。Widget 选项按适用条件裁剪[A] Start implementing — run /story-readiness [first-story-path]推荐[B] Create stories for [next-epic-slug] — run /create-stories [slug]仅当其他 Epic 尚无 Story 时[C] Plan the sprint — run /sprint-plan仅当所有 Epic 都有 Story 时[D] Stop here for this session输出需附注Work through stories in order — each storysDepends on:field tells you what must be DONE before you can start it.写盘结束后无论是否批准输出最终裁决Verdict: COMPLETE— [N] stories written toproduction/epics/[epic-slug]/. Run/story-readiness→/dev-storyto begin implementation.Verdict: BLOCKED— user declined. No story files written.十、协作协议六条纪律本技能通过六条协作协议约束交互行为防止越界Read before presenting— 静默加载全部输入后再展示故事清单Ask once— 整个 Epic 的故事一次性汇总呈现不逐条询问Warn on blocked stories— 写入前标记任何带 Proposed ADR 的故事Ask before writing— 写文件前获得整批故事集的批准No invention— 验收标准来自 GDD、实现说明来自 ADR、规则来自控制清单零虚构Never start implementation— 本技能止步于 Story 文件层绝不进入实现。第 5、6 条与lead-programmer的职责边界相互印证lead-programmer 测试规格 明确其不拥有游戏设计决策权也不直接写业务代码实际实现由/dev-story委派给专科 agent 完成dev-story 测试规格 断言Skill routes implementation to the correct specialist agent — it does not write source code directly。十一、行为契约的仓库级验证五条测试用例CCGS Skill Testing Framework/skills/pipeline/create-stories.md以 5 条用例把本技能的行为固化为可回归验证的契约这既是该技能被Skill Testing Framework纳管的方式也是理解其边界最直接的源码级证据用例场景关键断言Case 1快乐路径3 个需求、ADR 全 Accepted、lean 模式正确分类类型至少一个 Logic、门禁跳过有注记、写盘前逐条询问、不启动实现Case 2失败路径Epic 文件不存在输出指明缺失文件路径的错误、不写任何文件、建议先跑/create-epicsCase 3阻塞路径某需求被 Proposed ADR 覆盖Story 2 置Status: Blocked且附注具体 ADR 编号与/architecture-decision建议Story 1 正常 Ready阻塞故事仍被写入但提前标记Case 4边界情况无参数调用输出 usage 错误、列出可用 Epic、不静默替用户选择Case 5门禁行为full 模式下 QL-STORY-READY 执行逐故事呈现 ADEQUATE/INADEQUATE 结果未过者为 NEEDS WORK 并给出具体反馈写盘前呈现通过/失败状态Protocol Compliance 清单还额外验证了所有上下文EPIC、GDD、ADR、manifest、TR 注册表在起草前加载完毕故事草稿在May I write前完整展示控制清单规则逐故事引用而非杜撰以及以/story-readiness→/dev-story结束交接。十二、在管线中的完整位置一次端到端视角把本技能放回 CCGS 全流程其前后衔接一目了然/create-control-manifest 定义各 layer 的 Required/Forbidden/Guardrail 规则 ↓ /create-epics [system] 已批准 GDD → EPIC.md按 layer 组织 ↓ /create-stories [epic-slug] ★ 本文主题EPIC.md → 多个 story-NNN-*.md ↓ /story-readiness [story-path] 四维校验Design / Architecture / Scope / DoD产出 READY / NEEDS WORK / BLOCKED ↓ /dev-story [story-path] 委派专科 agent 实现验证验收标准full 模式含 LP-CODE-REVIEW ↓ /story-done 核对 TR 注册表最新需求文本与证据后关闭故事【免费下载链接】Claude-Code-Game-StudiosTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.项目地址: https://gitcode.com/GitHub_Trending/cl/Claude-Code-Game-Studios创作声明:本文部分内容由AI辅助生成(AIGC),仅供参考

关于本文作者

来自尧图内容编辑团队

尧图内容编辑团队 内容团队

尧图内容编辑团队

本文由尧图网络内容编辑团队执笔。团队由资深项目经理、前端工程师与设计师组成,所有内容均来自亲手交付的真实项目,先讲清问题、再给出可落地的解法。尧图深耕北京网站建设十年,服务过京华建材集团、智造科技等各行业客户,把一线经验沉淀为可复用的行业观察。

  • 十年建站经验,覆盖建材、制造、服务、文创等
  • 项目经理把关选题与事实准确性
  • 工程师与设计师联合撰写专业细节
  • 统一编辑规范,保证文风与排版一致
  • 每月复盘转化数据,迭代选题方向

延伸阅读

相关资讯与近期热门内容

深度阅读推荐

建站决策前值得细读的三篇

网站改版的5个关键决策
2024-08-12

网站改版的5个关键决策

什么时候该改版、改到什么程度、如何避免流量掉光,京华建材集团改版复盘给出答案。

获取专属建站方案

看完文章,把您的行业与预算告诉我们,免费获取一份量身定制的官网建设方案与报价。

立即免费咨询