spec-createlisted

# Create Feature Specification Transform a planning conversation into a structured spec folder that enables parallel agent implementation. The spec breaks a feature into self-contained task files — each one detailed enough that a coder agent can pick it up cold and implement it without reading anything else. The key insight: implementation plans that live in a single file are either too large for a context window or too shallow for independent execution. By splitting into one file per task with full context in each, we enable multiple agents to work in parallel while keeping each agent's context focused. ## When to Use - After a planning conversation where requirements and technical details have been discussed - When the user asks to create a spec, plan a feature, or break work into tasks - When the user wants to prepare work for parallel agent implementation ## Instructions ### Step 1: Gather Requirements If the conversation already contains planning context (requirements discussed, technical decisions made, architecture outlined), extract all of it. Review the entire conversation to ensure nothing is lost — the spec is the single source of truth, and anything not captured here disappears. If no planning conversation exists, interview the user: - What does this feature do and why does it matter? - What are the acceptance criteria? - What technical constraints or decisions have been made? - What files, APIs, schemas, or patterns are involved? ### Step 2: Name the Fea