spec-builderlisted

Transform vague product or feature ideas into concrete, detailed specification documents through an interactive interview process. Use when the user wants to flesh out an idea, create a spec, write requirements, plan a product/feature/prototype, or go from "I have this idea..." to a concrete document. Works for software products, physical products, services, or any concept that needs specification.
diegosouzapw/awesome-omni-skill · ★ 42 · Web & Frontend · score 63

Install: claude install-skill diegosouzapw/awesome-omni-skill

# Spec Builder Transform vague ideas into concrete, actionable spec documents through structured interviews. ## Workflow ### Phase 1: Gather Initial Context First, prompt for the idea: ``` What's the idea you'd like to turn into a spec? Describe it however it exists in your head right now - it can be vague. ``` Then ask background questions to calibrate the interview depth: ``` AskUserQuestion: 1. "What's your background?" - Technical (developer/engineer) - Semi-technical (PM, designer, technical founder) - Non-technical (business, creative, general user) 2. "What's the goal for this spec?" - MVP/prototype to test the idea - Full product spec for development - Pitch document for stakeholders - Personal reference to clarify my thinking ``` ### Phase 2: Deep Interview Conduct the interview using AskUserQuestion with **batched questions** (2-4 related questions per batch). **Rules:** - Never assume - if something is ambiguous, ask - Provide sensible default options for every question - Add "(Recommended)" to the best default option - Anticipate needs the user hasn't considered - Adapt question depth based on user's technical level **Question calibration by user background:** | Topic | Technical User | Non-Technical User | |-------|---------------|-------------------| | Architecture | "REST vs GraphQL vs tRPC?" | Skip - decide yourself | | Data storage | "SQL vs NoSQL? Which DB?" | "Does it need to remember data between sessions?" | | UI framewor