tools/ai/claude/config/skills/prd/SKILL.md
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
npx skillsauth add pixelastic/oroshi prdInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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. Use the project's domain glossary vocabulary throughout the PRD.
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.
Run prd-end <branchName> via the Bash tool, and parse the JSON output.
Write the PRD to <prdPath>, following the template.
Ask the user if they're ready to move to /issues
| Rationalization | Reality |
|---|---|
| "I know this codebase, no need to explore" | Domain terms may have changed. Explore first. |
| "The modules are obvious, no need to check with the user" | Module scope and test scope are separate decisions. Confirm both. |
| "I will write the PRD in the current repo" | Always use prd-end — it handles worktree creation and dep install |
| "I'll call git-worktree-create myself" | Always use prd-end — it handles worktree creation and dep install |
prd-end <branchName> called via Bash tool, JSON output parsed<prdPath>tools
Break a plan, spec, or PRD into independently-grabbable issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
documentation
Use when user says "sidequest" or "handoff" — compact conversation context into a document for a fresh agent to pick up.
development
Use when the user wants to nail down domain terms, resolve terminology ambiguities, or build a shared language for a module or repo. Drills vocabulary one question at a time and writes to the project GLOSSARY.md.
documentation
Use when writing or modifying ZSH functions.