PRD Writing Skill for Codex
Draft a product requirements document that covers the problem, users, objectives, solution, and release scope. It is useful for turning early notes into a reviewable proposal with assumptions visible.
中文Install in Codex
Use a Codex environment that can discover project skills. The example can be tested in a local project.
- In a temporary directory, run git clone https://github.com/bssm-oss/pm-skills-codex.git. Enter the clone, run git checkout --detach 9f19e3ff563a1cb4024cfb9a290d6002607b9dc9, and review the pinned SKILL.md.
- Copy the entire pm-execution/skills/create-prd folder to .agents/skills/create-prd in your own project, keeping its scripts, templates, and references together.
- Open Codex in that project. Choose the skill with /skills or mention $create-prd, then run the example below. Restart Codex if the list does not refresh.
Example task
Draft a PRD for a team that cleans up duplicate tags every week. The first release can merge only identical names. Permissions and the release date are still open.What to check
The PRD identifies the problem, users, objectives, first-release scope, and assumptions. Identical names remain the first-release limit, while permissions and timing are open questions.
Original SKILL.md on GitHub · Updated
Frequently asked question
Can I draft a PRD from a few rough notes?
Yes. Keep the constraints from the input and mark missing audiences, metrics, or release details for review before treating the draft as final.