to-prd

Synthesize a PRD from what you already know. Do NOT interview — extract from context, codebase exploration, and prior decisions. Iterate the artifact in place; commit when the user signs off.

Emission Modes [LOCKED]

Default (file mode): Write to <project-root>/docs/prd/<feature>.md. Idempotent — overwrite on rerun. Use file mode when no flag is passed, when working offline, when the repo has no GitHub remote, or when the user explicitly wants a tracked file.

Flag mode (--emit-issue): Submit via gh issue create --title "PRD: <feature>" --body-file <tmp>. Use only when the user explicitly opts in or the project's convention is issue-tracked PRDs (check <project-root>/CONTRIBUTING.md and .github/ISSUE_TEMPLATE/).

When ambiguous, default to file mode and ask the user one targeted question rather than guessing.

Process

1. Reuse priming if available; explore only when context is thin

If conversation context already covers domain language, naming conventions, and module shape, skip discovery and proceed to step 2. Otherwise dispatch an Explore agent over the codebase. Goal: current architectural state, naming conventions, ADRs, domain language. Read CONTEXT.md, AGENTS.md, docs/adr/, and any UBIQUITOUS_LANGUAGE.md. Use fd -e md . docs/ then bat -P -p -n -r for targeted reads.

2. Identify deep modules

Sketch modules to build or modify. Prefer deep modules — large functionality behind a narrow, stable interface — over shallow modules. Surface 3-7 candidates and their interfaces. Recommend which modules deserve isolated tests; defer to user on edge cases.