Stop Building Features
Based on Assumptions
AI-powered requirement clarification that systematically
uncovers gaps before you code.
Analyzing requirement for gaps...
Found 12 areas needing clarification across 5 categories.
Round 1 Questions:
1. Who are the primary users of this feature?
2. What order stages should be visible to customers?
3. Should users receive notifications on status changes?
The Requirement Problem
Stakeholder, Day 1
"Build a dashboard"
Same Stakeholder, Day 14
"Where's the pipeline view?"
"I assumed it was obvious"
Requirements arrive incomplete. Stakeholders don't know what they don't know. The "obvious" only becomes obvious after you ship the wrong thing.
How Spec Iterator Works
ANALYZE
Parse your requirement for gaps
CLARIFY
Ask targeted clarifying questions
TRACK
Watch your completeness score rise
GENERATE
Output a structured specification
Try it yourself
Input Requirement:
"We need order tracking for customers"
Click "Run Demo" to see questions
Know Exactly What's Missing
Track progress across 5 categories. See exactly what gaps remain and their impact before generating your spec.
Completeness
73%
Missing:
API rate limits, offline mode, error recovery scenarios
What You Get
# Order Tracking System ## Problem Statement **Pain:** Customers have no visibility into order status **Who:** E-commerce customers, support team ## Features ### 1. Order Status Page (MVP) **Acceptance Criteria:** - [ ] Display order stages: ordered, processing, shipped, delivered - [ ] Show estimated delivery date - [ ] Update within 5 minutes of status change ### 2. Email Notifications (MVP) **Acceptance Criteria:** - [ ] Send notification on each status change - [ ] Include tracking link in email - [ ] Support opt-out preference ## Edge Cases - Order stuck in processing > 24 hours - Multiple shipments for single order - International vs domestic tracking ## Open Questions - [ ] Integration with which shipping carriers? - [ ] Historical order lookback period?
Problem Statement
Clear problem definition
Features + Criteria
Testable requirements
Edge Cases
Boundary conditions
User Flow
Step-by-step journeys
Open Questions
Items needing follow-up
Assumed Items
Documented assumptions
Built For
Product Managers
Stop missing requirements that cause rework
Tech Leads
Don't estimate incomplete specs
Solo Devs
Think through requirements systematically
Startup Founders
Document ideas properly before dev
Simple Pricing
$0.05 - $0.15
per spec
Uses your Anthropic API key.
You pay Claude directly.
Cheaper than one clarification meeting.
Ready to Stop the Rework Cycle?
Transform rough ideas into complete specs in minutes.
Get Started on Smithery