NewFounder Mode is in private beta — auto-merge low-risk PRs, plain-English changelog.See how it works
NewSpecship 0.2 — Visual specs from screenshots

Describe what you want.We handle how.

Specship turns your tickets into shipping code. The AI handles the how. You stay in control of the what.

Connect GitHub  ·  assign a ticket  ·  first PR in under a minute
app.specship.dev / workspace / acme
MK
DR
AB
Active
3 tickets · 1 in coding · 1 in review
⌘K New
SPEC-127Coding14 min
Add CSV export to invoices table
billing-api·
MK
Implementing · 3 of 5 tests passing
SPEC-128In review2 h
Migrate auth to single-session JWT
billing-api·
DR
PR #215 ready for review
SPEC-129Writing specjust now
Match dashboard table layout from wireframe
dashboard·
AB
Drafting acceptance criteria
SPEC-130Tests3 h
R&D: Stripe vs. Paddle for EU VAT
billing-api·
MK
Researching · 4 sources scanned
Plugs into the tools your team already uses
GitHub
GitLab
Bitbucket
Linear
Jira
Asana
ClickUp
Monday
Notion
Slack
GitHub
GitLab
Bitbucket
Linear
Jira
Asana
ClickUp
Monday
Notion
Slack
The development loop

Idea → Ticket → Tests → Code → Review → Done.

The same loop every great team runs — except the agent does the middle three. You start with an idea. You end with a merged PR.

Idea
01
Ticket
02
Tests
03
Code
04
Review
05
Done
06
Try it

From paragraph to pull request.

Type a sentence. Watch specship write the spec, the tests, and the implementation — in that order, every time.

1 · Describe what you want
2 · Spec + tests, auto-written
Hit Generate ticket
specship will draft a full ticket with acceptance criteria
What you get

A spec-driven loop, on autopilot.

Click any feature to see it in action.

Spec-driven, every time

Assign a ticket. Get a PR.

The agent reads your ticket, writes the spec, drafts failing tests, implements, and opens a PR. You stay in the loop on every step — and in control of every decision.

  • Acceptance criteria gate
  • Tests written before code
  • Conventional commits & branch naming
linear.app / specship / SPEC-127
SPEC-127·Coding
Assigned

Add CSV export to invoices table

Acceptance criteria · auto-generated
  • User can click 'Export' in the table toolbar
  • CSV includes filtered rows
  • Streams to handle 10k+ rows
specship32s ago
3 tests drafted. Implementing now.
The opinionated bit

We think TDD isn’t optional.
So we made it impossible to skip.

Every ticket starts with acceptance criteria. The agent writes failing tests first, then code that turns them green. Your codebase gets stronger with every merge — not weaker, faster, or more brittle.

Acceptance criteria are non-negotiable. The agent refuses tickets without them.
Tests written before implementation. Every PR includes a diff + coverage report.
Wire the coverage report into your CI gate — your repo, your threshold.
specship · tdd loop
Cost you can predict

No surprise AI bills.

Subscription billing. Daily caps. Full per-ticket telemetry. The opposite of opening your dashboard to find an "oops" line item.

Daily budget cap

Set a ceiling. Specship respects it.

Per-project daily token spend cap. Defaults to a conservative $10/day and you can move it from there.

app.specship.dev / billing / budget
Daily budget · acme
$6.20/ $10.00
62% of cap● on track
Hard pause switch

Threshold hit → everything stops.

Instead of running over budget, Specship pauses in-flight work and pings you. Resume manually or wait for tomorrow.

app.specship.dev / queue · paused
BUDGET HIT · PAUSED
4 jobs paused mid-flight
Resume manually, raise the cap, or wait for tomorrow’s reset.
Per-ticket telemetry

Every cent has a ticket attached.

Token spend is broken down per project, per ticket, per loop phase. Audit anything, no analytics integration required.

app.specship.dev / SPEC-127 / spend
Ticket spend · SPEC-127
plan$0.04
tests$0.18
code$0.41
review$0.07
iterate$0.03
total$0.73
How it works

Five steps. Zero handoffs.

01

Connect

Authorize your Git host and your PM tool. Takes 30 seconds.

