Requirements Elicitation in Codex With GitHub Awesome Copilot PRD
Turn an underspecified feature request into a trackable Markdown product requirements document using clarifying questions and testable acceptance criteria.
中文Setup for Codex
Use Codex in a scratch repository with GitHub CLI 2.90 or later. This is the MIT-licensed GitHub Awesome Copilot PRD skill as an alternative for the Bitwarden requirements workflow listed here. The output is a local requirements document.
- In the scratch repository, run `gh skill install github/awesome-copilot skills/prd --pin 8ecd5b17f02fe5fbebf35eccd1867265eded811f --agent codex --scope project`.
- Confirm that `.agents/skills/prd/SKILL.md` exists. Open the scratch repository in Codex and select the `prd` skill.
Example task
Give the skill this brief: a neighborhood library wants people to receive an email before a book is due. Ask it to clarify delivery timing and opt-in rules first. Answer 48 hours before the due date and send only to opted-in readers. Ask for the PRD in Markdown.Expected result
The resulting PRD states the reminder timing and opt-in rule. Acceptance criteria cover an opted-in reader receiving a reminder and a reader without consent receiving none. Unresolved items such as retries are identified separately.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Will the PRD skill build the reminder feature?
Its output is the requirements document and the criteria used to review the feature. An implementation plan can use that document as input for a later step.