spec-flowlisted

# Spec-Flow - Structured Development Workflow Structured workflow for complex feature development. Creates living documentation that guides implementation and serves as team reference. ## ⚠️ Interaction Rules (MUST Follow) This skill uses a **phase-by-phase confirmation** workflow, ensuring users can review and adjust at each stage. ### Language Rule **All generated documents (.md files) MUST be written in Chinese (中文)**, including: - proposal.md, requirements.md, design.md, tasks.md - Section headings, descriptions, requirements text, task descriptions - Comments and notes within documents ### Core Principles 1. **One phase at a time**: Only work on the current phase. NEVER generate documents for subsequent phases in advance. 2. **Mandatory confirmation**: After completing each phase, you MUST stop and wait for user confirmation. 3. **User-driven progression**: Only proceed to the next phase when user explicitly says "continue", "ok", "next", "looks good", "继续", "好", "下一步", etc. ### Confirmation Template After completing each phase, you MUST use this format to request confirmation: ``` 📋 **[Phase Name] Complete** Created `.spec-flow/active/<feature>/<file>.md` containing: - [Key content summary] **Please review**: 1. [Review question]? 2. [Review question]? ✅ Say "continue" to proceed to next phase ✏️ Tell me what to modify if needed ``` ### ❌ Prohibited Behaviors - Generating multiple phase documents after user describes a feature - Automatically proceeding