agentleFS
OKHP3OKHP3/skillz/.agents/skills/okhp3-elicitation-interviews/SKILL.md

okhp3-elicitation-interviews

Skill3 starsChanged 2 months agoMITView on GitHub

Plan and facilitate structured elicitation sessions using BABOK v3 interview and workshop techniques. Use this skill when you need to gather process knowledge from subject matter experts; when the user wants a question plan before an interview or workshop; when elicitation is incomplete and gaps need targeted follow-up; when they say "help me interview the process owner", "prepare questions for the workshop", or "what should I ask to fill in the missing steps". Produces a question plan and elicitation notes template.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not fabricate answers from the question plan — only record what participants confirm

    line 61
  2. Very specific:

    If trigger.event_type is absent → lead with Stage 1 trigger questions

    line 85
  3. Very specific:

    If actors has no approver → probe approval chain: *"Who has the authority to stop or reject this?"*

    line 86
  4. Very specific:

    If exceptions is empty → probe with historical incident: *"What was the hardest version of this you've dealt with?"*

    line 87
  5. Very specific:

    If business_rules is empty → probe obligation: *"Are there any rules you must follow that an outsider wouldn't know?"*

    line 88
  6. Very specific:

    After elicitation, update pir.yaml and re-run process-intake-and-scope scoring.

    line 117

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

okhp3-elicitation-interviews

OverKill Hill P³ · overkillhill.com · github.com/OKHP3

Purpose

Generate a structured elicitation question plan and facilitate evidence-based process interviews using BABOK v3 §10.25 and §10.50 techniques. The plan targets known gaps in the PIR and provides sequenced, open-ended questions mapped to each PIR section.


When to use this skill

  • PIR exists but has completeness_score < 70 or open_questions that need targeted follow-up
  • User needs to interview a subject matter expert and wants a prepared question set
  • User is planning a process discovery workshop and needs a facilitator guide
  • You need to fill elicitation gaps before proceeding to process-narrative-authoring

When NOT to use this skill

  • PIR is already complete (score ≥ 70, no open_questions) — proceed directly to process-narrative-authoring
  • User has no access to process owners — document the gap and proceed with assumptions flagged
  • Do not fabricate answers from the question plan — only record what participants confirm

Question Plan Generation

scripts/generate-question-plan.mjs reads the PIR and generates targeted questions for each incomplete section.

Question categories

PIR sectionQuestion typeSample opening
triggerContext"What makes you realise the process needs to start today?"
actorsRole"Who else touches this beyond the people we've named?"
inputsArtefact"What document or data do you need before you can begin?"
outputsArtefact"What does the person receiving your output actually do with it?"
stepsSequence"Walk me through what you do on a typical day this runs."
business_rulesConstraint"Is there a policy or procedure that forces you to do it this way?"
exceptionsEdge case"Tell me about the last time this went wrong. What happened?"
systemsTool"Which systems do you open, update, or check during this process?"
controlsGovernance"How do you know when the process has been done correctly?"

Branching logic

  • If trigger.event_type is absent → lead with Stage 1 trigger questions
  • If actors has no approver → probe approval chain: "Who has the authority to stop or reject this?"
  • If exceptions is empty → probe with historical incident: "What was the hardest version of this you've dealt with?"
  • If business_rules is empty → probe obligation: "Are there any rules you must follow that an outsider wouldn't know?"

Facilitation Guidelines

  1. Open with context — read back the process name and one-sentence scope; confirm it is correct
  2. Use the question plan in order — complete highest-gap sections first
  3. Probe with "tell me more" — do not accept one-word answers for steps or rules
  4. Record verbatim — capture exact wording of rules and exceptions; paraphrase only for clarity
  5. Flag uncertainty — mark any answer prefaced with "I think" or "usually" as confidence: low
  6. Close with open invitation — "Is there anything else you think I should know to document this correctly?"
  7. Write up within 24 hours — update the PIR before memory fades

Elicitation Notes Template

The elicitation-notes.md output contains:

  • Session metadata (date, participants, facilitator, method)
  • Answers mapped to PIR sections
  • Verbatim quotes for business rules
  • Confidence flags for uncertain answers
  • Outstanding items that need follow-up

Handoff Instruction

After elicitation, update pir.yaml and re-run process-intake-and-scope scoring. When score ≥ 70, pass pir.yaml to stakeholder-and-role-mapping and then process-narrative-authoring.


References

Load on demand:

  • references/babok-elicitation-techniques.md — BABOK v3 §4, §10.14, §10.25, §10.50 technique summaries and question frameworks

Scripts

  • scripts/generate-question-plan.mjs — generates elicitation question plan from PIR scope and open_questions

Assets

  • assets/fixtures/question-plan-example.yaml — canonical question plan for purchase-approval intake

About

Built by Jamie Hill · OverKill Hill P³ Published at github.com/OKHP3 Part of the OKHP3/skillz Agent Skill library. MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.

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.