Back to Details

mvp

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

MVP Product Planner

MVP产品规划工具

Deep requirements gathering, feature ideation, scope management, technical architecture, and living documentation for new products. Produces 5 planning artifacts: OVERVIEW, FEATURES, MVP_SCOPE, ROADMAP, and DELIVERABLES.
为新产品提供深度需求收集、功能构思、范围管理、技术架构设计和动态文档服务。生成5种规划文档：OVERVIEW、FEATURES、MVP_SCOPE、ROADMAP和DELIVERABLES。

Quick Start

快速开始

Follow all steps sequentially across 3 phases. Do NOT write any files until the plan is approved in Step 6.
按顺序完成3个阶段的所有步骤。在步骤6获得计划批准前，不得写入任何文件。

Workflow

工作流程

Phase 1: Understand (Steps 0-3)

第一阶段：需求理解（步骤0-3）

Step 0: Enter Plan Mode & Parse Invocation

步骤0：进入规划模式并解析调用指令

  1. Call 
    EnterPlanMode
    immediately -- no files are written until the plan is approved in Step 6.
  2. Parse the invocation: 
    • /mvp
      (bare) -- start the full workflow from Step 1
    • /mvp a fitness tracker
      -- seed description provided, use it as the answer to Step 1's seed question and skip that question
    • /mvp --resume
      -- Glob for existing docs in 
      ./docs/mvp/
      , 
      ./plans/
      , 
      ./mvp/
      . If found, read them and resume from the appropriate step based on what's already documented. If not found, start fresh from Step 1.
  1. 立即调用
    EnterPlanMode
    ——在步骤6中获得计划批准前，不得写入任何文件。
  2. 解析调用指令： 
    • /mvp
      （无参数）——从步骤1开始完整工作流程
    • /mvp a fitness tracker
      ——已提供初始描述，将其作为步骤1初始问题的答案，并跳过该问题
    • /mvp --resume
      ——在
      ./docs/mvp/
      、
      ./plans/
      、
      ./mvp/
      目录下查找现有文档。如果找到，读取文档并根据已完成的内容从对应步骤恢复流程；如果未找到，从步骤1重新开始。

Step 1: Problem Space Exploration

步骤1：问题领域探索

Deep requirements gathering via 
AskUserQuestion
with concrete options. Ask ALL of these questions, adapting options based on prior answers:
  1. Seed question (skip if a description was provided in the invocation):
    What are you building? Describe the problem or product in a few sentences.
  2. Target users (select one):
    • Yourself / Developers / Internal team / End consumers (B2C) / Businesses (B2B)
  3. Problem severity (select one):
    • Hair on fire / Annoying / Nice to have / New behavior
  4. Existing solutions (multiSelect):
    • Nothing / Manual processes / Competitors / Internal tools / Open source
  5. Scale expectations (select one):
    • Just me / Small group (<100) / Medium (hundreds-thousands) / Large (10k+) / Unknown
After gathering all answers, produce a Problem Brief and confirm it with the user via 
AskUserQuestion
:
markdown
undefined
通过
AskUserQuestion
工具，结合具体选项进行深度需求收集。根据之前的答案调整选项，必须询问以下所有问题：
  1. 初始问题（如果调用指令中已提供描述则跳过）：
    你正在构建什么？用几句话描述问题或产品。
  2. 目标用户（选择一项）：
    • 你自己 / 开发者 / 内部团队 / 终端消费者（B2C） / 企业客户（B2B）
  3. 问题严重程度（选择一项）：
    • 紧急需求 / 轻微困扰 / 锦上添花 / 全新需求
  4. 现有解决方案（可多选）：
    • 无 / 手动流程 / 竞品 / 内部工具 / 开源方案
  5. 规模预期（选择一项）：
    • 仅个人使用 / 小团队（<100人） / 中等规模（数百至数千人） / 大规模（1万+人） / 未知
收集所有答案后，生成问题简报，并通过
AskUserQuestion
工具与用户确认：
markdown
undefined

