quick-startlisted

# Quick Start — Automated Backlog Implementation Fastest path from "meeting note" to "working on it". Perfect for vague backlog items where you want Claude to figure out the details. ## Project Configuration Read project configuration from `.claude/project.json` in the current repository root: - `linear.teamId`, `linear.teamName`, `linear.projectId` - `github.owner`, `github.repo`, `github.defaultBranch` - `vercel.*` If `.claude/project.json` doesn't exist, suggest running `/setup-project` first. ## Instructions for Claude ### Expected Usage ``` /quick-start ABC-19 ``` User provides an issue ID (must be in Backlog state). Claude handles everything else. ### Step 1: Fetch and Validate Issue ``` Use mcp__linear__get_issue with provided ID ``` **IMPORTANT: Read the FULL issue description.** The `get_issue` response includes the complete description field — display and use the entire description, not just the first few lines. The description contains critical context, acceptance criteria, and requirements. **Validation:** - Issue exists - Issue is in "Backlog" state - Issue belongs to the correct project (read from `.claude/project.json`) **If validation fails:** ``` ❌ Cannot quick-start ABC-XX Reason: [Issue doesn't exist / Not in Backlog / Wrong project / Already refined] Suggestion: - If not in Backlog: Use /new-feature instead - If doesn't exist: Check Linear for correct ID - If already refined: Use /new-feature to start work ``` **If validation passes, displa