What problem does it solve? A repository freshly created from the Harness template starts unconfigured: it needs a deploy-target decision (Railway or code-only), an optional pre-built Next.js technical foundation, an optional MCP layer, and a change-key prefix, all applied as a single commit before any feature work can begin. ## Core Features & Use Cases - One-shot configuration: Asks a short batch of questions (deploy target, foundation, MCP, change prefix), then applies the choice, pushes exactly one commit to preprod, and deletes itself. - Railway provisioning: On the Railway path, runs a secrets preflight, lets the user pick a workspace when the account has several, and watches provisioning of production, preprod, and per-feature preview environments. - Foundation and MCP payloads: Copies a verified Next.js 16 application (Drizzle, Better Auth, TanStack Query) and an optional MCP endpoint out of quarantine, then runs a local verify chain. - Recovery handling: Detects half-applied and failed-preflight states from a previous run and resumes idempotently instead of starting over. - Use Case: You click "Use this template" on GitHub, open the new repo in Claude Code, and run /setup; after answering a few questions the repository is configured, provisioned, and ready for /feature. ## Quick Start Run /setup in a fresh repository created from the Harness template and answer the questions it asks.