Ship
Instruction-first SDLC framework
Ship gives your agent a method, not a vendor lock-in
Use one guided prompt to adapt delivery, QA, release gates, and retros to your existing stack (Linear/Jira/GitHub Issues/spreadsheets, any CI, any agent runtime).
Choose Your Path
Getting started
Prompt builder + copy-ready instruction. Fastest way to launch adoption with any agent.
Adoption playbooks
Interactive setup contract, launch matrix, migration notes, and practical rollout artifacts.
Interfaces & API
Tracker adaptation contract and backend endpoints: /search, /fetch, /feedback.
Reference implementations
Battle-tested wiring (ElMundi) + contribution path for new real-world setups.
What You Get
- Interactive onboarding — agent asks discovery questions before changing files.
- Portable contracts — queue, QA split, release gates, digest/retro rhythm.
- Evidence trail — decisions and automation outputs stay auditable.
- Continuous improvement — retro feedback can become Ship backlog issues safely.
Local run
Next.js (manual + landing) — from repo root:
npm install
npm run landing:dev
Open http://127.0.0.1:3000/docs for this manual.
Backend API:
python3 -m venv .venv
. .venv/bin/activate
pip install -r requirements-backend.txt
uvicorn backend.app.main:app --reload --host 127.0.0.1 --port 8100
Buying & procurement
Ship is methodology + prompts + reference implementations.
- No mandatory vendor bundle.
- No implicit SLA unless your org adds one.
- Exit path is explicit because interfaces are documented.
Documentation versioning
Current manual version: 0.7.0 (ship with the repository).
License
Apache 2.0 for this repository unless a file says otherwise. See Legal & copyright.