pixelastic/to-prd
config/ai/claude/skills/to-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.
$ install --global
skillsauthnpx skillsauth add pixelastic/oroshi to-prdInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 28, 2026, 6:07 AM88.6s2 files scanned
SKILL.md
- name:
- to-prd
- description:
- 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.
To PRD
Overview
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.
Core Workflow
Step 1 — Understand the codebase
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, and respect any ADRs in the area you're touching.
Step 2 — Sketch out
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.
Step 3 — Write the PRD.md
Run prd-end <branchName> via the Bash tool, and parse the JSON output.
Write the PRD to <prdPath>, following the template.
Common Rationalizations
| Rationalization | Reality |
|---|---|
| "I know this codebase, no need to explore" | Recent ADRs and 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 |
Checklist
- [ ] Codebase explored — domain glossary and ADRs identified
- [ ] Deep modules identified — each has a simple, testable interface
- [ ] User confirmed module list matches intent
- [ ] User confirmed which modules get tests
- [ ]
prd-end <branchName>called via Bash tool, JSON output parsed - [ ] PRD.md written to
<prdPath> - [ ] PRD contains all 6 sections present (Problem, Solution, User Stories, Implementation Decisions, Testing Decisions, Out of Scope)
Related Skills
pixelastic/prd
tools
VerifiedTrustedCommunity
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.
38SKILL.mdUpdated Jun 5, 2026
pixelastic/issues
tools
VerifiedTrustedCommunity
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.
38SKILL.mdUpdated Jun 5, 2026
pixelastic/sidequest
documentation
VerifiedTrustedCommunity
Use when user says "sidequest" or "handoff" — compact conversation context into a document for a fresh agent to pick up.
38SKILL.mdUpdated Jun 4, 2026
pixelastic/glossary
development
VerifiedTrustedCommunity
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.
38SKILL.mdUpdated Jun 3, 2026