메뉴
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | create-prd |
| description | Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context. |
This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.
Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the PRD, and respect any ADRs in the area you're touching.
Sketch out the major components you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep components that can be tested in isolation.
A deep module (as opposed to a shallow components) is one which encapsulates a lot of functionality in a simple, testable interface which rarely changes.
Check with the user that these modules match their expectations.
docs/product/001-<descriptive-title>.md. Use numbering and kebab casing for
the filename of the new PRD you're creating.We use PRDs to describe functional requirements, a solution strategy, and associated features and user stories as you would in an agile project.
The problem that the user is facing, from the user's perspective.
The solution to the problem, from the user's perspective.
A LONG, numbered list of user stories. Each user story should be in the format of:
This list of user stories should be extremely extensive and cover all aspects of the feature.
A list of the risks that are worth considering. These can be technical, organizational, or integration related.
A description of the things that are out of scope for this PRD.
Any further notes that are important for this PRD.