Back to Details

plan-plus

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Plan Plus — Brainstorming-Enhanced PDCA Planning

Plan Plus — 结合头脑风暴的增强型PDCA规划

Combines brainstorming's intent discovery with bkit PDCA's structured planning to produce higher-quality Plan documents through collaborative dialogue.
结合头脑风暴的意图挖掘与bkit PDCA的结构化规划，通过协作对话产出更高质量的规划文档。

Overview

概述

Plan Plus enhances the standard 
/pdca plan
by adding 4 brainstorming phases before document generation. This ensures that user intent is fully understood, alternatives are explored, and unnecessary features are removed before any implementation begins.
When to use Plan Plus instead of 
/pdca plan
:
  • The feature has ambiguous or complex requirements
  • Multiple implementation approaches are possible
  • You want to ensure YAGNI compliance from the start
  • The feature involves significant architectural decisions
Plan Plus 在标准 
/pdca plan
的基础上，在生成文档前新增了4个头脑风暴阶段。这确保在任何实施工作开始前，已充分理解用户意图、探索了备选方案，并剔除了不必要的功能。
何时使用Plan Plus而非 
/pdca plan
：
  • 功能需求模糊或复杂
  • 存在多种实现方案
  • 希望从一开始就确保符合YAGNI原则
  • 功能涉及重大架构决策

HARD-GATE

硬性要求（HARD-GATE）

<HARD-GATE> Do NOT write any code, scaffold any project, or invoke any implementation skill until this entire process is complete and the user has approved the Plan document. This applies to EVERY feature regardless of perceived simplicity. A "simple" feature still goes through this process — the design can be short, but you MUST present it and get approval. </HARD-GATE>
<HARD-GATE> 在整个流程完成且用户批准规划文档前，不得编写任何代码、搭建任何项目框架或调用任何实现类工具。无论功能看起来多么简单，这一要求适用于所有功能。即使是“简单”功能也必须经过该流程——设计可以简短，但必须提交并获得批准。 </HARD-GATE>

Process Flow

流程步骤

Phase 0: Context Exploration (automatic)
    ↓
Phase 1: Intent Discovery (1 question at a time)
    ↓
Phase 2: Alternatives Exploration (2-3 approaches)
    ↓
Phase 3: YAGNI Review (multiSelect verification)
    ↓
Phase 4: Incremental Design Validation (section-by-section)
    ↓
Phase 5: Plan Document Generation (plan-plus.template.md)
    ↓
Phase 6: Next Steps → /pdca design {feature}
阶段0：背景探索（自动执行）
    ↓
阶段1：意图挖掘（每次一个问题）
    ↓
阶段2：备选方案探索（2-3种方案）
    ↓
阶段3：YAGNI评审（多选验证）
    ↓
阶段4：增量设计验证（逐节确认）
    ↓
阶段5：规划文档生成（使用plan-plus.template.md）
    ↓
阶段6：下一步 → /pdca design {feature}

Phase Details

阶段详情

Phase 0: Project Context Exploration (Automatic)

阶段0：项目背景探索（自动执行）

Before asking any questions, explore the current project state:
  1. Read CLAUDE.md, package.json, pom.xml, etc. for project information
  2. Check recent 5 git commits (understand current work direction)
  3. Check existing 
    docs/01-plan/
    documents (prevent duplication)
  4. Check 
    .bkit-memory.json
    (check ongoing PDCA status)
Share exploration results briefly: "I've reviewed the current project state: ..."
在提出任何问题前，先探索当前项目状态：
  1. 读取CLAUDE.md、package.json、pom.xml等文件获取项目信息
  2. 查看最近5条git提交记录（了解当前工作方向）
  3. 检查现有
    docs/01-plan/
    文档（避免重复工作）
  4. 查看
    .bkit-memory.json
    （检查PDCA流程的当前状态）
简要分享探索结果：“我已查看当前项目状态：……”

Phase 1: Intent Discovery (Brainstorming Style)

