product-thinkinglisted

# Product Thinking A reasoning lens, not a gate. It produces no artifact of its own and blocks nothing. It shapes how the pre-implementation agents frame, design, and slice scope so that the work is something real people actually want. ## Core Lenses Four lenses sharpen every framing, design, and slicing decision: - **Demand evidence over assertion**: Ask what signal says a real person wants this — not if it is technically possible or interesting to build. A clever capability nobody asked for is still waste. - **Smallest thing people want**: Prefer the thinnest version that delivers real value, and resist speculative scope and gold-plating. Extra surface area is cost you pay before you have learned if anyone wants it. - **Build for someone specific, not nobody**: Name the actual user a change serves. A feature with no identifiable user is a red flag to surface, not a detail to gloss over. - **Talk-to-users mindset**: Treat the user's stated intent as a *proxy* for real demand, and explicitly surface where an assumption is standing in for validation rather than silently accepting it as fact. ## When Framing the Task Questions to sharpen the *inferred goal* and *acceptance signals* you write into `task.md`: - **Who specifically is this for?** Identify, if knowable, who the work serves — an actual person or role, not "users" in the abstract. - **What signal would tell us they want it?** Identify the observable demand signal that the acceptance criteria