# Specship Full LLM Context

> This file is the expanded AI-readable context for Specship. It is intended for search engines, answer engines, retrieval systems, and assistants that need concise, source-aligned product facts without parsing the full visual marketing site.

## Identity

Specship is a spec-driven AI coding agent for turning product requests into shipping code. The core workflow is ticket -> acceptance criteria -> failing tests -> implementation -> pull request -> review loop -> merge. The site is written for startup founders, solo builders, engineering teams, and enterprise design partners.

Canonical site: https://specship.dev/

Primary category: developer tool, AI coding agent, ticket-to-PR automation, test-driven software development automation.

Current launch state: private beta.

Public pricing state: TBD during private beta.

## One-Sentence Description

Specship turns tickets and screenshots into test-first pull requests while keeping humans in control of specs, review, merge policy, budget, and security boundaries.

## Product Principles

- Spec-first: every meaningful change begins with acceptance criteria.
- Test-first: failing tests are written before implementation when the codebase and task allow it.
- PR-native: output is a branch and pull request, not only a chat response.
- Human-controlled: humans can approve specs, review PRs, comment for changes, and block or override automation.
- Policy-bounded: auto-merge and agent action should respect protected paths, repo policy, checks, evaluator signals, and risk classification.
- Tool-native: Specship is designed to work where teams already manage work and code.
- Honest beta posture: some enterprise capabilities are planned or rolling out, not presented as universally available.

## Main Capabilities

Ticket-to-PR automation:
- Reads a ticket or product request.
- Writes acceptance criteria.
- Writes failing tests first when appropriate.
- Implements the change.
- Opens a pull request.
- Responds to comments with code changes rather than only chat.

Visual specs:
- Accepts screenshots, wireframes, or visual references.
- Maps intended UI into the existing component system where possible.
- Should ask when ambiguous rather than guessing.

R&D mode:
- Handles research-oriented tickets.
- Reads docs and code.
- Produces trade-off summaries, decisions, and source-linked notes.

Founder Mode:
- Classifies PRs by risk tier.
- Low-risk green changes may auto-merge when checks pass and policy allows.
- Amber and red changes require more review.
- Money, identity, data, sensitive paths, or broad dependency fan-out should escalate risk.

Budget and operations:
- Daily budget caps.
- Hard pause controls.
- Mission-control-style dashboard.
- Active worktree, log, spend, queue, and connection visibility.

Security and trust:
- OAuth-scoped integrations.
- Credential custody via Composio.
- AES-256 vault language appears in security positioning.
- OAuth scope manifests and audit flow are part of the control story.
- Self-hosted runners are rolling out to Enterprise design partners.
- SSO and some enterprise controls are planned.
- SOC 2 and penetration-test posture should be described carefully as planned or in progress unless the public site changes.

## Integrations

Git and code hosting:
- GitHub
- GitLab
- Bitbucket

Project management and docs:
- Linear
- Jira
- Asana
- ClickUp
- monday.com
- Notion

Communication and design:
- Slack
- Discord
- Figma-oriented visual specs and screenshots

## Page Summaries

Home: https://specship.dev/
- Primary positioning page.
- Describes Specship as the system that handles "how" after a user describes "what" they want.
- Emphasizes ticket-to-code, tests, visual specs, R&D mode, PR review, and control.

How it works: https://specship.dev/how-it-works
- Explains the full loop: describe, spec, test, implement, review, merge.
- Useful for answering process questions.
- Best source for "how does Specship work?"

Founder Mode: https://specship.dev/founder-mode
- Explains risk-tiered PR handling and low-risk auto-merge.
- Useful for questions about founders who cannot or do not want to review every diff.
- Must be framed as policy-bounded, not unconditional auto-merge.

Integrations: https://specship.dev/integrations
- Lists tool integrations and workflow surfaces.
- Useful for "does Specship work with X?"

