start-worklisted

# /start-work - Begin Working on a GitHub Issue Start work on a GitHub issue with proper environment setup, branch creation, and workflow enforcement. ## Usage ``` /start-work <issue-number> ``` ## Arguments - `issue-number` (required): The GitHub issue number to work on (e.g., `198`) --- ## Workflow Steps Execute these steps in order. **STOP and report if any step fails.** ### Step 1: Pre-flight Checks ```bash # Check for uncommitted changes git status --porcelain ``` **If output is not empty:** > "You have uncommitted changes. Please commit or stash them before starting new work." > Show the uncommitted files and STOP. **If clean:** Proceed. ### Step 2: Fetch GitHub Issue ```bash gh issue view $ISSUE_NUMBER ``` **Extract from issue:** - Title - Labels (to determine: feature, bug, docs, etc.) - Description/body **Report to user:** > "Starting work on #[number]: [title]" ### Step 3: Review Available MCP Tools **BEFORE planning implementation, review available MCP servers and tools that might be useful for this issue.** Use the `ListMcpResourcesTool` to see all available MCP servers and their capabilities: ```typescript // Review all MCP servers ListMcpResourcesTool({}) ``` **Consider which tools might be relevant:** - **Supabase MCP**: Database queries, migrations, logs, advisors - **GitHub MCP**: Issue management, PR operations, code search - **Context7 MCP**: Library documentation lookup (Next.js, Supabase, React, etc.) - **Netlify MCP**: Deployment, fo