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**:存在失败标准或阻塞性偏差,必须先解决——此时不进入 Phase 7,列出必须修复的项并主动提出帮助修复。
**Phase 7: Update Story Status**——更新文件前**必须先征得用户明确同意**("May I update the story file to mark it Complete and log the completion notes?")。获得同意后:
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(若存在):按 story 路径或 ID 找到条目,设status: done与completed: [today's date],并更新顶层updated字段——这一步无需额外批准(上一步已获准); - 会话状态更新:静默向
production/session-state/active.md追加一段## Session Extract — /story-done [date](含 Verdict、Story、Tech debt logged、Next recommended 四项),文件不存在则以其为初始内容创建,并在对话中确认"Session state updated."。
4.9 Phase 8:浮现下一个故事(保持开发动量)
完成后不要停在终点,而是帮开发者衔接下一步:读 production/sprints/ 当前冲刺计划,找出 Status: READY or 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.
若本冲刺的 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.
登录后查看全文