stella/ai-shared/product-think

Product Think

Shape a feature or problem before implementation. Use this when the request is still fuzzy, when several solutions are possible, or when execution risks outrunning product clarity.

Arguments

$ARGUMENTS: feature idea, problem statement, or change request.

Interaction Mode

Default to one coherent pass after confirming the problem statement. Do not stop after every step for ceremonial approval. Pause only when the user's answer would materially change who the product serves, the product boundary, or the recommended direction. Do not make the user answer questions the repository or evidence can resolve. Lead with discoveries, not step narration.

Instructions

Produce a short product brief: the problem and who has it, the user need kept apart from the proposed solution, the outcome that should change, constraints (technical, organizational, compliance or trust, timeline), options from the simplest viable to the stronger one plus what not to build yet, the tradeoffs between them, scope, success and failure signals, risks, and a recommendation. Move to implementation planning only once the brief is coherent.