Problem Brief

问题简报

Product: {one-line description} Target users: {audience} Core problem: {the pain being solved} Current alternatives: {what exists today} Scale: {expected scale} Key insight: {what makes this solution different/better}

Ask: "Does this Problem Brief capture your vision correctly? (Yes / Adjust -- tell me what to change)"
产品： {一句话描述} 目标用户： {受众} 核心问题： {要解决的痛点} 当前替代方案： {现有解决方案} 规模： {预期规模} 核心优势： {本解决方案的差异化优势}

询问：“这份问题简报是否准确传达了你的愿景？（是 / 需要调整——告诉我修改内容）”

Step 2: Requirements Deep-Dive

步骤2：需求深度挖掘

Targeted questions based on Step 1 answers. Use 
AskUserQuestion
for each:
  1. Core workflows -- Ask:
    What is the SINGLE most important thing a user does?
    Then ask clarifying sub-questions based on the answer:
    • Does this require authentication?
    • Is it real-time or async?
    • What data does it involve (structured, unstructured, files)?
    Repeat for up to 2 more workflows: "What's the SECOND most important workflow?" and "Any third critical workflow?"
  2. Technical constraints (multiSelect):
    Which of these apply to your product?
    Options: Auth required / Real-time updates / Offline support / Mobile-first / API integrations / Data persistence / Multi-tenancy / Privacy compliance (GDPR etc.) / None of these
  3. Anti-goals (multiSelect):
    What should we explicitly EXCLUDE from the MVP? These are common features that add scope without proving the core idea.
    Options: Admin dashboard / Analytics / Payments / Notifications / Mobile app / User customization / Social features / Search / Internationalization
基于步骤1的答案提出针对性问题，每个问题都使用
AskUserQuestion
工具：
  1. 核心工作流程——询问：
    用户最核心的操作是什么？
    然后根据答案提出澄清性子问题：
    • 是否需要身份验证？
    • 是实时操作还是异步操作？
    • 涉及哪些数据（结构化、非结构化、文件）？
    最多重复询问2个次要工作流程：“第二重要的工作流程是什么？”以及“是否有第三个关键工作流程？”
  2. 技术约束（可多选）：
    以下哪些约束适用于你的产品？
    选项：需要身份验证 / 实时更新 / 离线支持 / 移动端优先 / API集成 / 数据持久化 / 多租户 / 隐私合规（如GDPR） / 无以上约束
  3. 非目标功能（可多选）：
    哪些功能应明确排除在MVP之外？这些是常见但会增加范围却无法验证核心价值的功能。
    选项：管理后台 / 数据分析 / 支付功能 / 通知功能 / 移动应用 / 用户自定义 / 社交功能 / 搜索功能 / 国际化

Step 3: Technical Architecture

步骤3：技术架构设计

Architecture questions tailored to the product type. Use 
AskUserQuestion
for each:
  1. Application type (select one):
    • Web app / CLI tool / API service / Mobile app / Desktop app / Library/SDK
  2. Framework (options based on app type):
    For Web app: Next.js / SvelteKit / Remix / Plain React + Vite / Astro / Other For CLI tool: Node.js (Commander) / Python (Click/Typer) / Rust (Clap) / Go (Cobra) / Other For API service: Express / Fastify / FastAPI / Actix / Go net/http / Other For Mobile app: React Native / Flutter / Swift / Kotlin / Other For Desktop app: Electron / Tauri / Other For Library/SDK: TypeScript / Python / Rust / Go / Other
    Mark the best fit as "(Recommended)" based on requirements gathered in Steps 1-2. Explain why in one sentence.
  3. Database (select one):
    • PostgreSQL / SQLite / MongoDB / Redis / None (stateless) / Other
    • Recommend based on scale expectations and data model needs from Step 2.
  4. Deployment (select one):
    • Cloudflare Workers / Vercel / AWS / Self-hosted / Local only / Other
  5. Architecture pattern (select one):
    • Monolith (Recommended for MVP) / Microservices / Serverless functions / Hybrid
