Back to Details

concise-planning

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Concise Planning

简洁规划

Goal

目标

Turn a user request into a single, actionable plan with atomic steps.
将用户请求转化为包含原子化步骤的单一可执行计划。

Workflow

工作流程

1. Scan Context

1. 扫描上下文

  • Read 
    README.md
    , docs, and relevant code files.
  • Identify constraints (language, frameworks, tests).
  • 阅读
    README.md
    、文档及相关代码文件。
  • 识别约束条件（语言、框架、测试要求）。

2. Minimal Interaction

2. 最小化交互

  • Ask at most 1–2 questions and only if truly blocking.
  • Make reasonable assumptions for non-blocking unknowns.
  • 仅在遇到真正阻碍时，最多提出1-2个问题。
  • 对于非阻碍性的未知内容，做出合理假设。

3. Generate Plan

3. 生成计划

Use the following structure:
  • Approach: 1-3 sentences on what and why.
  • Scope: Bullet points for "In" and "Out".
  • Action Items: A list of 6-10 atomic, ordered tasks (Verb-first).
  • Validation: At least one item for testing.
使用以下结构：
  • 方法：用1-3句话说明做什么及原因。
  • 范围：用项目符号列出「包含」和「排除」内容。
  • 行动项：列出6-10个原子化、有序的任务（以动词开头）。
  • 验证：至少包含一个测试项。

Plan Template

计划模板

markdown
undefined
markdown
undefined

Plan

Plan

<High-level approach>
<High-level approach>

Scope

Scope

  • In:
  • Out:
  • In:
  • Out:

Action Items

Action Items

[ ] <Step 1: Discovery> [ ] <Step 2: Implementation> [ ] <Step 3: Implementation> [ ] <Step 4: Validation/Testing> [ ] <Step 5: Rollout/Commit>
[ ] <Step 1: Discovery> [ ] <Step 2: Implementation> [ ] <Step 3: Implementation> [ ] <Step 4: Validation/Testing> [ ] <Step 5: Rollout/Commit>

Open Questions

Open Questions

  • <Question 1 (max 3)>
undefined
  • <Question 1 (max 3)>
undefined

Checklist Guidelines

检查清单指南

  • Atomic: Each step should be a single logical unit of work.
  • Verb-first: "Add...", "Refactor...", "Verify...".
  • Concrete: Name specific files or modules when possible.
  • 原子化：每个步骤应为单一逻辑工作单元。
  • 动词开头：例如「添加...」、「重构...」、「验证...」。
  • 具体化：尽可能指定具体文件或模块。