shipwright-pipeline
Autonomous app builder that converts plain-English descriptions into
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/shipwright-pipeline && cp -r /tmp/shipwright-pipeline/plugins/ai-agency/shipwright/skills/shipwright-pipeline ~/.claude/skills/shipwright-pipelineSKILL.md
# Shipwright Pipeline
## Overview
Shipwright converts a plain-English app description into a fully built, tested, and deployment-ready application. It delegates execution to `product-agent`, an autonomous 9-phase build engine available on PyPI.
## Prerequisites
- Python 3.10+ available in PATH.
- `product-agent` installed (`pip install product-agent`).
- Node.js 18+ for JavaScript/TypeScript stacks.
## Supported Stacks
- **Next.js + Supabase** — Full-stack with auth, database, and edge functions
- **Next.js + Prisma** — Full-stack with type-safe ORM
- **SvelteKit** — Lightweight full-stack with Svelte
- **Astro** — Content-focused static and hybrid sites
## Instructions
1. Gather the app description from the user. Ask clarifying questions if the description is vague.
2. Confirm the target stack. If none specified, recommend based on the app type:
- Data-heavy with auth: Next.js + Supabase
- API-first with complex models: Next.js + Prisma
- Lightweight interactive: SvelteKit
- Content or marketing site: Astro
3. Run `product-agent` with the app description and selected stack.
4. Monitor the 9-phase pipeline: Intake, Architecture, Scaffold, Implement, Test, Integrate, Polish, Validate, Ship.
5. Report results to the user including test summary and any warnings.
## Output
- A complete, buildable project directory with all source code, tests, and configuration.
- A test report summarizing pass/fail counts.
- Build verification output confirming the project compiles and starts.
## Error Handling
- If `product-agent` is not installed, prompt the user to install it with `pip install product-agent`.
- If a phase fails, report the phase name, error message, and suggested fix.
- If the selected stack is not supported, list available stacks and ask the user to choose.
## Examples
**Build a SaaS dashboard:**
```
/shipwright-build Build a real-time analytics dashboard with user auth, team workspaces, and Stripe billing. Use Next.js + Supabase.
```
**Add features to an existing project:**
```
/shipwright-enhance Add dark mode toggle, export-to-CSV on all tables, and email notification preferences.
```
**Scaffold a content site:**
```
/shipwright-build Create a developer documentation site with search, versioned docs, and a blog. Use Astro.
```
## Resources
- [Shipwright on GitHub](https://github.com/Wynelson94/shipwright)
- [product-agent on PyPI](https://pypi.org/project/product-agent/)
- See `${CLAUDE_SKILL_DIR}/references/examples.md` for usage examples.|
Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
Plan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".
Knowledge engineer — architecture docs, ADRs, diagrams, changelogs, onboarding, and reports.