메뉴
Turn the current conversation context into a PRD. Use when user wants to create a PRD from the current context.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Transforms a solidified idea, spec file, design doc, exploration output, or grilling session output (from /idea, /grill-me, or /grill-with-docs) into a structured, ticket-ready implementation plan. Use this skill whenever the user wants to turn any requirement, feature idea, spec, or decision into a detailed plan — even if they just say "plan this", "make a plan for", "let's plan out", or pastes raw notes and asks what to build. Always trigger this skill when the input looks like a feature request, system design, product requirement, or grilling output that needs to be broken down into actionable steps. If the user wants to go from idea → plan → build, this is the skill for the plan step.
Kubernetes debugging for pod failures and networking.
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping.
notifies user about status of today (TODOs, emails, repos tracking, news, etc.)
| name | to-prd |
| description | Turn the current conversation context into a PRD. 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.
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.
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.
