setuplisted

# SpecRails Setup Initialize this project with the specrails workflow by generating project-specific configuration files. The sr plugin already provides all agents, skills, and commands — this skill generates the *data* layer that adapts the workflow to your project. **Input:** $ARGUMENTS — optional flags: - `--name <name>` — project name (defaults to directory name) - `--stack <stack>` — primary tech stack description (e.g. "Next.js + Rails + PostgreSQL") - `--domain <domain>` — product domain (e.g. "SaaS analytics", "developer tooling") - `--skip-claude-md` — skip CLAUDE.md generation --- ## Phase 1: Gather Project Context If `$ARGUMENTS` is empty, interactively gather: 1. **Project name** — default: current directory basename 2. **Tech stack** — ask: "What is your primary stack? (e.g. Next.js + Rails, Django + React, Go + gRPC)" 3. **Domain** — ask: "What domain is this product in? (e.g. developer tooling, SaaS analytics, e-commerce)" 4. **Backend layer** — ask: "What are your backend technologies?" (can be same as stack) 5. **Frontend layer** — ask: "What are your frontend technologies?" (can be same as stack) 6. **CI commands** — ask: "What command runs your full CI? (e.g. npm test, make test, ./scripts/ci.sh)" If `--name`, `--stack`, `--domain` flags are provided, use those values and skip the interactive prompts. Confirm the gathered values before proceeding: ``` About to set up specrails for: Project: <name> Stack: <stack> Domain: <domain> Backend: <ba