Create PRD

Overview

Generate a problem-first Product Requirements Document with measurable success metrics, testable acceptance criteria, and clearly scoped boundaries. Every PRD starts from the user problem, not the solution.

Workflow

1. Read product context — Scan .chalk/docs/product/ for the product profile (0_product_profile.md), JTBD docs, existing PRDs, and user research. Also check .chalk/docs/engineering/ for architecture docs that inform feasibility. If no product context exists, note that explicitly and work from what the user provides.

2. Accept the feature request — Parse $ARGUMENTS to identify the problem space, target user, and any constraints the user has mentioned. If $ARGUMENTS is vague (e.g., "notifications"), ask one round of clarifying questions before proceeding. Never silently assume the scope.

3. Determine the next file number — Read filenames in .chalk/docs/product/ to find the highest numbered file. The next PRD number is highest + 1.

4. Generate the PRD — Write all sections listed below. Every section is mandatory. Do not leave sections empty or write "TBD" without also adding the item to Open Questions.

5. Cross-reference architecture — Read .chalk/docs/engineering/ to validate that the proposed solution is feasible within the current stack. Flag any new infrastructure, services, or third-party dependencies in the Dependencies section.

6. Flag assumptions — Any statement that is not grounded in an existing doc or explicit user input goes into Open Questions. Be aggressive about surfacing unknowns.