メニュー
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Generate a single-file HTML artifact (status report, slide deck, prototype, throwaway editor, flowchart, etc.) and open it in the browser. Use when the user wants a one-off visual artifact instead of markdown — for sharing, reference, or interactive exploration.
Gather context from the codebase and (optionally) the web, then propose multiple ways to move forward with tradeoffs, relative impact, and effort. Use when user wants to explore options, weigh approaches, or asks "what are my options" / "how should I tackle this" before committing to a plan.
Propose a concrete plan to cut a branch and implement a change as one or more atomic commits, grounded in the current codebase and (optionally) outside research. Use when user wants a step-by-step implementation plan, asks "propose a plan" / "how would you implement this", or is ready to move from discussion to execution.
Summarize what shipped over a date range, commit range, or release tag — synthesizes git log, GitHub PRs, and Linear issues into a single markdown brief.
View a Sentry issue by short ID (e.g. PROJECT-123) or URL. Shows details, status, latest event, and tag distribution. Use when user wants to view, check, or look up a Sentry issue, error, or event.
Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
SOC 職業分類に基づく
| name | write-a-prd |
| description | Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature. |
| allowed-tools | Bash(gh *), Bash(git *), Read, Grep, Glob, Agent, mcp__gitea__issue_write |
Create a PRD through user interview, codebase exploration, and module design, then submit as an issue. You may skip steps if not necessary.
git remote -vCheck the git remotes above to determine the platform:
github.com → use gh CLIAsk the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.
Verify their assertions and understand the current state of the codebase.
Interview the user 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. Look for opportunities to extract deep modules that can be tested in isolation.
A deep module encapsulates a lot of functionality behind a simple, testable interface which rarely changes.
Check with the user that these modules match their expectations. Check which modules they want tests written for.
Once you have a complete understanding, use the template below to write the PRD. Submit as an issue:
gh issue createmcp__gitea__issue_write with method createThe 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 should be extensive and cover all aspects of the feature.
A list of implementation decisions made, including:
Do NOT include specific file paths or code snippets — they may become outdated quickly.
Things explicitly out of scope for this PRD.
Any further notes about the feature.