startlisted

# /start — Development Pipeline Orchestrator > One command to rule them all. Routes your task through the right skills, guarantees test infrastructure, and won't let you claim done without proof. ## Usage ``` /start <task description> ``` ## Pipeline You MUST follow this sequence exactly. No shortcuts. No skipping steps. --- ### Step 0: Test Infrastructure **This step runs EVERY time, before anything else. Do NOT skip any sub-step.** Check if `testing.md` exists at the project root. **If it does NOT exist:** 1. Explore the project to discover: - Package manager (npm, pnpm, yarn, bun) - Test frameworks already installed (vitest, jest, playwright, etc.) - Scripts in `package.json` (test, test:e2e, test:integration, etc.) - Existing test files and their locations - Required environment variables - Database or service dependencies 2. Create `testing.md` using the template below, filled in with **real values from this project**: ```markdown # Testing Guide ## Environment Setup - Package manager: [detected] - Required env vars: [list with descriptions] - Database: [commands to start/seed test DB, or "none"] - Services: [docker-compose, external APIs, or "none"] ## Running Tests ### Unit Tests Command: `[detected or recommend]` Location: `tests/unit/` ### Integration Tests Command: `[detected or recommend]` Location: `tests/integration/` ### E2E Tests (Playwright) Command: `npx playwright test` Setup: `npx playwright install chromium` Base URL: `[d