Menu
Generate a Product Requirements Prompt for engineering handoff. Needs an approved PRD. Sensors, link validation, and eval gates.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Visual + UX design defaults for new UIs. Material Design 3, dark/light theme, modern type, Behance-grade polish, i18n (en, pt-BR, es), context-aware favicon. No emojis and no em-dashes; use MD3/modern icons instead. Apply when building something new. Project conventions in .claude/conventions/web.md override these defaults.
Re-install / upgrade harness-kit in the current project to the version bundled in the installed plugin. Run after /plugin update harness-kit fetches a newer plugin version.
Install the harness-kit pipeline into the current project. Copies agents, slash commands, skills, hooks, and the status bar into the project's .claude/, plus AGENTS.md and CLAUDE.md at the repo root. Run after adding the harness-kit plugin from the marketplace.
Design any system from scratch into a rigorous System Design Doc. Generic fallback when no topic-specific playbook fits. Sensors and evals gate.
Design a distributed rate limiter at scale, policy model, enforcement layers (edge/gateway/service), algorithms (token bucket, sliding window), hot keys, fail-open vs fail-closed, multi-region, shadow mode. Topic playbook from the System Design series EP (Rate Limit
Adversarial design review of a System Design Doc. Interrogates the staff questions, finds the cost-explosion and failure risks, returns a verdict. Sensors and evals gate.
| name | prp |
| description | Generate a Product Requirements Prompt for engineering handoff. Needs an approved PRD. Sensors, link validation, and eval gates. |
| user_invocable | true |
Generate a PRP. Follow guides/pipeline.md for retry, approval, and publish.
Source PRD: if user passes a path, use it. Else pick the most recent in .claude/runtime/outputs/pm/prd/. None found, abort. Tell user to run /product-manager:prd first. hooks/pre-prp-check.sh blocks if the PRD lacks the approved marker.
Compute feature_id from the source PRD filename (basename without .md). Save the PRP to .claude/runtime/outputs/pm/prp/{feature_id}.md so it matches.
Before generating, write the phase start marker:
.claude/runtime/outputs/pm/.markers/{feature_id}.prp-generate.start
Content: {"timestamp": "<ISO-8601 UTC now>", "session_id": ""}
Read:
Explore target repos. Ask user for repo paths if not provided. Use the context-strategy tier order:
.claude/runtime/cache/graphify/{slug}/graphify-out/graph.json → query for symbols/callers (much cheaper than grep).claude/runtime/cache/repomix/*.xml → read for full file contentCapture file:line. Never invent paths. If a target repo is large + uncached, suggest the user run /context:graph {repo} before continuing, don't auto-build.
Save to .claude/runtime/outputs/pm/prp/{feature_id}.md.
Sensors: sensors/prp-structure.md, sensors/prp-context-quality.md, sensors/prp-links.md.
Evals: evals/prp-quality.md, evals/prp-context-readiness.md.
After save reply: PRP saved at {path}. Score: {N}/10. Ready for handoff.