elaborate

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Elaborate

任务细化

Goal

目标

  • Task scope, constraints, and risks are fully understood.
  • Concerns raised and resolved.
  • A spec, with concrete testable success criteria, is established.
  • Output is ready to be used as input for task implementation.
  • 全面理解任务范围、约束条件及风险。
  • 提出并解决相关疑问。
  • 制定包含可测试具体成功标准的规格说明。
  • 输出内容可直接作为任务实施的输入。

Prerequisites

前置条件

  • normalize-requirements
    skill available
  • confront
    skill available
  • clarify
    skill available
  • spec
    skill available
  • 具备
    normalize-requirements
    skill
  • 具备
    confront
    skill
  • 具备
    clarify
    skill
  • 具备
    spec
    skill

Input

输入

  • Raw Requirements: freeform description or structured text, OR an itemized batch (each entry
    {id, body}
    ) - keep each entry's
    id
    attached through the
    normalize-requirements
    /
    confront
    /
    clarify
    /
    spec
    chain.
  • 原始需求:自由格式描述或结构化文本,或逐条列出的批量内容(每条格式为
    {id, body}
    )——在
    normalize-requirements
    /
    confront
    /
    clarify
    /
    spec
    流程中需保留每条的
    id

Steps

步骤

Step 1: Normalize Requirements

步骤1:标准化需求

Invoke:
Skill(skill: "normalize-requirements", args: "<raw_requirements>")
调用:
Skill(skill: "normalize-requirements", args: "<raw_requirements>")

Step 2: Confront

步骤2:排查问题

Invoke:
Skill(skill: "confront", args: "<requirements>")
调用:
Skill(skill: "confront", args: "<requirements>")

Step 3: Clarify

步骤3:澄清疑问

Invoke:
Skill(skill: "clarify", args: "<requirements> <codebase> <challenge> <concerns>")
调用:
Skill(skill: "clarify", args: "<requirements> <codebase> <challenge> <concerns>")

Step 4: Spec

步骤4:制定规格

Invoke:
Skill(skill: "spec", args: "<updated_requirements> <addressed_concerns>")
调用:
Skill(skill: "spec", args: "<updated_requirements> <addressed_concerns>")

Output

输出

Markdown format:
  • Updated Requirements
  • Addressed Concerns
  • Spec
Markdown格式:
  • 更新后的需求
  • 已解决的疑问
  • 规格说明