阶段1：意图挖掘（头脑风暴式）

Principle: One question at a time, prefer multiple choice
Use 
AskUserQuestion
tool to discover the following in order:
原则：每次只提一个问题，优先使用选择题
使用
AskUserQuestion
工具按顺序挖掘以下信息：

Q1. Core Purpose

Q1. 核心目标

"What is the core problem this feature solves?"
  • Provide 3-4 choices (inferred from project context)
  • Always include a custom input option
“该功能解决的核心问题是什么？”
  • 提供3-4个选项（根据项目背景推断）
  • 始终包含自定义输入选项

Q2. Target Users

Q2. 目标用户

"Who will primarily use this feature?"
  • Admin / End user / Developer / External system
“谁将是该功能的主要使用者？”
  • 管理员 / 终端用户 / 开发人员 / 外部系统

Q3. Success Criteria

Q3. 成功标准

"What criteria would indicate this feature is successful?"
  • Derive specific, measurable criteria
“哪些标准能表明该功能已成功实现？”
  • 推导具体、可衡量的标准

Q4. Constraints (only when needed)

Q4. 约束条件（仅在需要时提问）

Conflicts with existing systems, performance requirements, technical constraints, etc.
Important: Minimize questions. Clear features need only Q1-Q2. Only proceed to Q3-Q4 for ambiguous features.
与现有系统的冲突、性能要求、技术限制等
重要提示：尽量减少问题数量。需求清晰的功能仅需提问Q1-Q2。仅对模糊的功能才继续提问Q3-Q4。

Phase 2: Alternatives Exploration (Brainstorming Core)

阶段2：备选方案探索（头脑风暴核心环节）

Always propose 2-3 approaches with trade-offs for each.
Format:
undefined
必须提出2-3种方案，并说明每种方案的优缺点。
格式：
undefined

Approach A: {name} — Recommended

方案A：{名称} — 推荐方案

  • Pros: ...
  • Cons: ...
  • Best for: ...
  • 优点：……
  • 缺点：……
  • 适用场景：……

Approach B: {name}

方案B：{名称}

  • Pros: ...
  • Cons: ...
  • Best for: ...
  • 优点：……
  • 缺点：……
  • 适用场景：……

Approach C: {name} (optional)

方案C：{名称}（可选）

  • Pros: ...
  • Cons: ...

> Present the recommended approach first with clear reasoning.
> Use AskUserQuestion to let the user choose.
  • 优点：……
  • 缺点：……

> 优先展示推荐方案并给出明确理由。使用AskUserQuestion工具让用户选择。

Phase 3: YAGNI Review (Brainstorming Core)

阶段3：YAGNI评审（头脑风暴核心环节）