After gathering, add a Tech Stack section and confirm with the user:
markdown
undefined
针对产品类型提出架构相关问题，每个问题都使用
AskUserQuestion
工具：
  1. 应用类型（选择一项）：
    • Web应用 / CLI工具 / API服务 / 移动应用 / 桌面应用 / 库/SDK
  2. 开发框架（根据应用类型提供选项）：
    Web应用：Next.js / SvelteKit / Remix / Plain React + Vite / Astro / 其他 CLI工具：Node.js (Commander) / Python (Click/Typer) / Rust (Clap) / Go (Cobra) / 其他 API服务：Express / Fastify / FastAPI / Actix / Go net/http / 其他 移动应用：React Native / Flutter / Swift / Kotlin / 其他 桌面应用：Electron / Tauri / 其他 库/SDK：TypeScript / Python / Rust / Go / 其他
    根据步骤1-2收集的需求，将最适合的框架标记为“（推荐）”，并用一句话说明原因。
  3. 数据库（选择一项）：
    • PostgreSQL / SQLite / MongoDB / Redis / 无（无状态） / 其他
    • 根据步骤2中的规模预期和数据模型需求推荐合适的数据库。
  4. 部署方式（选择一项）：
    • Cloudflare Workers / Vercel / AWS / 自托管 / 仅本地运行 / 其他
  5. 架构模式（选择一项）：
    • 单体架构（MVP推荐） / 微服务 / 无服务器函数 / 混合架构
收集所有答案后，添加技术栈部分，并与用户确认：
markdown
undefined

Tech Stack

技术栈

Type: {app type} Framework: {framework} Database: {database} Deployment: {platform} Architecture: {pattern} Key rationale: {why these choices fit the requirements}

Ask: "Does this tech stack look right? (Yes / Adjust -- tell me what to change)"

---
类型： {应用类型} 框架： {开发框架} 数据库： {数据库} 部署平台： {部署方式} 架构模式： {架构模式} 核心依据： {这些选择符合需求的原因}

询问：“这个技术栈是否合适？（是 / 需要调整——告诉我修改内容）”

---

Phase 2: Design (Steps 4-6)

第二阶段：设计规划（步骤4-6）

Step 4: Feature Ideation (Agent-Powered)

步骤4：功能构思（Agent驱动）

