georgiai

Interview a business owner about how their business actually runs and produce a single, build-ready Business Requirements Document (BRD) so complete that a coding agent can build the whole system from it in one shot — no follow-up questions, no invented decisions, no gaps. Use this skill whenever the user wants to write, draft, review, or improve a BRD, a software specification, a requirements document, or a "spec" for a system to be built; whenever they want to be interviewed about their business process so it can be turned into software; whenever they mention "one-shot", "build-ready spec", "zero assumptions", or hand over exports/orders/screenshots of a current tool to be turned into requirements — even if they don't use the word "BRD".

Use when an MCP server's OAuth login in Claude Code fails on every attempt with "Unrecognized client_id" or invalid_client — /mcp → Authenticate loops endlessly, one project fails while the same server works in other projects, and reinstalling/re-adding the server under the same name changes nothing. Applies to any OAuth MCP server (Supabase, Notion, etc.) whose Dynamic Client Registration went stale.

Use when working on Nuxt 4+ projects - provides server routes, file-based routing, middleware patterns, Nuxt-specific composables, and configuration with latest docs. Covers h3 v1 helpers (validation, WebSocket, SSE) and nitropack v2 patterns. Updated for Nuxt 4.3+.

Interrogate an existing draft functional specification (spec, BRD, PRD, requirements doc) to extract every decision it does NOT make — via batches of closed A/B/C/D/E multiple-choice questions grouped by section, covering edge cases, state transitions, permissions, errors, data rules, concurrency, contradictions and undefined terms. Use when the user pastes or points to a draft spec and wants to be interviewed about its gaps rather than have it rewritten. For writing a BRD from scratch, use brd-architect instead.