agentleFS
Sign inStart free
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/discovery-question-design/SKILL.md

discovery-question-design

Skill1 starsChanged 24 days agoMITView on GitHub

Designs tailored discovery questions when a consultant needs reliable evidence for qualification and scoping.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use before discovery interviews, workshops or follow-up meetings with client stakeholders.

    line 9
  2. Distinctive:

    Write neutral open questions before diagnostic or confirming questions.

    line 20
  3. Distinctive:

    Add probes for examples, frequency, consequence, ownership and evidence.

    line 21
  4. Distinctive:

    Test wording for bias, duplication, jargon and time demand.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Discovery Question Design

When to use it

Use before discovery interviews, workshops or follow-up meetings with client stakeholders.

What Claude needs

  • client-context.md for business background
  • Meeting purpose, attendees and available time
  • Existing hypotheses and known facts
  • Decisions the conversation must enable

Method

  1. Convert each required decision into an evidence need.
  2. Group questions by context, trigger, impact, current response, desired outcome and buying process.
  3. Write neutral open questions before diagnostic or confirming questions.
  4. Add probes for examples, frequency, consequence, ownership and evidence.
  5. Prioritise must-ask questions and create optional branches by answer type.
  6. Test wording for bias, duplication, jargon and time demand.

Output format

Provide a sequenced question guide with purpose, primary question, probes, evidence sought and optional branch.

Quality checks

  • Each question serves a stated decision
  • Questions do not embed the preferred answer
  • The must-ask set fits the available time

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free