mnriem

Apply a go / needs-clarification / kill gate and hand survivors off into Spec-Driven Development

Define the problem: who is affected, what hurts, goals, non-goals, and success metrics

Capture and normalize a raw idea (text, URL, ticket, or codebase pointer) into an intake note

Gather evidence — users, market, prior art, and data — to support or challenge the idea

Shape a concept: solution options, scope, appetite, and trade-offs (no implementation design)

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.