菜单
Transforms a conversation or idea into a Product Requirements Document (PRD) with user stories, then submits it as a Forgejo issue. Invoke with /write-a-prd when ready to formalise a feature or initiative.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | write-a-prd |
| description | Transforms a conversation or idea into a Product Requirements Document (PRD) with user stories, then submits it as a Forgejo issue. Invoke with /write-a-prd when ready to formalise a feature or initiative. |
| context | fork |
| allowed-tools | ["Read","Glob","Grep","Bash","Write","Edit"] |
Converts a raw idea or conversation into a structured PRD, grounded in the actual codebase, then submits it as a Forgejo issue for tracking.
Invoke with /write-a-prd when:
git remote get-url origin.Follow the Forgejo API procedure in protocols.md (steps 1–3) to resolve
$FORGEJO_URL, $FORGEJO_TOKEN, $OWNER, and $REPO. Stop if any step
fails — do not attempt issue creation with missing or invalid credentials.
Ask the user to describe the feature or initiative in their own words. Capture:
Load L0 (.abstract.md) and L1 (.overview.md) to understand the project
structure. For areas directly relevant to the feature, read L2 source files.
Verify or correct any claims the user made about how the system currently works.
Run a focused interview (see /grill-me approach) to resolve ambiguities:
Stop when all open questions are resolved.
Identify which parts of the codebase will change and how:
Produce a structured document:
# PRD: <Feature Name>
## Problem
<What problem does this solve? Who is affected?>
## Goals
- <Measurable goal 1>
- <Measurable goal 2>
## Non-goals
- <What this does NOT include>
## User stories
- As a <role>, I want to <action> so that <benefit>.
## Acceptance criteria
- [ ] <Criterion 1>
- [ ] <Criterion 2>
## Technical scope
<Which subsystems change and how. Reference files from .overview.md.>
## Open questions
- <Any unresolved decisions — should be empty before submission>
Use the Create an issue pattern from the Forgejo API section of
protocols.md, with title = "PRD: <Feature Name>" and body = <prd content>.
Print the returned .html_url when done.
A Forgejo issue containing the full PRD, with all acceptance criteria defined and open questions resolved. The issue URL is printed at the end.
Repeatable codebase audit & fix cycle using parallel agent teams. Phases: audit, consolidate, fix, validate. All output stays in docs/.tmp/ (gitignored, never committed). Supports delta-scoped audits via --since=<tag> to review only changed files and their adjacent code paths (cost-effective for continuous use).
Conducts a relentless interview about every aspect of a plan or idea, walking down each branch of the design tree until shared understanding is reached. Invoke with /grill-me before starting any significant design or implementation work.
Converts a PRD (Forgejo issue or local file) into independently executable Forgejo issues organised as vertical slices through integration layers. Invoke with /prd-to-issues <issue-url-or-path>.
Implements a feature or fix using strict red-green-refactor TDD cycles. Confirms interfaces and behaviours before writing any code. Invoke with /tdd <task description>.
Refresh .abstract.md (L0) and .overview.md (L1) across all subsystems. Diff mode (default) updates only subsystems modified since the last index; regeneration mode rewrites everything. Invoke with /context-update when indexes may be stale, before running the large task planning protocol, or after significant refactors.
Incorporate an insight, protocol, or convention from another agent session into the opencode-project-template. Extracts the pattern, places it in the right template file, and bumps the version. Invoke with /template-update when you have a conversation excerpt or lesson learned that should be codified into the template.