agentleFS
45ck45ck/business-analysis-skills/.agents/skills/pyramid-funnel-diamond-interviewer/SKILL.md

pyramid-funnel-diamond-interviewer

Skill28 starsChanged 8 months agoMITView on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Add transition prompts and contingency prompts.

    line 35
  2. Distinctive:

    Prefer structured outputs over loose prose.

    line 50
  3. Distinctive:

    Do not pretend weak evidence is confirmed fact.

    line 55
  4. Distinctive:

    Do not confuse stakeholder opinion with validated rule or process truth.

    line 56
  5. Distinctive:

    Do not hide missing coverage behind polished wording.

    line 57
  6. Distinctive:

    Do not flatten politically different stakeholders into one generic audience.

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

pyramid-funnel-diamond-interviewer

Purpose

Choose and apply the right interview question structure: pyramid, funnel, or diamond, based on stakeholder type and elicitation objective.

Trigger this skill when

  • You need help choosing how to sequence interview questions.
  • The topic is sensitive, ambiguous, or at risk of producing vague answers.
  • Different stakeholder types require different elicitation pacing.

Expected inputs

  • interview goal
  • stakeholder type
  • topic sensitivity
  • known context

Deliverables

  • recommended structure
  • question order
  • rationale
  • example sequence

Operating procedure

  1. Assess whether the interview should open broad, open narrow, or combine both.
  2. Match stakeholder type and topic sensitivity to pyramid, funnel, or diamond structure.
  3. Draft an ordered question sequence.
  4. Add transition prompts and contingency prompts.
  5. Explain why this structure fits the objective.

Quality gates

  • Structure matches the stakeholder and topic.
  • Questions move from one layer to the next deliberately.
  • The output includes rationale, not just a list.

Handoff targets

  • probe-question-generator
  • interview-plan-designer
  • business-rule-extractor

Output style

  • Be explicit about uncertainty.
  • Prefer structured outputs over loose prose.
  • Separate confirmed findings, inferred findings, and open questions.
  • Preserve source context where practical.

Failure modes to avoid

  • Do not pretend weak evidence is confirmed fact.
  • Do not confuse stakeholder opinion with validated rule or process truth.
  • Do not hide missing coverage behind polished wording.
  • Do not flatten politically different stakeholders into one generic audience.

Minimum output skeleton

## Summary
## Findings
## Structured outputs
## Risks or tensions
## Open questions
## Recommended next skill

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.