spec-flow

# Spec-Flow - Structured Development Workflow Structured workflow for complex feature development. Creates living documentation that guides implementation and serves as team reference. ## Core Principles 1. **One phase at a time** — NEVER generate documents for subsequent phases in advance 2. **Mandatory confirmation** — After each phase, STOP and wait for user confirmation 3. **User-driven progression** — Only proceed when user says "continue"/"ok"/"next"/"继续"/"好" ## Parameters | 参数 | 说明 | |------|------| | `--fast` | 跳过逐阶段确认，一次性生成所有文档（最后整体确认） | | `--skip-design` | 跳过 Design 阶段（简单功能，架构显而易见时） | ## Language Rule **所有生成的 .md 文件必须使用中文。** ## Interaction Rules Load `references/interaction-rules.md` for detailed confirmation templates and prohibited behaviors. --- ## Five-Phase Workflow Copy this checklist and check off items as you complete them: ### Spec-Flow Progress: - [ ] **Phase 0: Initialize** ⚠️ REQUIRED - [ ] 0.1 Run `scripts/init-spec-flow.sh <feature-name>` or create `.spec-flow/active/<feature>/` - [ ] 0.2 Check if `.spec-flow/steering/` exists — if so, read for project context - [ ] 0.3 问自己：**这个功能的核心价值是什么？用一句话能说清吗？** - [ ] **Phase 1: Proposal** ⚠️ REQUIRED - [ ] 1.1 Create `.spec-flow/active/<feature>/proposal.md` using `templates/proposal.md.template` - [ ] 1.2 包含：Background, Goals, Non-Goals, Scope, Risks, Open Questions - [ ] 1.3 问自己：**有没有隐含的需求没写出来？** - [ ] 1.4 问自己：**Non-Goals 是否足够明确？能防止 scope creep 吗？** - [ ] 1.5 ⏸️ 确认节点 — 等待用户确认后继续 ...