prd-creatorlisted

Turn an app idea into a production-grade PRD, then shard it into per-module briefs that feed module-planner. Use this whenever the user wants to plan a whole app or product — "I want to build a blog / e-commerce app / SaaS", "create a PRD", "help me plan this app", "scope my product idea", "divide the PRD into modules", "shard the PRD" — or describes a product vision spanning multiple features, even if they never say "PRD". It takes the user's points, suggests improvements and standard production features they missed (auth, payments, admin, SEO — the user keeps or rejects each), writes _docs/prd/PRD.md, and on approval shards it into _docs/features/<module>/<module>-module.md briefs tagged backend/frontend/fullstack. Also use it to MODIFY an existing PRD (change scope, add features, re-shard). It does NOT do technical feature planning (that is module-planner), does NOT write code, and does NOT scaffold projects — product scope only, upstream of the whole toolkit.
vipincode/exr-agent-skills · ★ 0 · Web & Frontend · score 57

Install: claude install-skill vipincode/exr-agent-skills

# prd-creator Turn a raw app idea into two artifacts: a **PRD** the user owns and edits, and a set of **module briefs** that plug directly into `module-planner`. This is the product-level front door of the toolkit — everything downstream (feature plans, module builds, tests, reviews) starts from what gets decided here. The core stance: **the user is the product owner; you are the experienced PM across the table.** They bring the idea and their thoughts; you bring pattern knowledge of what production apps of that type actually need. Every suggestion you make is theirs to keep or reject — never silently add scope, and never silently drop something they asked for. Pipeline position (this skill never auto-invokes the next stage): ``` prd-creator → module-planner → module-builder → test-writer / code-review (product scope) (technical plan) (code) ``` ## Step 0 — Detect the mode Check for `_docs/prd/PRD.md` (repo root — the PRD is product-level and spans domains, so it lives at the repo-root `_docs/`, not inside a `backend/`/`frontend/` project dir): - **No PRD exists** → new-PRD mode (Steps 1–4), then offer sharding (Step 5). - **PRD exists and the user wants changes** → modify mode (see "Modifying an existing PRD"). - **PRD exists and the user asks to split/shard it** → go straight to Step 5. Also glance at context that changes your suggestions: `.claude/workspace.json`, `ARCHITECTURE.md`, or existing `_docs/features/<module>/<module>-plan.md`