okhp3-process-intake-and-scopelisted

# okhp3-process-intake-and-scope **OverKill Hill P³** · [overkillhill.com](https://overkillhill.com) · [github.com/OKHP3](https://github.com/OKHP3) ## Purpose This skill guides structured process intake and scope definition using BABOK v3-aligned elicitation techniques. It produces: 1. **Process Intake Record (PIR)** — structured YAML with trigger, actors, inputs, outputs, steps, exceptions, business rules, systems, and controls 2. **Scope Statement** — concise prose defining process boundaries, exclusions, and success criteria The PIR is the foundational input consumed by every downstream skill in the BP-SKILL suite. --- ## When to use this skill - User wants to document a process they describe in natural language, bullet points, or prose - User says "help me scope this," "let's map this process," or "define the boundaries" - You need a structured PIR before calling `stakeholder-and-role-mapping` or `process-narrative-authoring` - User wants to capture business rules, exception paths, or system touchpoints for a workflow ## When NOT to use this skill - A validated PIR with `ready_for_narrative: true` already exists — proceed to `process-narrative-authoring` - User wants a diagram without prior discovery — use `visual-process-modeling` with their description - Do not invent process details the user has not provided — record gaps as `open_questions` --- ## Intake Workflow Execute the following stages in order. Conduct a natural conversation — do not present these