speclisted

# Spec Write a structured spec before any code. The spec is the shared source of truth; code without one is guessing. ## When to skip Single-file fixes, config changes, or tasks where requirements are unambiguous and self-contained. Note: `/build auto` requires a spec, so always run `/spec` before autonomous multi-task builds. ## Process ### 1. Surface assumptions first Before writing anything, list what you're assuming: ```text ASSUMPTIONS: 1. This is a web application (not native mobile) 2. Authentication uses session-based cookies (not JWT) 3. The database is PostgreSQL (based on existing Prisma schema) → Correct me now or I'll proceed with these. ``` Silent assumptions are the #1 source of wasted work. Don't fill in ambiguous requirements. ### 2. Ask clarifying questions about - The objective and target users - Core features and acceptance criteria - Tech stack preferences and constraints - Known boundaries (always do, ask first, never do) ### 3. Detect the existing stack Read the project's dependency files (`package.json`, `go.mod`, `Cargo.toml`, `.csproj`, `pyproject.toml`, etc.) to identify exact versions. State what you found: ```text STACK DETECTED: - React 19.1.0 (from package.json) - Vite 6.2.0 - Tailwind CSS 4.0.3 ``` ### 4. Write the spec Create `SPEC.md` at the project root covering these six areas: ```markdown # Spec: [Project/Feature Name] ## Objective What we're building and why. Who is the user. What success looks like. ## Tech Stack Framew