PRD OS — Development skill for Claude Code
Standalone PRD + DSSE execution plugin for Claude Code.
How to install PRD OS
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open assafkip/prd-os and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What PRD OS does
Standalone PRD + DSSE execution plugin for Claude Code.
Alternatives in Development
- Create PRD — Create a PRD with 8-section template covering problem to release 7.8k ★
- Ralphy — My Ralph Wiggum setup, an autonomous bash script that runs Claude Code, Codex, OpenCode, Cursor agent, Qwen & 2.8k ★
- /write PRD — Generate a PRD that moves smoothly from strategy to delivery 2.3k ★
README
prd-os
Standalone Claude Code plugin for PRD authoring and DSSE issue execution.
One plugin, one install, one version. Turns rough ideas into reviewable PRDs, gates them through Codex review, triages findings, decomposes into atomic issue specs, and executes those issues with scope enforcement and receipts.
Questions people ask
**How do I stop Claude Code from creeping outside the task scope?** Snapshot the allowed files into state before work starts, then block edits to anything else. prd-os does this at `/issue-approve`: it freezes the `allowed_files` set, and a hook blocks any Edit or Write outside it. Widening scope takes an explicit `/issue-amend` with a written reason, logged to the audit trail.
**How do I get a real PRD workflow inside Claude Code instead of a chat thread?** prd-os adds eleven slash commands that move an idea through a state machine: draft, review, triage, approve, split into atomic issues, then execute each one with scope enforcement and receipts. The PRD ends up as the permanent record of what shipped and what changed mid-build.
**How do I keep Claude from auto-applying code-review findings?** Make triage explicit. prd-os never auto-applies a Codex finding. Every finding needs a disposition: accepted, rejected, or deferred. Rejections and defers require a written rationale on disk. Closeout stays blocked until every in-scope finding is dispositioned.
**How is prd-os different from a PRD template or asking ChatGPT to write a PRD?** A template is a document. prd-os is a state machine with gates. It runs an independent Codex reviewer with cold context, enforces file scope at write time, caps review recursion, and writes a full audit trail. The free plugin here does this. The paid build adds worked examples, setup guides, and support: https://claudedaddy.gumroad.com/l/ayfunm
What it ships
**PRD side (`/prd-*`):**
/prd-start— capture a rough idea as a PRD draft/prd-review— send draft through/codex:review- `/prd-ap
Related Skills
Hybrid Status
Show execution status of all stories in the PRD. Displays batch progress, individual story states, completion
Add To Pickle Jar
Queue the current Pickle Rick session's PRD into the Pickle Jar for batch execution later.
Ralph Init
Initialize a PRD (Product Requirements Document) for structured ralph-loop execution
Ralf
Start Ralf autonomous execution on a .ralf/prd.json file
PRD JSON
Convert Step 5 flow PRDs (prototype mode) or Step 11 PRDs (implementation mode) into the canonical execution b
PRD Orchestrate
Build dependency-aware orchestration plans from the execution backlog under .sigma/orchestration/
Related Agents
Scope Guard (Shared Prompt Block For Tier 2 Agents)
This file is not a standalone agent. It contains the shared scope enforcement prompt text that Tier 2 (executi
Pragmatic Engineer
Council archetype — the execution-reality advisor. Dispatched only by the rc-council skill, which holds each a
Council Machiavelli
Council member. Use standalone for power dynamics & incentive analysis, or via /council for multi-perspective