write-a-prdlisted

# Write a PRD Transform settled planning evidence into a product and implementation specification that a fresh `to-plan` session can use without the original conversation. Do not reopen the interview and do not invent missing decisions. ## Source Prefer a `write-planning-brief` artifact passed as an argument. Otherwise use a supplied decision document or the current completed planning conversation. Read referenced research, design, domain, or decision artifacts only where the PRD depends on them. Verify current-state claims against the repository when material. If the source is marked `More decisions required`, produce a draft PRD that preserves every unresolved checkpoint and mark it `Not ready for to-plan`. Do not hide uncertainty inside prose. ## Output Accept an optional output path. Otherwise use the repository's established PRD convention, then `plans/prds/<topic-slug>.md` when `plans/` exists, or `docs/prds/<topic-slug>.md` otherwise. Update an existing PRD for the same topic rather than creating a competing source of truth. Write prose through `write-well` after the factual structure is complete. Style work must not remove requirements, qualifications, citations, or uncertainty. ## Required PRD ```markdown # <Feature> ## PRD status Ready for to-plan | Not ready for to-plan ## Problem statement <The affected actor's problem and consequences.> ## Solution <The resulting capability from the user's perspective.> ## Current state and constraints <Relevant veri