Official descriptionOpen source3d ago
Dani777rtg/shipwright
Spec-driven AI development method for Claude Code: requirements interview → architecture → plan → build → verify → ship → self-improving retro. Built on ECC.
View on GitHub ↗Direct link · no redirect page
- Star count
- 1 ★ · Dani777rtg/shipwright · read from the GitHub search API · (checked 2026-10-16 20:00:20)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-14 · last seen 2026-10-14 · seen 1× · listed by 1 sources
- Score
- score 103 · 1 ★ · 1 sources · repo
- Install
pip install graphifyy
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
pip install graphifyy. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
Dani777rtg/shipwright；first catalogued 2026-10-14；last seen 2026-10-14。There is no official certification or quality rating here — we record sources and dates only.Third-party quality signals
Shipwright
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
A Claude Code plugin that takes a problem to working software **fast and done right**: ECC's experts say how to build it, agents build it in parallel with tests first, brief checks, and you approve the spec and the delivery.
**Status:** v1.2 — 4 phases, 2 approvals. The 8-phase version remains available at tag v0.16.0.
How it works
**Problem → ask ECC's experts (architecture, development, QA) → build in parallel → brief checks → ship.**
| Phase | What happens | You |
|---|---|---|
| 1. Spec | Reads the brief and your code, asks only what blocks, consults ECC's experts, writes one spec with stories, verifiable criteria, risk and tasks | **Approve** |
| 2. Build | One QA agent per story writes the locked acceptance tests; builders work in parallel with your stack's ECC skills, tests first; one review per batch; pace against your deadline; product docs with a proven quick start | — |
| 3. Verify | Hidden tests, full suite, pertinent test types, a short security pass → SHIP / NO SHIP | Only if something fails |
| 4. Ship | PR, deploy with canary and rollback, or a document | **Approve** |
Phases chain on their own. /shipwright:status shows progress and whether the deadline holds; /shipwright:change changes what was approved, with impact and approval; /shipwright:retro (optional) improves the framework with what was learned.
Not traded for speed: acceptance tests written by an independent agent that builders cannot touch, tests first, everything green before integrating, a security check of sensitive code, your approval of the spec and of production. ECC's skills make the code better; the locked tests prove it works.
Install
Two **separate** commands: type the first, press Enter and wait; then the second.
1. Add the marketplace:
(If an "Enter marketplace source" box opens, type only Dani777rtg/shipwright there.)
2. Install the plugin:
Check by typing /shipwright: /shipwright:spec, /shipwright:build… should appear. If not, run /reload-plugins.
Requirements: git and Node 18+. Optional: graphify (pip install graphifyy) to map existing systems.
Use
If the brief comes as documents (PDF, notes, transcripts), pass their path: /shipwright:spec "C:\folder\brief.md". It works the same for something **new** and for a change to an **existing system** ("add Google login to our app"). Shipwright talks to you and writes the mission documents in your language.
**Status:** v1.2 — 4 phases, 2 approvals. The 8-phase version remains available at tag v0.16.0.
How it works
**Problem → ask ECC's experts (architecture, development, QA) → build in parallel → brief checks → ship.**
| Phase | What happens | You |
|---|---|---|
| 1. Spec | Reads the brief and your code, asks only what blocks, consults ECC's experts, writes one spec with stories, verifiable criteria, risk and tasks | **Approve** |
| 2. Build | One QA agent per story writes the locked acceptance tests; builders work in parallel with your stack's ECC skills, tests first; one review per batch; pace against your deadline; product docs with a proven quick start | — |
| 3. Verify | Hidden tests, full suite, pertinent test types, a short security pass → SHIP / NO SHIP | Only if something fails |
| 4. Ship | PR, deploy with canary and rollback, or a document | **Approve** |
Phases chain on their own. /shipwright:status shows progress and whether the deadline holds; /shipwright:change changes what was approved, with impact and approval; /shipwright:retro (optional) improves the framework with what was learned.
Not traded for speed: acceptance tests written by an independent agent that builders cannot touch, tests first, everything green before integrating, a security check of sensitive code, your approval of the spec and of production. ECC's skills make the code better; the locked tests prove it works.
Install
Two **separate** commands: type the first, press Enter and wait; then the second.
1. Add the marketplace:
(If an "Enter marketplace source" box opens, type only Dani777rtg/shipwright there.)
2. Install the plugin:
Check by typing /shipwright: /shipwright:spec, /shipwright:build… should appear. If not, run /reload-plugins.
Requirements: git and Node 18+. Optional: graphify (pip install graphifyy) to map existing systems.
Use
If the brief comes as documents (PDF, notes, transcripts), pass their path: /shipwright:spec "C:\folder\brief.md". It works the same for something **new** and for a change to an **existing system** ("add Google login to our app"). Shipwright talks to you and writes the mission documents in your language.
- Source
- github · https://github.com/Dani777rtg/shipwright
- Browse by field
- Open source
- Traction
- 1 ★
- added
- 3d ago
More in Open source
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.