backend-buildlisted

Turn a `BACKEND_DESIGN.md` brief into a working backend. Read the brief first, follow its decisions, don't invent architecture the brief didn't decide. ## Example prompts - "Build the backend from the brief" - "Implement the notifications service" - "Code the API defined in BACKEND_DESIGN.md" - "Start building the server for checkout" ## Prerequisites - A `BACKEND_DESIGN.md` file at `.design/<feature-slug>/` (produced by `/backend-design`). - If none exists, stop and tell the user to run `/backend-design` first — this skill needs a brief, not a vibe. ## Process 1. **Read the brief in full.** Note every decision the brief locked in: - Stack (Fastify vs other), schema strategy (JSON Schema / TypeBox / Zod), ORM, datastore - Plugin boundaries, decorators, hooks - Auth model, error shape, logger config - Every route in the API surface table - Deployment target, migrations strategy 2. **Scan the codebase.** If this is an existing project, do NOT restart from scratch. Extend what's there. Check: - `package.json` for existing deps - Existing plugin tree, route files, decorator definitions - Existing DB connection, migration setup, test framework - `.env` / `env.example` for existing config keys 3. **Confirm the build plan** before writing code. State back: - Files you'll create / modify (as a short list) - New dependencies needed (and why) - Migration(s) that will be generated - Build order (foundations → auth → routes → tests) W