Story Done: [Story Name]
Story Done: [Story Name]
Story: [file path] Date: [today]
Acceptance Criteria: [X/Y passing]
- [x] [Criterion 1] — auto-verified (test passes)
- [x] [Criterion 2] — confirmed
- [ ] [Criterion 3] — FAILS: [reason]
- [?] [Criterion 4] — DEFERRED: requires playtest
Test-Criterion Traceability
| Criterion | Test | Status |
|---|---|---|
| AC-1: [text] | [test file::test name] | COVERED |
| AC-2: [text] | Manual confirmation | COVERED |
| AC-3: [text] | — | UNTESTED |
Test Evidence
Story Type: [Logic | Integration | Visual/Feel | UI | Config/Data | Not declared]
Required evidence: [unit test file | integration test or playtest | screenshot + sign-off | walkthrough doc | smoke check pass]
Evidence found: [YES — [path] | NO — BLOCKING | NO — ADVISORY]
Deviations
[NONE] OR:
- BLOCKING: [description] — [GDD/ADR reference]
- ADVISORY: [description] — user accepted / flagged for tech debt
Scope
[All changes within stated scope] OR:
- Extra files touched: [list] — [note whether valid or scope creep]
Verdict: COMPLETE / COMPLETE WITH NOTES / BLOCKED
三种判决的定义:
- **COMPLETE** — 所有标准通过,无阻塞性偏离;
- **COMPLETE WITH NOTES** — 所有标准通过,记录了建议性偏离;
- **BLOCKED** — 存在失败标准或阻塞性偏离,必须先解决。
若判决为 **BLOCKED**:不得进入 Phase 7,列出必须修复的条目,并主动提出帮助修复阻塞项。
---
## 十、Phase 7 — 更新故事状态(Update Story Status)
**写文件前必须征得同意**:先询问 "May I update the story file to mark it Complete and log the completion notes?",得到明确 "yes" 后才允许编辑。
### 10.1 编辑故事文件
1. 更新状态字段:`Status: Complete`;
2. 在文件底部追加 `## Completion Notes` 章节:
```markdown
## Completion Notes
**Completed**: [date]
**Criteria**: [X/Y passing] ([any deferred items listed])
**Deviations**: [None] or [list of advisory deviations]
**Test Evidence**: [Logic: test file at path | Visual/Feel: evidence doc at path | None required (Config/Data)]
**Code Review**: [Pending / Complete / Skipped]
- 若存在建议性偏离,询问:"Should I log these as tech debt in
docs/tech-debt-register.md?" - 更新
production/sprint-status.yaml(若存在):按故事文件路径或 ID 找到对应条目,设置status: done与completed: [today's date],并更新顶层updated字段。此更新为静默操作(上一步已获批准,无需额外确认)。
10.2 会话状态更新
更新故事文件后,静默追加到 production/session-state/active.md:
## Session Extract — /story-done [date]
- Verdict: [COMPLETE / COMPLETE WITH NOTES / BLOCKED]
- Story: [story file path] — [story title]
- Tech debt logged: [N items, or "None"]
- Next recommended: [next ready story title and path, or "None identified"]
若 active.md 不存在,则以该块为初始内容创建它。完成后在对话中确认:"Session state updated."。这与 /dev-story 的会话状态更新机制完全同构(见 .claude/skills/dev-story/SKILL.md Phase 7),保证了跨技能的状态连续性。
十一、Phase 8 — 顺位推出下一个故事(Surface the Next Story)
完成后帮助开发者保持节奏:
- 从
production/sprints/读取当前冲刺计划; - 找出满足以下条件的故事:
- Status 为 READY 或 NOT STARTED;
- 未被其他未完成故事阻塞;
- 位于 Must Have 或 Should Have 层级。
呈现:
### Next Up
The following stories are ready to pick up:
1. [Story name] — [1-line description] — Est: [X hrs]
2. [Story name] — [1-line description] — Est: [X hrs]
Run `/story-readiness [path]` to confirm a story is implementation-ready
before starting.
11.1 冲刺收尾序列(Sprint Close-Out Sequence)
若冲刺内不再有可推进的 Must Have 故事(全部 Complete 或 Blocked):
### Sprint Close-Out Sequence
All Must Have stories are complete. QA sign-off is required before advancing.
Run these in order:
1. `/smoke-check sprint` — verify the critical path still works end-to-end
2. `/team-qa sprint` — full QA cycle: test case execution, bug triage, sign-off report
3. `/gate-check` — advance to the next phase once QA approves
Do not run `/gate-check` until `/team-qa` returns APPROVED or APPROVED WITH CONDITIONS.
登录后查看全文