app-prdlisted

# app-prd Turn a raw idea dump into a complete, implementable PRD committed to the target repo. The PRD is the single source of truth every later stage (question refinement, issue filing, workflow execution) builds on — write it so a cold agent could implement from it plus nothing else. ## Input - An idea dump: features, pricing, constraints, platform choices — usually messy prose. Optionally a target repo (defaults to the current checkout). - If no repo exists yet and the user named one, offer `gh repo create <name> --private` before proceeding. ## Steps ### 1. Check repo state `git status`, `git log --oneline -3`, `git remote -v`, `git ls-remote origin`. Three cases: - **Normal repo**: proceed with the standard worktree + PR flow. - **Empty repo with remote** (no commits anywhere): bootstrap first — create `main`, one **empty** initial commit (`git commit --allow-empty -m "Initial commit"` + attribution footer), push. A PR needs a base branch to exist; never put the PRD itself in the bootstrap commit. - **No repo/remote**: confirm repo creation with the user. ### 2. Draft `PRD.md` Structure (adapt section names to the product, keep the skeleton): 1. Header table — product name, repo, platforms, status (**mark the MVP scope explicitly**, e.g. "Draft v0.1 — MVP scope"), last-updated date. 2. **Product Overview** — what it does, for whom, the emotional/business core in plain language. 3. **Goals** — 3-5 bullets. 4. **Platforms & Technology** — a table: each app surfa