Back to Details

briefing

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Do NOT interview the user. Synthesise a tight briefing document from the current conversation context — the PRD, acceptance criteria, slice definition, CONTEXT.md, and any ADRs.
The goal is to give an AFK agent exactly what it needs to execute the slice correctly, and nothing more. Brevity is correctness — a bloated briefing causes drift.
请勿询问用户。需从当前对话上下文（包括PRD、验收标准、任务模块定义、CONTEXT.md以及所有ADRs）中整合出一份简洁的简报文档。
目标是为AFK agent提供完成该任务模块所需的全部必要信息，无多余内容。简洁即准确——冗长的简报会导致偏离方向。

Process

流程

  1. Identify the specific slice being handed off. If ambiguous, ask the user which slice before proceeding.
  2. Read 
    CONTEXT.md
    if it exists. Read any ADRs relevant to the slice's area.
  3. Produce the briefing using the template below.
<briefing-template>
  1. 明确即将交付的特定任务模块。若存在歧义，请先询问用户具体是哪个模块再继续。
  2. 若存在
    CONTEXT.md
    文件，请阅读该文件。阅读与该任务模块领域相关的所有ADRs。
  3. 使用下方模板生成简报。
<briefing-template>

Task

任务

One paragraph. What the agent must build — described as end-to-end behaviour, not layer-by-layer implementation. Reference the slice name and parent PRD issue if available.
一段文字描述。说明Agent必须构建的内容——以端到端行为而非分层实现的方式描述。若有相关信息，请引用任务模块名称和父PRD议题。

What done looks like

完成标准

The acceptance criteria for this slice, verbatim from the 
/acceptance
session if one was run. If not, derive the done conditions from the PRD.
  • Criterion 1
  • Criterion 2
  • Criterion 3
该任务模块的验收标准，若曾开展
/acceptance
会话，则直接使用会话中的原文。若未开展，则从PRD中推导完成条件。
  • 验收标准1
  • 验收标准2
  • 验收标准3

What to know

关键须知

Key context the agent needs that is not obvious from the code:
  • Relevant terms from 
    CONTEXT.md
    (name and one-line definition only)
  • ADRs that apply to this area (decision and reason, one line each)
  • Any constraints, compliance requirements, or non-obvious dependencies
Keep this section short. If something is visible in the code, omit it.
Agent需要了解的、无法从代码中直接获取的关键上下文：
  • CONTEXT.md
    中的相关术语（仅需名称和一行定义）
  • 适用于该领域的ADRs（每项决策及原因各用一行描述）
  • 任何约束条件、合规要求或非显性依赖
请保持此部分简洁。若信息可从代码中查看，则无需列出。

What not to touch

禁止修改内容

Explicit list of files, modules, or behaviours the agent must leave unchanged. Be specific.
  • [module or file]: [why it must not change]
If nothing is off-limits, write "None — but stay within the scope of this slice."
明确列出Agent必须保持不变的文件、模块或行为。请具体说明。
若没有禁止修改的内容，请填写“无——但需严格限定在本任务模块范围内。”

How to verify

验证方式

The steps a human would follow to confirm the slice is working before raising a PR. Should be runnable in under 5 minutes.
  1. [step]
  2. [step]
</briefing-template>
在提交PR之前，人工验证该任务模块是否正常工作的步骤。整个验证过程应在5分钟内完成。
  1. [步骤]
  2. [步骤]
</briefing-template>