BobbieLee

Use when product work needs clearer framing, prioritization, or communication: clarifying a vague request, evaluating whether a feature is worth doing, comparing options, prioritizing requests, drafting a lightweight spec, building a roadmap, defining metrics, preparing an executive summary, reviewing outcomes, or making product-leadership/founder trade-offs. Best when the user needs a practical recommendation or reusable output, not just frameworks. Do not use for raw data crunching, deep project tracking, legal/compliance review, generic marketing copy, or pure UI copy.