메뉴
Create a PRD through user interview, codebase exploration, module design, success criteria, risk analysis, and testing strategy. 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 직업 분류 기준
Apply Entity Framework Core patterns for tracking, migrations, retries, bulk operations, DbContext lifetime, query behavior, and database-backed tests. Use when implementing, reviewing, debugging, or optimizing EF Core data access and migration workflows.
Structure or modernize .NET solutions using .slnx, global.json, Directory.Build.props, Central Package Management, SourceLink, NuGet configuration, release metadata, and reproducible build conventions. Use for new solution setup, repository-wide build configuration, SDK pinning, or project-layout migrations.
Build or query a persistent knowledge graph for broad architecture, cross-file relationships, or mixed code-and-document corpora. Use when the user explicitly asks for Graphify or a knowledge graph, when graphify-out already exists and can answer an architecture question, or when persistent cross-session mapping materially helps. Do not trigger for routine code questions, focused audits, or small repository tasks.
Build or standardize Tailwind CSS v4 design systems with CSS-first tokens, variants, reusable components, responsive layouts, forms, theming, and accessibility. Use when creating a component library, defining design tokens, migrating design-system primitives, or removing inconsistent utility patterns.
Teach the user a new skill or concept, within this workspace.
Build .NET integration tests against disposable Docker dependencies with Testcontainers and xUnit. Use for databases, caches, brokers, migration tests, container lifecycle, isolation, wait strategies, CI execution, or replacing infrastructure mocks with real services.
| name | write-a-prd |
| description | Create a PRD through user interview, codebase exploration, module design, success criteria, risk analysis, and testing strategy. 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 about the parts of the plan that remain unclear after repo exploration. Resolve the core problem, target users, success metrics, constraints, non-goals, and major product/technical decisions. Do not invent missing constraints; ask or mark them as TBD.
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.
Use concrete, measurable language. Avoid vague requirements like "fast", "easy", or "intuitive" unless they are backed by measurable acceptance criteria.
The problem that the user is facing, from the user's perspective.
The solution to the problem, from the user's perspective.
3-5 measurable outcomes that define whether the feature worked. Include product, operational, quality, or evaluation metrics as appropriate.
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.
Concrete "done" criteria for the user stories. Prefer externally observable behavior over implementation details.
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.
Any security, privacy, permission, compliance, retention, logging, or data-migration requirements. Mark as N/A only when the feature has no meaningful data or access-control implications.
Include this section only when the feature uses AI. Capture model/tool requirements, grounding/citation needs, failure modes, evaluation strategy, and quality thresholds.
A list of testing decisions that were made. Include:
A description of the things that are out of scope for this PRD.
The main product, technical, migration, security, performance, cost, dependency, and rollout risks, each paired with a mitigation or open decision.
The intended delivery phases, feature flags, migration order, release checks, monitoring, and fallback plan where relevant.
Any further notes about the feature.
