1. Product Discovery
/athene-product-discoveryGuarantees problem-market fit before allocating architectural cycles. Discovers intent through a few targeted questions, maps real customer opportunities, and scores which one is worth solving before anything gets built.
When to use it
- checkA feature request shows up without a clear problem behind it
- checkYou want 2-3 solution options compared before committing
When to skip it
- closeThe problem and scope are already well understood and approved
- closeIt's a small fix with no real product ambiguity
How it works
- arrow_rightDiscovers intent through a few targeted questions
- arrow_rightMaps 3-7 real customer opportunities
- arrow_rightScores which one's worth solving
- arrow_rightCompares 2-3 options as a now / later / never release
- arrow_rightHands off to the build skill once approved
Usage example
You: "I think our users want a dark mode."
Athene: Athene asks what's actually driving the request before agreeing dark mode is the fix.
Next in documentationAthene (build)
Next step → Athene (build)arrow_forward