Elicit

This walks you through building Allium specifications by asking the right questions at the right time. It helps you figure out scope boundaries first (what's in, what's out, what's a separate spec), then guides you to the right abstraction level through tests like "could this be implemented differently?" and "why does the stakeholder care?". The approach changes based on what you bring: if you're describing a process it starts with discovery, if you're naming entities it jumps to details, if you have existing code it points you to distillation. The real value is in teaching you to distinguish domain concerns from implementation details, which is harder than it sounds when you're in the middle of a conversation.