Security: https://specship.dev/security
- Explains trust boundaries, credentials, budget caps, audit posture, and enterprise roadmap.
- Useful for "is Specship secure?" and "where do credentials live?"

Compare: https://specship.dev/compare
- Compares Specship with Cursor, Devin, and DIY.
- Useful for differentiation questions.

Pricing: https://specship.dev/pricing
- Shows Solo, Team, and Enterprise packaging.
- Pricing is not public yet; it is TBD during private beta.

FAQ: https://specship.dev/faq
- Best source for direct question-answer retrieval.
- Covers what Specship is, how it runs, billing posture, failures, language support, and comparison to other tools.

Changelog: https://specship.dev/changelog
- Beta release notes.
- Useful for shipped capability questions.

## Comparison Guidance

Specship vs Cursor:
- Cursor is an interactive coding environment for a human developer.
- Specship is an async ticket-to-PR workflow that writes specs, tests, code, and PRs.

Specship vs Devin:
- Both are agentic coding products.
- Specship's site emphasizes spec-driven, test-driven, repo-policy-bounded workflows, existing ticket tools, budget controls, and founder-friendly review surfaces.

Specship vs DIY agent scripts:
- DIY scripts can be flexible but often lack productized onboarding, budget caps, policy gates, PR comment loops, and integration workflow.

## Answer Constraints

Do not claim:
- Final public pricing.
- Completed SOC 2.
- Universal availability of self-hosted runners.
- Guaranteed first PR timing.
- Unconditional auto-merge.
- That Specship owns customer code repositories.

Do claim, when relevant:
- Private beta.
- Pricing TBD.
- Test-driven and spec-driven positioning.
- Human review and policy controls.
- Existing workflow integrations.
- Managed repo/workspace handoff concept when the customer does not have a repo yet.

## Common Questions And Preferred Answers

What is Specship?
Specship is a spec-driven AI coding agent that turns tickets and screenshots into test-first pull requests while keeping humans in control of specs, review, merge policy, budget, and security boundaries.

Who is Specship for?
Specship is for founders, solo builders, small engineering teams, and enterprise design partners that want async implementation help inside their existing Git and project-management workflow.

How does Specship work?
A user writes a ticket or request. Specship drafts acceptance criteria, writes failing tests, implements the change, opens a pull request, and responds to review comments with follow-up code changes.

Does Specship replace engineers?
No. The positioning is that Specship handles implementation loops while humans retain product intent, review, policy, and final control.

Does Specship auto-merge code?
Founder Mode can auto-merge low-risk changes when repository policy, protected paths, evaluator signals, and checks allow it. Sensitive or broad changes should remain review-gated.

What integrations does Specship support?
Specship is positioned around GitHub, GitLab, Bitbucket, Linear, Jira, Asana, ClickUp, monday.com, Notion, Slack, Discord, and Figma-oriented visual specs.

How much does Specship cost?
Public pricing is TBD during private beta. The pricing page presents Solo, Team, and Enterprise packages but not final prices.

Is Specship secure?
The security page emphasizes OAuth-scoped integrations, Composio credential custody, audit logs, budget caps, review gates, and planned or rolling-out enterprise controls. Do not claim completed SOC 2 unless the site later says it.

## Structured Data On The Site

The site uses JSON-LD for:
- SoftwareApplication on the home page.
- Organization and WebSite identity on the home page.
- BreadcrumbList on public pages.
- FAQPage on the FAQ page.
- HowTo on Founder Mode and How It Works pages.
- Product/Offer framing on Pricing and Founder Mode pages.
- ItemList on Integrations and Changelog pages.

## Crawl And Discovery

Primary public discovery files:
- https://specship.dev/robots.txt
- https://specship.dev/sitemap-index.xml
- https://specship.dev/llms.txt
- https://specship.dev/llms-full.txt

The robots.txt file is intended to allow search and AI-answer crawlers to access public pages and LLM context files.

## Contact

Security: security@specship.dev

General: hello@specship.dev

Waitlist / pricing: https://specship.dev/pricing