本文へ移動
cccskills
無料GitHub で公開

client-discovery

Run a consulting client discovery session — uncover the real problem, scope, and decision process. Use when asked to prepare for a client discovery call, qualify a consulting lead, scope an engagement, or run a kickoff. Produces a discovery plan — the questions that surface the real problem (not the stated one), budget/authority/timeline qualifiers, success criteria, red flags, and a follow-up that leads to a proposal.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Client Discovery Skill

The brief a client gives you is rarely the real problem — and the difference is where good consulting (and accurate scoping) lives. This skill preps a discovery session that gets beneath the stated ask to the actual problem, qualifies whether it's a fit (budget, authority, timeline), and pins the success criteria — so you scope and price accurately and write a proposal that lands.

Required Inputs

Ask for these only if they aren't already provided:

  • The prospect — who they are, the stated ask, and how they found you.
  • Your offering — what you do, so questions probe fit.
  • What you need to decide — go/no-go, scope, and price.

Output Format

Discovery Plan: [prospect]

1. The goal of the call — qualify + uncover the real problem + earn the right to propose. Not to pitch.

2. Get to the real problem — questions that move past the symptom to the cause and the stakes:

  • "What made this a priority now?" · "What have you already tried?" · "What happens if you do nothing?" · "How will you know this is solved?" · "Who else is affected / involved?"
  • Use 5-whys-style follow-ups to reach the root, not the presenting issue.

3. Qualify (fit) — surface, tactfully:

  • Budget — is there one, and roughly what range? ("Have you set aside budget / a range in mind?")
  • Authority — who decides and signs? Are they on the call?
  • Timeline — when do they need it, and why that date?
  • Decision process — what happens after this call; who else weighs in.

4. Success criteria — the concrete outcome that = success, in their terms. (This becomes the proposal's objectives.)

5. Red flags — watch for: no budget/authority, "just exploring," scope that balloons mid-call, shopping many vendors on price, unrealistic timeline. Note how to handle each.

6. Close & next step — how to summarise what you heard (confirm understanding) and set up the proposal ("I'll send a proposal with options by [date]").

Quality Checks

  • Questions dig past the stated ask to the root problem and the cost of inaction
  • Budget, authority, timeline, and decision process are all surfaced (tactfully)
  • Success criteria are captured in the client's own terms
  • Red flags are anticipated with a handling plan
  • Ends by confirming understanding and setting up the proposal

Anti-Patterns

  • Do not pitch during discovery — listen and diagnose; the proposal is where you prescribe
  • Do not accept the stated problem at face value — the real one (and real scope) is usually underneath
  • Do not skip qualifying budget/authority — a beautiful proposal to someone who can't buy is wasted
  • Do not ignore red flags to win work — a bad-fit client costs more than the fee
  • Do not end without a confirmed next step and date — momentum dies in the gap

Based On

Consulting discovery / sales-qualification practice — root-cause questioning, BANT-style qualification, outcome-defined scoping.

Example Trigger Phrases

  • "Prepare for a client discovery call."
  • "Qualify a consulting lead."
  • "Scope an engagement."
  • "Run a kickoff."

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

mohitagw15856 のスキルをすべて見る

このスキルの問題を報告する