Deploy 2 
Task
agents in parallel (both with 
Plan
subagent_type) with the full context from Steps 1-3.
Construct the prompts from the templates in 
AGENT_PROMPTS.md
(located in this skill's directory). Read that file to get the prompt templates.
Agent 1: Product Architect
  • Proposes a structured feature set organized by user workflow
  • For each feature: name, description, complexity (S/M/L), dependencies, MVP-essential vs enhancement
  • Considers how the tech stack choices enable or constrain features
Agent 2: Domain Explorer
  • Thinks from the user's perspective
  • Suggests features the user hasn't considered: onboarding UX, error states as features, data lifecycle (import/export/backup), sharing/collaboration, accessibility, admin needs
  • Outputs "likely needed" vs "nice surprise" categories
After both agents return, synthesize their outputs into a unified, deduplicated feature list. Merge overlapping suggestions, preserve the best description, and track the source of each feature.
并行部署2个
Task
Agent（均设置
Plan
子代理类型），并传入步骤1-3的全部上下文信息。
根据本技能目录下
AGENT_PROMPTS.md
中的模板构建提示词，请读取该文件获取提示词模板。
Agent 1：产品架构师
  • 提出按用户工作流程组织的结构化功能集合
  • 每个功能包含：名称、描述、复杂度（S/M/L）、依赖关系、MVP核心功能 vs 增强功能
  • 考虑技术栈选择对功能的支持或限制
Agent 2：领域探索师
  • 从用户视角思考问题
  • 提出用户未考虑到的功能：引导页UX、错误状态优化、数据生命周期（导入/导出/备份）、分享/协作、可访问性、管理需求
  • 将功能分为“可能需要”和“惊喜功能”两类
两个Agent返回结果后，将其合成为统一、去重的功能列表。合并重叠建议，保留最佳描述，并跟踪每个功能的来源。

Step 5: Feature Presentation & Prioritization

步骤5：功能展示与优先级排序

Present the unified feature table to the user:
markdown
undefined
向用户展示统一的功能表格：
markdown
undefined

Proposed Features

建议功能列表

#FeatureDescriptionComplexitySourceSuggested Tier
1User authEmail/password loginMUserMVP
2DashboardMain overview screenMProduct ArchitectMVP
3CSV exportDownload dataSDomain ExplorerFuture

**Source** column values:

- `User` -- explicitly requested by the user
- `Inferred` -- derived from requirements (e.g., auth implied by multi-user)
- `Suggested` -- proposed by an agent

Then use `AskUserQuestion` twice:

1. (multiSelect): "Which features MUST be in your MVP? (select all that apply)"
   - List all features as options

2. "Any features to ADD that are missing, or REMOVE entirely? (Add / Remove / Looks good)"
   - If Add: ask what to add, then incorporate and re-present
   - If Remove: ask which to remove
序号功能名称描述复杂度来源建议层级
1用户身份验证邮箱/密码登录M用户MVP
2仪表盘主概览页面M产品架构师MVP
3CSV导出下载数据S领域探索师未来版本

**来源**列的取值：

- `User`——用户明确要求的功能
- `Inferred`——从需求中推导的功能（如多用户场景隐含身份验证需求）
- `Suggested`——Agent提出的功能

然后通过`AskUserQuestion`工具询问两个问题：

1. （可多选）：“哪些功能必须包含在你的MVP中？（选择所有适用项）”
   - 列出所有功能作为选项

2. “是否需要添加缺失的功能，或移除现有功能？（添加 / 移除 / 无需调整）”
   - 如果选择添加：询问要添加的功能，将其加入列表后重新展示
   - 如果选择移除：询问要移除的功能

Step 6: Scope Definition & Approval

步骤6：范围定义与批准

Organize features into two sections:
MVP Scope -- ordered by implementation sequence respecting dependencies:
markdown
undefined
将功能分为两部分：
MVP范围——按实现顺序排列，需考虑依赖关系：
markdown
undefined

MVP Scope (v1)

MVP范围（v1版本）

OrderFeatureDepends OnComplexityNotes
1Data models--SFoundation
2User authData modelsMRequired by most features

**Future Roadmap** -- grouped into release waves:

```markdown
顺序功能名称依赖项复杂度说明
1数据模型--S基础功能
2用户身份验证数据模型M大多数功能都需要依赖

**未来路线图**——按发布阶段分组：

```markdown

Future Roadmap

未来路线图

v1.1 -- Quick Wins

v1.1版本——快速迭代功能

| Feature | Complexity | Why deferred |
| 功能 | 复杂度 | 延期原因 |

v1.2 -- Enhanced Experience

v1.2版本——增强体验功能

| Feature | Complexity | Why deferred |
| 功能 | 复杂度 | 延期原因 |

Backlog -- Investigate Later

待办清单——后续探索

| Feature | Complexity | Why deferred |

Present both sections to the user, then use `AskUserQuestion` as a **hard approval gate**:

> Ready to finalize this plan? Pick an option:
>
> 1. **Approve** -- proceed to documentation (Recommended)
> 2. **Adjust scope** -- move features between MVP and future
> 3. **Adjust order** -- resequence the implementation plan
> 4. **Deep-dive** -- expand a specific feature before approving

Handle each option:

- **Approve**: Call `ExitPlanMode` to unlock file writes, proceed to Step 7.
- **Adjust scope**: Ask which features to move and in which direction, update the tables, re-present, and ask for approval again.
- **Adjust order**: Ask what to resequence, update, re-present, and ask again.
- **Deep-dive**: Expand the specified feature with more detail (user stories, edge cases, technical considerations), then ask for approval again.

Loop until the user approves.

On approval, call `ExitPlanMode` to unlock file writes.

---
| 功能 | 复杂度 | 延期原因 |

向用户展示这两部分内容，然后通过`AskUserQuestion`工具设置**强制批准关卡**：

> 准备好最终确定这份计划了吗？选择一个选项：
>
> 1. **批准**——进入文档撰写阶段（推荐）
> 2. **调整范围**——在MVP和未来版本之间移动功能
> 3. **调整顺序**——重新排列实现计划的顺序
> 4. **深入探索**——在批准前展开某个特定功能的细节

处理每个选项：

- **批准**：调用`ExitPlanMode`解锁文件写入权限，进入步骤7。
- **调整范围**：询问要移动的功能及方向，更新表格后重新展示并再次请求批准。
- **调整顺序**：询问要重新排序的内容，更新后重新展示并再次请求批准。
- **深入探索**：展开指定功能的细节（用户故事、边缘情况、技术考量），然后再次请求批准。

循环此过程直到用户批准。

获得批准后，调用`ExitPlanMode`解锁文件写入权限。

---

Phase 3: Document (Steps 7-8)

第三阶段：文档生成（步骤7-8）

Step 7: Documentation Output

步骤7：文档输出

First, ask where to save using 
AskUserQuestion
:
Where should I save the MVP planning documents?
  1. ./docs/mvp/
    (Recommended)
  2. ./plans/
  3. ./mvp/
  4. Custom path
Create the chosen directory if it doesn't exist.
Produce 5 artifacts:
首先通过
AskUserQuestion
工具询问保存位置：
MVP规划文档应保存到哪里？
  1. ./docs/mvp/
    （推荐）
  2. ./plans/
  3. ./mvp/
  4. 自定义路径
如果所选目录不存在则创建该目录。
生成5种文档：

1. 
OVERVIEW.md
-- Product Vision & Tech Stack

1. 
OVERVIEW.md
——产品愿景与技术栈

markdown
undefined
markdown
undefined

{Product Name}

{产品名称}

Vision

愿景

{2-3 sentence product vision}
{2-3句话的产品愿景}

Problem Brief

问题简报

Product: {one-line description} Target users: {audience} Core problem: {the pain being solved} Current alternatives: {what exists today} Scale: {expected scale} Key insight: {what makes this solution different/better}
产品： {一句话描述} 目标用户： {受众} 核心问题： {要解决的痛点} 当前替代方案： {现有解决方案} 规模： {预期规模} 核心优势： {本解决方案的差异化优势}

Tech Stack

技术栈

Type: {app type} Framework: {framework} Database: {database} Deployment: {platform} Architecture: {pattern} Key rationale: {why these choices fit}
类型： {应用类型} 框架： {开发框架} 数据库： {数据库} 部署平台： {部署方式} 架构模式： {架构模式} 核心依据： {这些选择符合需求的原因}

Product Principles

产品原则

  1. {principle 1}
  2. {principle 2}
  3. {principle 3}
  1. {原则1}
  2. {原则2}
  3. {原则3}

Competitive Landscape

竞争格局

AlternativeStrengthsWeaknessesOur Differentiator
undefined
替代方案优势劣势我们的差异化优势
undefined

2. 
FEATURES.md
-- Complete Feature Catalog

2. 
FEATURES.md
——完整功能目录

Every feature (MVP + future) with user stories, acceptance criteria, complexity, dependencies, and tier.
markdown
undefined
包含所有功能（MVP + 未来版本），并提供用户故事、验收标准、复杂度、依赖关系和层级。
markdown
undefined

Feature Catalog

功能目录

MVP Features

MVP功能

{Feature Name}

{功能名称}

  • Tier: MVP
  • Complexity: {S/M/L}
  • Dependencies: {list or none}
  • Source: {User/Inferred/Suggested}
User Story: As a {user type}, I want to {action} so that {benefit}.
Acceptance Criteria:
  • {criterion 1}
  • {criterion 2}
  • {criterion 3}
  • 层级： MVP
  • 复杂度： {S/M/L}
  • 依赖项： {列表或无}
  • 来源： {User/Inferred/Suggested}
用户故事： 作为{用户类型}，我想要{操作}，以便{收益}。
验收标准：
  • {标准1}
  • {标准2}
  • {标准3}

Future Features

未来功能

{Feature Name}

{功能名称}

...
undefined
...
undefined

3. 
MVP_SCOPE.md
-- Ordered Implementation Plan

3. 
MVP_SCOPE.md
——有序实现计划

markdown
undefined
markdown
undefined

MVP Implementation Plan

MVP实现计划

Implementation Sequence

实现顺序

OrderFeatureDepends OnComplexityNotes
1...--S...
顺序功能名称依赖项复杂度说明
1...--S...

Architecture Decisions

架构决策

  • {Decision 1 and rationale}
  • {Decision 2 and rationale}
  • {决策1及依据}
  • {决策2及依据}

Explicitly Out of Scope

明确排除的范围

These items are intentionally excluded from the MVP:
  • {item 1} -- {reason}
  • {item 2} -- {reason}
以下内容被有意排除在MVP之外：
  • {项1}——{原因}
  • {项2}——{原因}

Mini-Specs

迷你规格说明

{Feature 1}

{功能1}

{Brief technical approach -- 3-5 bullets on how to implement}
{简要技术实现方案——3-5条要点}

{Feature 2}

{功能2}

...
undefined
...
undefined

4. 
ROADMAP.md
-- Future Release Waves

4. 
ROADMAP.md
——未来发布路线图

markdown
undefined
markdown
undefined

Product Roadmap

产品路线图

v1.1 -- Quick Wins

v1.1版本——快速迭代功能

FeatureComplexityWhy DeferredTrigger to Reconsider
功能复杂度延期原因重新考虑的触发条件

v1.2 -- Enhanced Experience

v1.2版本——增强体验功能

FeatureComplexityWhy DeferredTrigger to Reconsider
功能复杂度延期原因重新考虑的触发条件

Backlog -- Investigate Later

待办清单——后续探索

FeatureComplexityWhy DeferredTrigger to Reconsider
功能复杂度延期原因重新考虑的触发条件

Open Questions

未解决问题

  • {question 1}
  • {question 2}
undefined
  • {问题1}
  • {问题2}
undefined

5. 
DELIVERABLES.md
-- Living Progress Tracker

5. 
DELIVERABLES.md
——动态进度跟踪器

Nested markdown checklists with complexity tags inline:
markdown
undefined
嵌套的markdown勾选列表，内联复杂度标签：
markdown
undefined

Deliverables Tracker

交付跟踪器

MVP (v1)

MVP（v1版本）

  • Data models (S) -- Define core schemas
    • User model
    • {Domain model 1}
    • {Domain model 2}
  • User auth (M) -- Email/password authentication
    • Registration flow
    • Login flow
    • Session management
  • 数据模型 (S) —— 定义核心 schema
    • 用户模型
    • {领域模型1}
    • {领域模型2}
  • 用户身份验证 (M) —— 邮箱/密码验证
    • 注册流程
    • 登录流程
    • 会话管理

Future

未来版本

  • v1.1: {Feature} (S)
  • v1.1: {Feature} (M)
  • v1.2: {Feature} (L)
  • Backlog: {Feature} (L)
undefined
  • v1.1版本：{功能} (S)
  • v1.1版本：{功能} (M)
  • v1.2版本：{功能} (L)
  • 待办清单：{功能} (L)
undefined

Step 8: Summary & Handoff

步骤8：总结与交接

Print a summary of what was created:
markdown
undefined
打印已创建内容的总结：
markdown
undefined

MVP Plan: {product name}

MVP计划：{产品名称}

Product: {one-line description} Tech stack: {framework} + {database} on {deployment} MVP features: {count} features ({S count} small, {M count} medium, {L count} large) Future features: {count} features across {wave count} release waves Documentation: {path}
产品： {一句话描述} 技术栈： {开发框架} + {数据库} 部署在{部署平台} MVP功能： {数量}个功能（{S数量}个小型，{M数量}个中型，{L数量}个大型） 未来功能： {数量}个功能，分为{阶段数量}个发布阶段 文档路径： {路径}

Files Created

已创建文件

FilePurpose
{path}/OVERVIEW.mdProduct vision and tech stack
{path}/FEATURES.mdComplete feature catalog with specs
{path}/MVP_SCOPE.mdMVP implementation plan and sequence
{path}/ROADMAP.mdFuture release roadmap
{path}/DELIVERABLES.mdImplementation checklist tracker
文件用途
{path}/OVERVIEW.md产品愿景与技术栈
{path}/FEATURES.md完整功能目录及规格说明
{path}/MVP_SCOPE.mdMVP实现计划与顺序
{path}/ROADMAP.md未来发布路线图
{path}/DELIVERABLES.md实现进度勾选列表

What's Next?

下一步操作

  1. Deep-dive into a specific feature -- I'll expand the spec
  2. Run /init-repo -- scaffold the project infrastructure
  3. Start building -- pick the first MVP feature and begin
  4. Refine scope -- revisit prioritization or add features
  5. Export -- create GitHub Issues, Linear tasks, etc. from the plan
undefined
  1. 深入探索某个特定功能——我会展开其规格说明
  2. 运行/init-repo——搭建项目基础设施
  3. 开始构建——选择第一个MVP功能并启动开发
  4. 调整范围——重新审视优先级或添加功能
  5. 导出——将计划转换为GitHub Issues、Linear任务等
undefined

Guidelines

指导原则

  • Call 
    EnterPlanMode
    at the very start -- no file writes until scope is approved in Step 6
  • Call 
    ExitPlanMode
    only after the user explicitly approves the plan
  • Ask before assuming -- use 
    AskUserQuestion
    with concrete options everywhere, not open-ended prompts
  • Features from agents must be clearly marked as 
    Suggested
    in the Source column
  • Think step-by-step about dependencies and edge cases before presenting any feature list
  • Resist scope creep -- actively push back when the user tries to put everything in MVP. A good MVP is small and focused.
  • Balanced suggestions -- practical core features with some creative ideas; ambitious ones clearly flagged so the user can easily defer them
  • Markdown checklists for deliverable tracking -- no external tools needed
  • Never write code -- this skill produces planning documents only
  • Suggest 
    /init-repo
    as the natural next step for scaffolding the project infrastructure
  • If the user asks to deep-dive into a feature, expand with user stories, edge cases, technical approach, and acceptance criteria
  • The "What's Next?" menu is important -- always include it at the end
  • 从一开始就调用
    EnterPlanMode
    ——在步骤6获得范围批准前，不得写入任何文件
  • 仅在用户明确批准计划后调用
    ExitPlanMode
  • 避免主观假设——所有地方都使用
    AskUserQuestion
    工具并提供具体选项，而非开放式问题
  • Agent提出的功能必须在“来源”列明确标记为
    Suggested
  • 在展示任何功能列表前，逐步思考依赖关系和边缘情况
  • 抵制范围蔓延——当用户试图将所有功能都放入MVP时，主动提出反对。优秀的MVP应小巧且聚焦。
  • 平衡建议——提供实用的核心功能和一些创意想法；将雄心勃勃的功能明确标记，方便用户延后考虑
  • 使用markdown勾选列表进行交付跟踪——无需外部工具
  • 绝不编写代码——本技能仅生成规划文档
  • 建议使用
    /init-repo
    作为搭建项目基础设施的自然下一步
  • 如果用户要求深入探索某个功能，展开其用户故事、边缘情况、技术实现方法和验收标准
  • “下一步操作”菜单非常重要——必须在末尾包含该部分