Back to Details

gjalla-breakdown

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Wave-Based Task Breakdown

基于阶段（Wave）的任务拆解

Break the feature into sized, dependency-ordered task waves. This makes it easier to keep track of progress as we build so we ensure that we're on track to build what the user expects:
将功能拆解为按依赖关系排序、有明确规模的任务阶段。这能让我们在开发过程中更轻松地跟踪进度，确保我们按用户预期推进开发：

Process

流程

  1. Read the spec: Identify all behavioral requirements and technical changes from the agent plan or gjalla spec.
  2. Identify tasks: Each task should touch 1-2 files and produce a small, reviewable diff that's verifiable.
  3. Map dependencies: Which tasks must complete before others can start?
  4. Group into waves: Tasks within a wave can be done in parallel; waves are sequential.
  1. 阅读规格文档：从Agent计划或gjalla规格中识别所有行为需求和技术变更。
  2. 识别任务：每个任务应涉及1-2个文件，生成可审查、可验证的小型代码差异。
  3. 梳理依赖关系：哪些任务必须先完成，其他任务才能开始？
  4. 分组为阶段：同一阶段内的任务可并行执行；阶段之间按顺序进行。

Task Format

任务格式

Waves of work comprise groups of tasks:
  • ID: W1-T1, W1-T2, W2-T1, etc.
  • Description: One-line summary of what changes.
  • Files: Exact file paths that will be modified or created.
  • Depends On: Task IDs this depends on (within same wave = none).
  • Acceptance: How to verify this task is done.
工作阶段由多组任务构成：
  • ID：W1-T1、W1-T2、W2-T1等。
  • 描述：变更内容的单行摘要。
  • 文件：将被修改或创建的具体文件路径。
  • 依赖项：此任务依赖的任务ID（同一阶段内无依赖）。
  • 验收标准：如何验证任务已完成。

Principles

原则

  • Waves help you group tasks into logical/modular sections so you can put them in an intuitive order. For instance, data model changes might need to come first so the rest of the waves have the foundation they need to build on.
  • The waves and tasks should have a place to mark once complete so that we can easily see our status as we implement.
  • Make sure that docs, verification, tests, etc are included in your breakdown.
To avoid overload, try to keep the total task count under 20 for a single spec; split larger features into multiple specs.
  • 阶段有助于将任务分组为逻辑/模块化部分，以便按直观顺序排列。例如，数据模型变更可能需要优先完成，这样后续阶段才有构建所需的基础。
  • 阶段和任务应有标记完成的地方，以便我们在实现过程中轻松查看状态。
  • 确保任务拆解中包含文档、验证、测试等内容。
为避免任务过载，单个规格文档的总任务数尽量控制在20个以内；较大的功能可拆分为多个规格文档。