Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
P

paulpriyam/spec2pr

Independent directory — not the official site. Details below come from the project's public repository.

Claude Code plugin: ticket, issue or idea to a reviewed, tested PR with the Elephant–Goldfish model (spec-kit…

1 ★ measured · checked 2026-11-19

Before you install: no copy-paste command · license MIT · link reachable

First step: nothing runnable here yet - start from the repository: https://github.com/paulpriyam/spec2pr

checked 2026-11-20 - the package in the command does not match this entry, so it is not shown as a copyable command.

★ 1·updated 2026-11-15
View on GitHub ↗Link checked 2026-11-17 · HTTP 200 · opens the vendor's own site

After install: how to tell it works

  1. What you see after install — The command exits 0 and the terminal shows no "command not found" or "permission denied".
  2. One-line self-check — Run the smallest usage example from that repository's README. If the output matches what the README describes, it is working.
  3. If that does not work — This project has no troubleshooting notes. Search its issues for "install".

The install command comes from the repository; these checks describe observable results only and do not replace the project's own docs.

Star count
1 ★ · paulpriyam/spec2pr · read from the GitHub search API · (checked 2026-11-19 20:00:48)
Source
read directly from its GitHub page · type: open-source project
Harvest history
first seen 2026-11-15 · last seen 2026-11-20 · seen 6× · listed by 2 sources
Score
score 203 · 1 ★ · 2 sources · repo
Install
see Install & config above
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Open Source. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository paulpriyam/spec2pr;first catalogued 2026-11-15;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.
README excerpt (English, untranslated) · Read the full README on GitHub →

# spec2pr

Excerpted from the repository README (abridged)

Give Claude Code a ticket. Get back a reviewed, tested pull request, and watch every step of the way.
spec2pr is a free plugin for Claude Code. You hand it a Jira ticket,
a GitHub issue or a one-line idea. It writes a spec, makes sure the spec is clear enough to build from,
builds the feature with a team of AI agents, tests it, opens the real app to check it works, reviews the
code, and opens the pull request. It stops and asks you whenever a decision is yours to make.
Website · Install · How it works · The dashboard
## Why
AI coding agents are fast, but on real features they tend to drift: they guess when the requirements
are vague, mark their own homework, and lose track of decisions made an hour ago. spec2pr fixes that
with one simple idea.
One agent remembers everything. We call it the elephant. It talks to you, writes the spec and
keeps every decision in it. It never writes code itself.
Every other agent starts fresh. We call them goldfish. Each one gets only the spec and the files
it needs, nothing else. If a goldfish can't build from the spec alone, the spec isn't good enough yet,
so it gets fixed before any code is written.
Nobody checks their own work. Code is checked against the spec, tested, tried out in the running
app and reviewed, each time by an agent that never saw how it was written.
## Install
You need Claude Code, git, python3, node, jq, and the
GitHub CLI (gh auth login).
bash
claude plugin marketplace add paulpriyam/spec2pr
claude plugin install spec2pr@spec2pr
Restart Claude Code. spec2pr writes its specs with spec-kit,
so set that up once per machine and once per project:
bash
uv tool install specify-cli --from git+https://github.com/github/spec-kit.git # once per machine
specify init --here --ai claude # once per project
## Your first feature
Open Claude Code in your project and type one of these:
text
/ship-feature PROJ-123 a Jira ticket
/ship-feature #42 a GitHub issue
/ship-feature saved-cards "Let users save their cards" just an idea
The dashboard opens in your browser. From there:
1. spec2pr reads the ticket and any linked docs or designs, and asks you about anything unclear.
2. It writes the spec and tests it on a goldfish. You'll see a Needs you card: read the plan and
press Go.
3. It builds, tests, checks the app and reviews, fixing what fails along the way.
4. It opens the pull request. Merging it is up to you.
Already halfway through something? Run /verify-feature. It checks what you have so far in the
running app, shows you what works and what doesn't, and asks whether to finish it, ship it, or stop.
## How it works
mermaid
flowchart LR
T["Ticket, issue or idea"] --> C["Gather requirements"]
C --> S["Write the spec (elephant)"]
S --> G{"Goldfish test: buildable from the spec alone?"}
G -- "no: fix the spec" --> S
G -- yes --> A(["You approve"])
A --> B["Build (agents in parallel)"]
B --> K["Check against the spec"]
K --> X["Test every acceptance criterion"]
X --> V["Try it in the running app"]
V --> R["Code review"]
R --> P(["Pull request"])
K -. gaps .-> B
X -. failures .-> B
V -. failures .-> B
R -. blocking issues .-> B
Every arrow back to Build is capped, so a stuck feature stops and asks you instead of looping
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/paulpriyam-spec2pr/)
Source
github · https://github.com/paulpriyam/spec2pr
Browse by field
Open source
Traction
1 ★
Listed by
2 independent sources
added
today

More entries

All 1,875 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index