Back to Details

issue-to-prd

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

issue-to-prd

issue-to-prd

ICM procedure: convert a new GitHub issue into a structured PRD or post clarifying questions.
ICM流程：将新的GitHub issue转换为结构化PRD，或发布澄清问题。

Invocation

调用方式

/issue-to-prd {repo} {issue_number}
Example: 
/issue-to-prd fellowship-dev/pylot 123
/issue-to-prd {repo} {issue_number}
示例：
/issue-to-prd fellowship-dev/pylot 123

When to use

使用场景

  • A new issue arrives and needs structuring (triggered by 
    challenge-new-issue
    event rule)
  • A human answered 
    open-questions
    and re-challenge fires (triggered by 
    rechallenge-after-answers
    )
  • Manual invocation to structure a specific issue
  • 新issue创建后需要结构化处理（由
    challenge-new-issue
    事件规则触发）
  • 人工回复了
    open-questions
    后触发重新处理（由
    rechallenge-after-answers
    规则触发）
  • 手动调用以结构化特定issue

What it does

功能说明

7-stage ICM procedure:
  1. 01-read-issue — fetch issue data (title, body, labels, comments)
  2. 02-context-completeness — audit implicit context gaps a fresh agent would miss
  3. 03-assess-clarity — check against 8-section gap checklist → 
    clear
    or 
    needs-questions
  4. 04-failure-modes — predict how an agent can go astray → guardrails for PRD
  5. 05-test-plan — test strategy + prerequisites (pre-merge and post-merge)
  6. 06-ask-or-structure — decision: post questions (exit) OR draft PRD
  7. 07-publish — rewrite issue body with PRD, apply labels
7阶段ICM流程：
  1. 01-read-issue — 获取issue数据（标题、正文、标签、评论）
  2. 02-context-completeness — 检查新手Agent可能会忽略的隐含上下文缺口
  3. 03-assess-clarity — 对照8项缺口清单进行检查 → 标记为
    clear
    （清晰）或
    needs-questions
    （需提问）
  4. 04-failure-modes — 预测Agent可能出现的失误 → 为PRD设置防护规则
  5. 05-test-plan — 测试策略及前提条件（合并前和合并后）
  6. 06-ask-or-structure — 决策：发布问题（退出流程）或草拟PRD
  7. 07-publish — 用PRD重写issue正文，添加对应标签

Exit paths

退出路径

  • Questions path (stage 06): posts GH comment, adds 
    open-questions
    label, stops
  • PRD path (stage 07): rewrites issue body, adds 
    ready-to-work
    + 
    prd-ready
    labels
  • 提问路径（第06阶段）：发布GitHub评论，添加
    open-questions
    标签，终止流程
  • PRD路径（第07阶段）：重写issue正文，添加
    ready-to-work
    和
    prd-ready
    标签

Stage handoffs

阶段交接

Each stage writes to its 
output/handoff.md
. Downstream stages read upstream handoffs. All output directories at 
stages/{stage}/output/
.
每个阶段会将内容写入对应的
output/handoff.md
。下游阶段读取上游的交接文件。 所有输出目录位于
stages/{stage}/output/
。

Execution

执行方式

Run stages sequentially. Read the CONTEXT.md for each stage before executing it. After stage 06, skip stage 07 if questions were posted.
按顺序运行各阶段。执行前请阅读每个阶段的CONTEXT.md文件。 若在第06阶段发布了问题，则跳过第07阶段。

Reference files

参考文件

  • shared/prd-template.md
    — PRD structure (used by stage 06)
  • shared/failure-modes.md
    — common agent pitfall catalog (used by stage 04)
  • stages/03-assess-clarity/references/gap-checklist.md
    — 8-section checklist
  • shared/prd-template.md
    — PRD结构模板（第06阶段使用）
  • shared/failure-modes.md
    — Agent常见失误目录（第04阶段使用）
  • stages/03-assess-clarity/references/gap-checklist.md
    — 8项缺口清单