菜单
Create a PRD through user interview, codebase exploration, and module design, then write the PRD to a date-prefixed feature folder under ./docs/plan/ (alongside plan.md if it exists). Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Maak een Jira ticket aan.
Werk een ticket-idee uit tot een compact Nederlands Jira-concept.
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in a date-prefixed folder under ./docs/plan/ (for example ./docs/plan/2026-06-02-feature-name/plan.md). Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
| name | write-a-prd |
| description | Create a PRD through user interview, codebase exploration, and module design, then write the PRD to a date-prefixed feature folder under ./docs/plan/ (alongside plan.md if it exists). Use when user wants to write a PRD, create a product requirements document, or plan a new feature. |
This skill will be invoked when the user wants to create a PRD. You may skip steps if you don't consider them necessary.
Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.
Explore the repo to verify their assertions and understand the current state of the codebase.
Interview the user relentlessly about every aspect of this plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.
Sketch out the major modules you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules that can be tested in isolation.
A deep module (as opposed to a shallow module) 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. Check with the user which modules they want tests written for.
YYYY-MM-DD-feature-name, and save the PRD there as prd.md (for example, ./docs/plan/2026-06-02-split-amsapp-notification-profiles/prd.md).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 implementation decisions that were made. This can include:
Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
A list of testing decisions that were made. Include:
A description of the things that are out of scope for this PRD.
Any further notes about the feature.