Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
PRP (Product Requirement Prompts)
Rasmus Widing's methodology: a PRP = PRD + curated codebase context + validation commands; skills for PRD, plan, implement, review and an autonomous loop.
Repo (now Wirasm/prp) pushed 2026-10-02; no tagged releases; distributed as the prp-core Claude Code plugin (checked 2026-10-25)
In Spec-driven development
Where it stands apart
- How is it mainly sustained? individual with revenue (paid app, tier, ads, or donations) (11% of 18 others)
- Which coding agents does it work with? one to four named third-party agents (11% of 18 others)
What it shares with most of the community
- Is it actively maintained? active (74% of 19 others)
- How is the main thing licensed? permissive open source (MIT/Apache/BSD) (74% of 19 others)
- Can it run entirely on your own device or infrastructure, without the maker's servers? yes (79% of 19 others)
- Do you need an account to use it? no account (74% of 19 others)
- Who is it for? developers (100% of 19 others)
- Once code exists, what is the spec? a planning scaffold: code becomes the truth after implementation (53% of 19 others)
- What format are specs written in? markdown from templates or free-form (67% of 18 others)
- Where do specs live? plain files in the project repository (89% of 19 others)
- How is the path from idea to code structured? a fixed sequence of phases (e.g. requirements, design, tasks) (53% of 19 others)
- By default, once a plan is approved, how is implementation run? the human drives it, phase by phase or task by task (50% of 18 others)
- What does it offer teams beyond sharing files in git? (if both, pick the paid product) nothing beyond git (50% of 18 others)
Nearest neighbors
- GSD (Get Shit Done) / GSD Core 81% of 16 shared answers match
- Claude Code Spec Workflow 76% of 17 shared answers match
- GitHub Spec Kit 76% of 17 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | active | source 2026-10-25 |
| How is the main thing licensed? | permissive open source (MIT/Apache/BSD) MIT | source 2026-10-25 |
| How is it mainly sustained? | stands apart individual with revenue (paid app, tier, ads, or donations) Individual author; Buy Me a Coffee donations plus paid AI engineering workshops. | source 2026-10-26 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | yes | source 2026-10-25 |
| Do you need an account to use it? | no account Prompts/skills installed locally; needs Claude Code (own login), none with the maker. | source 2026-10-26 |
| Who is it for? | developers | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | Agent Skills (SKILL.md) Agent Skills / Claude plugin format. | source 2026-10-26 |
| Once code exists, what is the spec? | a planning scaffold: code becomes the truth after implementation PRP is 'the minimum viable packet an AI needs'; /prp-prd-update tracks phase status only. | source 2026-10-25 |
| After implementation, what built-in step keeps specs and code aligned? (if several, the first that applies) | a step checks code against the spec (tests, review, or verifier) PRPs carry executable validation commands; /prp-review. | source 2026-10-25 |
| What format are specs written in? | markdown from templates or free-form | source 2026-10-25 |
| Where do specs live? | plain files in the project repository PRPs/ folder; /prp-loop writes plans under ~/.prp/. | source 2026-10-25 |
| Which coding agents does it work with? | stands apart one to four named third-party agents Claude Code. | source 2026-10-25 |
| What form does it mainly ship in? | prompts, skills, or slash commands installed into an agent (even if a CLI installs them) | source 2026-10-25 |
| How is the path from idea to code structured? | a fixed sequence of phases (e.g. requirements, design, tasks) PRD -> plan -> implement -> review. | source 2026-10-25 |
| Does a human approve the spec or plan before code is written? | review is recommended but not enforced | source 2026-10-25 |
| By default, once a plan is approved, how is implementation run? | the human drives it, phase by phase or task by task Commands run one at a time; /prp-loop optionally runs plan -> implement -> review headlessly. | source 2026-10-25 |
| What does it offer teams beyond sharing files in git? (if both, pick the paid product) | nothing beyond git | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/Wirasm/PRPs-agentic-eng · read 2026-10-25
- GitHub · github.com/Wirasm/prp · read 2026-10-25
RSS for this project · Its own release feed
Are you a maintainer? Claiming and correcting projects is coming soon.