📦 spec-stateflow — spec-状态flow

Spec 工作流

导入ant: You must follow these rules. Each phase must be confirmed by the user before proceeding to the next phase.

When to Use This 技能

Use this 技能 for structured development 工作流 when you need to:

Develop new features from scratch De签名 complex architecture Integrate multiple 模块s Ensure high-质量 requirement analysis and acceptance criteria

Do NOT use for:

Simple requirements Simple bug fixes Documentation 更新s Configuration changes How to Use This 技能 Follow the four phases in order — each phase requires user confirmation before proceeding: Phase 1: Write requirements using EARS syntax → requirements.md Phase 2: De签名 technical solution (architecture, API, DB, etc.) → de签名.md Phase 3: Break down tasks with field-level specifics → tasks.md Phase 4: 执行 tasks with 状态 追踪ing, 压缩ion 恢复y, and 上下文 switching 【HIGHEST PRIORITY】Real-time tasks.md 更新s — After completing each small task, you MUST immediately 更新 {SPEC_PATH}/tasks.md, before compilation, 测试, or 启动ing the next task. Not 更新d = not done. See Phase 4 状态 Assurance for detAIls

测试: This 技能 includes test-prompts.json with 5 test scenarios covering all phases. Use them to 验证 技能 behavior.

Path Convention

All Spec files use the following placeholders. Actual paths are defined in the user's project configuration:

Placeholder Meaning {SPEC_DIR} Spec file root directory {SPEC_NAME} Current spec name {SPEC_PATH} Full path = {SPEC_DIR}/{SPEC_NAME}

Spec file 列出:

File Description {SPEC_PATH}/requirements.md Requirements document (Phase 1 输出) {SPEC_PATH}/de签名.md Technical de签名 document (Phase 2 输出) {SPEC_PATH}/tasks.md Task breakdown & 进度 追踪er (Phase 3 输出, single source of truth) Entry Points Your situation 启动 here New feature / complex task Phase 1 (full 工作流: Phase 1 → 2 → 3 → 4) Ready to 执行 (user confirmed plan) Phase 4 → Quick 启动 会话 压缩ed / interrupted Phase 4 → 压缩ion 恢复y

For all 运行time 状态s (error, 上下文 switch, task completion, etc.), see Phase 4 → 状态 Navigation.

工作流 Rules

When you determine that the user's 输入 implies a new requirement (not explicitly 状态d), you may work independently following standard software engineering practices. Confirm with the user when necessary.

When the user explicitly 状态s a new requirement, you must follow the full 工作流: understand the problem and requirements clearly, and confirm with the user before proceeding to the next phase.

Phase 1: Requirements Document and Acceptance Criteria De签名

First complete the requirements de签名 using EARS (Easy 应用roach to Requirements Syntax) method. You must confirm requirement detAIls with the user. After final confirmation, the requirements are finalized, then proceed to the next phase.

Save to {SPEC_PATH}/requirements.md. After confirming with the user, proceed to the next phase.

If user rejects or 请求s changes: 更新 requirements.md and re-confirm. Do NOT proceed to Phase 2 until user explicitly 应用roves.

Reference 格式化:

# Requirements Document

Introduction

Requirement description

Requirements

Requirement 1 - Requirement Name

User Story: User story content

Acceptance Criteria

• Use EARS syntax: While , when , the <系统 name> shall <系统 响应>. For example: When "Mute" is selected, the laptop shall suppress all audio 输出.
• ...

...

Phase 2: Technical Solution De签名

After completing the requirements de签名, based on the current technical architecture and the confirmed requirements above, de签名 the technical solution. It should be concise but accurately describe the technical architecture (e.g., architecture, tech stack, techno记录y selection, database/interface de签名, test strategy, security). Use mermAId diagrams when necessary.

Must include chapters: Background, De签名 Goals, Business 模型, 系统 De签名 (precise to package path, class name, method 签名ature), Refactoring De签名 (if 应用licable), 部署ment Plan (for large tasks), Risk Assessment (for large tasks).

Save to {SPEC_PATH}/de签名.md. You must confirm with the user clearly, then proceed to the next phase.

If user rejects or 请求s changes: 更新 de签名.md and re-confirm. Do NOT proceed to Phase 3 until user explicitly 应用roves.

Reference 格式化:

# Technical Solution De签名

Background

Why this de签名 is needed — business 上下文 and problem 状态ment

De签名 Goals

• Goal 1: ...
• Goal 2: ...

Business 模型

Core domAIn 模型s, entity relationships, key data flows

系统 De签名

Architecture Overview

(mermAId diagram or 组件 description)

模块: {模块-name}

• Package: com.example.模块
• New classes:

- ClassName — responsibility description - InterfaceName — method 签名atures: ReturnType methodName(ParamType param)

• Modified classes:

- ExistingClass — 添加 method `newMe