spec-writer

Transform vague product ideas into clear PRD requirements by using Socratic interrogation to question ambiguous terms like 'fast' or 'easy', extracting precise definitions and testable user stories from the initial request.

Defining non-goals to prevent scope creep involves explicitly documenting out-of-scope features during PRD creation, ensuring development teams focus strictly on validated user stories and testable requirements.

Write user stories from ambiguous requests by applying context compression to identify the core user benefit, formatting the output strictly as 'As a [User], I want to [Action], so that [Benefit]' to ensure user-centricity.

Yes, PRD generation works for high-level concepts like a 'modern-looking app' by interrogating vague terms to extract specific UI elements, performance metrics, and feature boundaries, then structuring them into a formal template.

Use Socratic interrogation for requirement clarification when initial user requests contain subjective adjectives or undefined assumptions, ensuring every extracted product requirement is measurable and testable before documentation.