Perform a YAGNI (You Ain't Gonna Need It) review on the selected approach:
Use AskUserQuestion with 
multiSelect: true
: "Select only what is essential for the first version:"
List all features and move unselected items to Out of Scope.
Principle: Don't abstract what can be done in 3 lines. Don't design for hypothetical future requirements.
对选定的方案进行YAGNI（You Ain't Gonna Need It，你不会需要它）评审：
使用AskUserQuestion工具并设置
multiSelect: true
： “请选择第一版本中仅需保留的核心内容：”
列出所有功能项，将未选中的项移至“范围外”。
原则：能用3行代码实现的功能就不要抽象设计。不要为假设性的未来需求做设计。

Phase 4: Incremental Design Validation (Brainstorming Style)

阶段4：增量设计验证（头脑风暴式）

Present the design section by section, getting approval after each:
  1. Architecture overview → "Does this direction look right?"
  2. Key components/modules → "Does this structure look right?"
  3. Data flow → "Does this flow look right?"
If the user says "no" to any section, revise only that section and re-present.
逐节展示设计内容，每完成一节就获取用户批准：
  1. 架构概述 → “这个方向是否可行？”
  2. 核心组件/模块 → “这个结构是否合理？”
  3. 数据流 → “这个流程是否正确？”
如果用户对任何一节表示“否”，仅修改该节内容并重新提交确认。

Phase 5: Plan Document Generation

阶段5：规划文档生成

Generate the Plan document using 
plan-plus.template.md
with results from Phases 0-4.
Additional sections (not in standard plan.template.md):
  • User Intent Discovery — Core problem, target users, success criteria from Phase 1
  • Alternatives Explored — Approaches compared in Phase 2
  • YAGNI Review — Included/deferred/removed items from Phase 3
  • Brainstorming Log — Key decisions from Phases 1-4
Output Path: 
docs/01-plan/features/{feature}.plan.md
After document generation, update PDCA status:
  • Create Task: 
    [Plan] {feature}
  • Update .bkit-memory.json: phase = "plan"
结合阶段0-4的结果，使用
plan-plus.template.md
生成规划文档。
新增章节（标准plan.template.md中没有的内容）：
  • 用户意图挖掘 — 来自阶段1的核心问题、目标用户、成功标准
  • 备选方案对比 — 阶段2中对比的各个方案
  • YAGNI评审结果 — 阶段3中确定的保留/推迟/移除项
  • 头脑风暴日志 — 阶段1-4中的关键决策
输出路径：
docs/01-plan/features/{feature}.plan.md
文档生成后，更新PDCA状态：
  • 创建任务：
    [Plan] {feature}
  • 更新.bkit-memory.json：phase = "plan"

Phase 6: Next Steps

阶段6：下一步

After Plan document generation:
Plan Plus completed
Document: docs/01-plan/features/{feature}.plan.md
Next step: /pdca design {feature}
规划文档生成后：
Plan Plus 已完成
文档路径：docs/01-plan/features/{feature}.plan.md
下一步：/pdca design {feature}

Key Principles

核心原则

PrincipleOriginApplication
One question at a timeBrainstormingSequential questions via AskUserQuestion
Explore alternativesBrainstormingMandatory 2-3 approaches in Phase 2
YAGNI ruthlesslyBrainstormingmultiSelect verification in Phase 3
Incremental validationBrainstormingSection-by-section approval in Phase 4
HARD-GATEBrainstormingNo code before approval (entire process)
Context firstBrainstormingAutomatic exploration in Phase 0
原则来源应用场景
每次只提一个问题头脑风暴通过AskUserQuestion工具按顺序提问
探索备选方案头脑风暴阶段2中必须提供2-3种方案
严格执行YAGNI头脑风暴阶段3中使用多选验证
增量式验证头脑风暴逐节获取批准
硬性要求（HARD-GATE）头脑风暴未获批准前不得编写代码（整个流程）
先明确背景头脑风暴阶段0自动执行背景探索

Integration with PDCA

与PDCA的集成

Plan Plus produces the same output as 
/pdca plan
and feeds seamlessly into the standard PDCA cycle:
/plan-plus {feature}     ← Enhanced planning with brainstorming
    ↓
/pdca design {feature}   ← Standard PDCA continues
    ↓
/pdca do {feature}
    ↓
/pdca analyze {feature}
    ↓
/pdca report {feature}
Plan Plus 产出的结果与
/pdca plan
一致，可无缝接入标准PDCA循环：
/plan-plus {feature}     ← 结合头脑风暴的增强型规划
    ↓
/pdca design {feature}   ← 继续执行标准PDCA流程
    ↓
/pdca do {feature}
    ↓
/pdca analyze {feature}
    ↓
/pdca report {feature}

Usage Examples

使用示例

bash
undefined
bash
undefined

Start brainstorming-enhanced planning

启动结合头脑风暴的增强型规划

/plan-plus user-authentication
/plan-plus user-authentication

After Plan Plus completes, continue with standard PDCA

Plan Plus完成后，继续执行标准PDCA流程

/pdca design user-authentication /pdca do user-authentication
undefined
/pdca design user-authentication /pdca do user-authentication
undefined