nahisaho Purpose Discovery (MCK)
Discover the client's true objective through structured dialogue.
Use This Skill When
- Starting a new McKinsey-style consulting engagement.
- The request is ambiguous or surface-level.
- Defining scope, constraints, and success criteria.
Workflow
- Decompose request into 6 elements (PURPOSE, TARGET, SCOPE, TIMELINE, CONSTRAINTS, DELIVERABLES).
- Present for user approval ⏸️.
- One-question-at-a-time dialogue (minimum 3 rounds).
- 5 Whys analysis for abstract answers.
- JTBD analysis (Functional, Emotional, Social jobs).
- Define true objective → user approval ⏸️.
- Generate research plan with bilingual search queries.
- Recommend MCK-specific frameworks based on the objective.
Deliverables
results/purpose-definition.md: 6-element breakdown + true objective.results/research-plan.md: search queries, recommended MCK frameworks.
Quality Gates
- All 6 elements addressed.
- Minimum 3 dialogue rounds completed.
- True objective is specific, actionable, and user-approved.
- Recommended MCK frameworks are justified.
If any gate fails: identify the specific failing check, fix the issue, and re-validate before proceeding.
Gotchas
- 複数の質問を一度に投げてはならない。必ず1問1答形式で進める
- ユーザーの最初の依頼が「真の目的」であることは稀。表層的な依頼の裏にある本質を探ること
- MCKフレームワークの推薦は目的確定後に行う。目的が曖昧な段階でフレームワークを決めない
- 対話ラウンドは最低3ラウンド。3ラウンド未満で「十分」と判断してはならない
- 構造化プロンプトの6要素に空欄がある場合は追加ヒアリングで埋めること
Validation Loop
- 6要素分解と真の目的を生成
- チェック: PURPOSE が意思決定に直結するか、SCOPE が検証可能か
- 不合格なら対話を追加
- ユーザー承認後のみ完了