Research to PRD

Turn a research doc into a committed PRD, then publish it so it flows into to-issues → to-pr.

/research → /research-to-prd <doc> → to-issues → to-pr

Core principle

A research doc is a menu — options, evidence, a staged recommendation. A PRD is a commitment — one path, decomposed, with a definition of done. The research already grilled the problem space; what's missing is commitment, not understanding. So do NOT re-grill — force only the few decisions the doc left open, and never pick the scope for the user.

This is why it differs from to-prd (which synthesizes conversation with no interview): it takes the doc as an argument, runs a thin decision gate, and adds a Research Basis section that traces every decision to evidence.

Process

1. Resolve the doc

The argument is the research doc — a path or a fuzzy name. Try in order: an exact path; else glob docs/research/*<arg>* then **/*<arg>*.{md,html}; else propose the newest file in docs/research/. Read it in full (parse through the markup if it's HTML).