02

Describe

Open a ticket. Write a paragraph. Drop in a screenshot if you have one.

03

Assign

Route it to Shipd with your configured assignment, label, mention, or ready status. The agent picks it up immediately.

04

Review

Read the PR. Comment to request changes. The agent watches the ticket.

05

Ship

Merge. The bot updates the ticket and closes it. You're done.

linear.app / specship / SPEC-204
SPEC-204·Writing spec
Assigned

Match this dashboard table layout

Same data as today, but laid out like this wireframe. Use existing components.

dashboard-table.png
↑ user-dropped wireframe — agent will match
specship12s ago
Read the wireframe. Mapping to <DataTable> + <Toolbar>. Adding 'Export CSV' as a primary button per your design. Acceptance criteria below — looks right?
Visual specs

Paste a screenshot. Skip the Figma handoff.

Drop any image into a ticket comment — wireframe, screenshot, sketch on a napkin. The agent reads it, maps to your existing components, and matches the UI as closely as it can.

  • No plugin. No spec doc. No handoff meeting.
  • Uses your component library, not generic Tailwind.
  • Asks if it's unsure — never guesses on ambiguity.
R&D mode

Research tickets that actually finish.

Tag a ticket as R&D. The agent researches the topic, reads docs and code, writes a comparison, and posts the whole thing back to your workspace.

// in your ticket
Research: Stripe vs. Paddle for EU VAT
notion.so / acme / r-d / stripe-vs-paddle-for-european-vat-handli
R&DAuthored by· 2 min read

Stripe vs. Paddle for European VAT handling

TL;DR
Paddle is a merchant of record — handles VAT registration, collection, and remittance for you. Stripe Tax handles calculation only; you still register in each country. For ≤€10M ARR, Paddle wins on operational cost.
Decision
Migrate EU sales to Paddle. Keep Stripe for US/APAC. Migration: ~4 weeks, blocked on legal review of Paddle MSA.
Sources
Stripe Tax docs, Paddle MoR guide, 3 founder threads on YC, internal /docs/finance.md.
Pricing

Simple tiers. Waitlist while we tune.

Pricing TBD — join the list to lock in beta rates.

Solo

For founders shipping alone.

TBD
billed monthly
Join the waitlist
  • 1 connected repo
  • 1 PM tool integration
  • Unlimited tickets / month
  • Test-driven workflow
  • R&D ticket mode
  • Visual spec attachments
  • Multi-seat collaboration
  • Private repo support
  • Self-hosted runners
  • SSO + audit logs
  • Priority support
Most popular

Team

For small teams that want guardrails.

TBD
per seat, monthly
Join the waitlist
  • Up to 5 connected repos
  • Unlimited PM tools
  • Unlimited tickets / month
  • Test-driven workflow
  • R&D ticket mode
  • Visual spec attachments
  • Multi-seat collaboration
  • Private repo support
  • Self-hosted runners
  • SSO + audit logs
  • Priority support

Enterprise

For teams with their own compliance bar.

Let's talk
annual contract
Talk to us
  • Unlimited repos
  • Unlimited PM tools
  • Unlimited tickets / month
  • Test-driven workflow
  • R&D ticket mode
  • Visual spec attachments
  • Multi-seat collaboration
  • Private repo support
  • Self-hosted runners (rolling out)
  • SSO + audit logs (planned)
  • Priority support
Founder Mode · private beta

Stop reviewing PRs you can’t read.

We classify every PR by risk. Low-risk + tests green → auto-merge. Risky → we ping you with a plain-English summary and wait. You get a changelog instead of a diff queue.

Auto-merge is always bounded by your repo policies, protected paths, and reviewer rules.

app.specship.dev / changelog
This morning, in plain English
✓ Login flow shipped
PR #214 · 3 tests · 94% coverage
✓ Pricing page
PR #213 · 6 tests
⚠ Payment route needs your review
PR #212 paused · /api/billing/charge
Now in private beta

Stop writing tickets nobody picks up.Start shipping.

Join the waitlist — we’re onboarding a few teams a week. Builders only, no procurement decks.

No credit card · We’ll email you when you’re in · Unsubscribe any time