Story Readiness: [story 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-StudiosFile: [path] Verdict: [READY / NEEDS WORK / BLOCKED]Passing Checks (N/[total])[list passing items briefly]Gaps[Checklist item]: [exact description of what is missing or wrong] Fix: [specific text needed to resolve this gap]Blockers (if BLOCKED)[What is blocking]: [story ID or design question that must resolve first]### 6.3 多故事汇总输出模板 markdown ## Story Readiness Summary — [scope] — [date] Ready: [N] stories Needs Work: [N] stories Blocked: [N] stories ### Ready Stories - [story title] ([path]) ### Needs Work - [story title]: [primary gap — one line] - [story title]: [primary gap — one line] ### Blocked Stories - [story title]: Blocked by [story ID / design question] --- [Full detail for each non-ready story follows, using the single-story format]6.4 Sprint 升级警告当作用域为sprint且任何Must Have故事处于 NEEDS WORK 或 BLOCKED 时输出顶部追加醒目警告WARNING: [N] Must Have stories are not implementation-ready. [List them with their primary gap or blocker.] Resolve these before the sprint begins or replan with /sprint-plan update.6.5 输出后处理先给结果再谈下一步技能协议要求先完整呈现检查结果再给出判定且不向用户索要写文件许可因为根本不会写文件。输出结尾必须有明确的下一步建议 —— 要么修复问题要么进入实现。7. Phase 8QL-STORY-READY 导演门与审查模式联动技能完成四维检查后进入导演门阶段。门 ID 为QL-STORY-READY由 qa-lead 以 Task 方式触发门定义与裁决规则见 .claude/docs/director-gates.md触发时机故事被纳入 sprint 之前由/create-stories、/story-readiness、/sprint-plan在故事选择阶段调用。传递给 qa-lead 的上下文Story file path故事文件路径Story typeLogic / Integration / Visual/Feel / UI / Config/DataAcceptance criteria list逐字引用自故事The GDD requirement (TR-ID and text) the story covers故事覆盖的 GDD 需求门裁决ADEQUATE—— 标准可按原文实现放行GAPS [list]—— 特定标准需要打磨技能需通过 AskUserQuestion 向用户呈现选项Update story with suggested gaps/Accept and proceed anyway/Discuss furtherINADEQUATE—— 标准过于模糊故事必须修订后才能进入 sprint。/story-readiness在 full / lean / solo 三种模式下的行为story-readiness门属于 per-skill gate不属于 PHASE-GATE模式QL-STORY-READY 行为输出备注solo跳过QL-STORY-READY skipped — Solo mode.lean跳过非 PHASE-GATEQL-STORY-READY skipped — Lean mode.full正常触发在输出中记录 Gate: QL-STORY-READY — [result]门裁决与四维检查结果的关系是叠加而非取并集qa-lead 的 INADEQUATE 裁决会覆盖四维检查的 READY 结果将最终判定压为 BLOCKED。技能运行时把门触发所依赖的 review mode 在 Phase 0 解析一次并全程缓存确保多次门检查使用同一模式。与它呼应的是故事关闭侧的门/story-done在 full 模式下触发LP-CODE-REVIEWlead-programmer 代码审查门NEEDS CHANGES 裁决会阻止故事被标记为 Complete见 .claude/skills/story-done/SKILL.md。这一对门构成了故事从就绪到完成的闭环质量防线。8. 协作协议只读、不代笔、重定向技能强调自己从不提议编辑、从不请求写文件。报告完成后向用户提出Would you like help filling in the gaps for any of these stories? I can draft the missing sections for your approval.若用户同意技能只在对话中草拟缺失章节绝不使用 Write/Edit 工具 —— 写入由用户或/create-stories完成。同时内置三条重定向规则处理典型异常场景重定向动作故事文件完全不存在Run/create-epics [layer]then/create-stories [epic-slug]to generate stories from the GDD and ADR.无 GDD 引用且工作规模小若改动小于约 4 小时Run/quick-design [description]to create a Quick Design Spec, then reference that spec in the story.故事范围膨胀超出原始估算Consider splitting it or escalating to the producer before implementation begins.这些规则确保技能不止于报错而是给出可执行的、指向正确工具的出路。9. 与相邻技能的衔接故事生命周期全景/story-readiness不是孤岛它嵌在一条完整的工程链中。技能文档末尾给出的 Recommended Next Steps 展示了其位置/qa-plan sprint ← define test requirements before sprint begins /story-readiness [path] ← validate before starting (本文技能) /dev-story [path] ← implement it /code-review [files] ← review it /story-done [path] ← verify and close it【免费下载链接】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），仅供参考