issue-to-prd

Original：🇺🇸 English

Translated

Use when converting a new GitHub issue into a structured PRD, or posting clarifying questions when the issue is underspecified.

6installs

Added on2026-08-03

NPX Install

npx skill4agent add fellowship-dev/dogfooded-skills issue-to-prd

ICM procedure: convert a new GitHub issue into a structured PRD or post clarifying questions.

/issue-to-prd {repo} {issue_number}

Example:

/issue-to-prd fellowship-dev/pylot 123

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

7-stage ICM procedure:

01-read-issue — fetch issue data (title, body, labels, comments)
02-context-completeness — audit implicit context gaps a fresh agent would miss
03-assess-clarity — check against 8-section gap checklist →
```
clear
```
or
```
needs-questions
```
04-failure-modes — predict how an agent can go astray → guardrails for PRD
05-test-plan — test strategy + prerequisites (pre-merge and post-merge)
06-ask-or-structure — decision: post questions (exit) OR draft PRD
07-publish — rewrite issue body with PRD, apply labels

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

Each stage writes to its

output/handoff.md

. Downstream stages read upstream handoffs. All output directories at

stages/{stage}/output/

.

Run stages sequentially. Read the CONTEXT.md for each stage before executing it. After stage 06, skip stage 07 if questions were posted.

```
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