Requirements Refiner

Transform rough requirements into implementation-ready specifications optimized for Claude Code execution.

When to Use

• Received a PRD/spec that's prose-heavy and ambiguous
• Requirements scatter file paths throughout text
• Specs say "similar to X" without explaining X
• Missing API contracts, data models, or clear scope
• Before starting implementation on complex features
• Starting a new project from scratch (greenfield)
• Need to identify missing information before coding
• Architectural refactoring (e.g., session-based to JWT)
• Multi-service features spanning frontend/backend/database

When NOT to Use