End-to-End Feature Pipeline Shipper

What it does

/ship is a Cursor slash command. Type it in chat to run a saved workflow: End-to-End Feature Pipeline Shipper.

Orchestrates a complete multi-agent engineering workflow from technical spec to schema migration, backend endpoints, frontend UI, tests, and docs.

Spec, architect, implement, test, and document full-stack features in one turn. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /ship for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /ship exists so the pipeline, all 6 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Engineering Kit. It is wired to Technical Lead & System Architect (tech-lead), Senior Backend Architect (backend-architect), React 19 & Next.js Specialist (react-specialist), and Test Automation Engineer (test-automator). Required skills: SaaS Architecture Patterns & Multi-Tenancy; Next.js App Router & Server Components; PostgreSQL & Drizzle ORM Schema Standards; Vitest Unit & Integration Testing.

When to use it

• Use when implementing a major full-stack feature requiring coordinated changes across models, routes, components, and tests.
• Use /ship when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just wrote marketing copy.

When not to use it

• Do not run /ship on a one-line bug, a CSS token, or a complexity-L epic. Split first.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. tech-lead parses requirements against CURSOR.md conventions and generates a technical spec
2. postgres-pro drafts database schema changes and migration files
3. api-engineer implements type-safe API endpoints with Zod validation
4. react-specialist builds responsive UI components and Server Actions
5. test-automator writes Vitest unit tests and Playwright E2E verification suites
6. technical-writer updates docs/ and changelog

Example usage

Type this in Cursor chat: /ship Add user avatar upload with S3 storage and thumbnail generation

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: src/app/api/...
• Expected artifact: src/components/...
• Expected artifact: src/db/schema.ts
• Expected artifact: tests/...

Best practices

• Keep the prompt specific. /ship Add user avatar upload with S3 storage and thumbnail generation is the shape: object, constraint, and outcome.
• Let the listed agents work in order: tech-lead → backend-architect → react-specialist → test-automator.
• Save outputs in the repo. Chat-only answers evaporate.
• Engineering commands should leave tests or an audit note, not only implementation files.

Common mistakes

• Typing /ship with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the SaaS Architecture Patterns & Multi-Tenancy skill that the command depends on.