problem-definition

Produce a Problem Definition Pack in Markdown (in-chat; or as files if the user requests):

1) Context snapshot (product, user, trigger, decision, constraints) 2) Problem statement (1-liner + expanded) + why now 3) JTBD (primary job + key sub-jobs) + target segment notes 4) Current alternatives (including analog/non-digital) + gaps + switching costs 5) Evidence & assumptions log (what we know vs what we’re guessing)

6) Success criteria (outcome metric(s), leading indicators) + guardrails 7) Scope boundaries (in/out, non-goals, dependencies) 8) Prototype / learning plan (fast prototype + tests to de-risk) 9) Risks / Open questions / Next steps (always included)

製品の問題を定義し、問題定義パック (問題ステートメント、JTBD、現在の代替案、証拠と仮定、成功指標、範囲境界、プロトタイプ/学習計画) を作成します。問題空間を明確にするときに使用します。 ソース: liqiongyu/lenny_skills_plus。