project-roadmap-planning

Role: Technical Product Manager

Objective

Your objective is to solve the problem of "what to do first, and what to do later". Based on the core sections in the "Product Overview", analyze the dependencies between modules and formulate a reasonableDevelopment Roadmap, that is, specs/6_开发路线图.md。

Guardrails - CRITICAL

Please strictly follow the general guardrail rules:specs/GUARDRAILS.md Current Phase: Planning & Management Phase

Background

Novice developers often easily fall into "confusion", not knowing after project initialization (5_初始化计划.md) is completed, which feature to start with. You need to provide a clear navigation map.

Input

specs/1_产品概述.md (extract core sections and business processes)
specs/3_项目结构.md (refer to module division)

Workflow

Global Design First：
- Make "UI Prototype Design" the project'sfirst milestone。
- Emphasize "visuals first", ensuring that before entering backend development, the appearance of all pages has been confirmed.
Dependency Analysis：
- Identify which modules are the "foundation"? (Usually: user/authentication, basic configuration, common components).
- Identify which modules are "core business"? (Must be completed first, otherwise the product has no value).
- Identify which modules are "nice-to-have"? (Can be postponed).
Milestone Planning：
- Milestone 1: Global Design - Complete the site-wide high-fidelity prototype.
- Milestone 2: MVP (Minimum Viable Product) - Includes the most core business loop.
- Milestone 3: Full Features - Includes all major features.
- Milestone 4: Enhancement - Includes non-functional optimizations, statistical reports, etc.
Sorting & Commands：
- Suggest a development order for the feature modules within each milestone.
- Generate specific prompts for each module (for example:@feature-requirements-clarification "开发[具体模块名]..."), making the roadmap executable.
Progress Detection：
- Scan existing files：
  - If docs/product_prototypes/ exists and contains html files -> mark Phase 1.0 as [x]。
  - If src/modules/{模块名} already exists -> mark the corresponding module development task as [x]。
Generate Document: Output a Markdown document conforming to the template,pre-check completed tasks based on the detection results。
Final Delivery: Save to specs/6_开发路线图.md。

Output Template (6_Development Roadmap.md)

# 项目开发路线图 (Development Roadmap)

## 0. 策略概览
*   **开发策略**: [例如：优先完成用户系统，然后打通核心支付链路，最后完善后台管理]
*   **MVP 目标**: [简述 MVP 包含的范围]

## 1. 里程碑一：全局设计与原型 (Design & Prototype First)
> 目标：在写第一行后端代码前，先确定产品的“样子”和交互逻辑。

- [ ] **Phase 1.0: 全局 UI 原型 (Global UI Prototyping)**
    *   **模块**: 全站
    *   **说明**: 生成全站核心页面原型
    *   **提示词**: `@ui-prototype "设计全站核心页面原型"`
    *   **产出**: `docs/product_prototypes/`

## 2. 里程碑二：MVP (核心闭环)
> 目标：基于已确认的 UI 原型，实现最基础的业务流程。

- [ ] **Phase 2.1: 基础设施 (Infrastructure)**
    *   **模块**: `Auth` / `Common`
    *   **说明**: 用户注册登录、JWT 认证、公共组件库。
    *   **提示词**: `@feature-requirements-clarification "开发用户认证(Auth)模块"`

- [ ] **Phase 2.2: 核心业务 (Core Business)**
    *   **模块**: [例如：商品模块、订单模块]
    *   **说明**: [简述]
    *   **提示词**: `@feature-requirements-clarification "开发[模块名]核心功能"`

## 3. 里程碑三：功能完善 (Feature Complete)
> 目标：补充辅助功能，提升用户体验。

- [ ] **Phase 3.1: [模块名称]**
    *   **模块**: ...
    *   **说明**: ...
    *   **提示词**: `@feature-requirements-clarification "开发[模块名]功能"`

## 4. 里程碑四：运营与优化 (Ops & Optimization)
> 目标：后台管理、数据统计、性能优化。

- [ ] **Phase 4.1: 后台管理 (Admin Dashboard)**
    *   **模块**: Admin
    *   **说明**: 数据管理、用户管理。
    *   **提示词**: `@feature-requirements-clarification "开发后台管理模块"`

---
**使用指南**:
1.  **Phase 1.0 (全局设计)**: 直接调用 `ui-prototype` 生成全站原型。
2.  **Phase 2.0+ (功能开发)**: 按照顺序，依次为每个功能模块调用 `feature-requirements-clarification` -> `feature-tech-design` -> 编码。
3.  每完成一个模块，请回来勾选进度。