okhp3-process-intake-and-scope
Conduct structured process intake and scope definition using BABOK v3 elicitation techniques. Use this skill when the user wants to document a business process from scratch; when they describe a workflow, procedure, or set of steps and need it structured; when they ask to scope a process, define process boundaries, or capture business rules; when they say \"help me document this process\", \"let's scope out this workflow\", or \"what are the inputs and outputs\"; when you need a Process Intake Record (PIR) as input for downstream narrative, modeling, or SOP skills. This is the first-pass discovery skill; once a PIR exists, use okhp3-elicitation-interviews to fill remaining gaps rather than restarting intake.
Target: Office & team collaboration. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- okhp3-process-intake-and-scope
- Purpose
- When to use this skill
- When NOT to use this skill
- Intake Workflow
- Stage 0: Orientation
- Stage 1: Trigger
- Stage 2: Actors
BP-SKILL: Business Process Agent Skill Suite · part of mermaid-diagram-bpmn · OverKill Hill P³ -- 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. -- 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 okhp3-stakeholder-and-role-mapping or okhp3-process-narrative-authoring User wants to capture business rules, exception paths, or system touchpoints for a workflow A validated PIR with readyfornarrative: true already exists: proceed to okhp3-process-narrative-authoring A PIR exists but has gaps to fill through targeted follow-up: use okhp3-elicitation-interviews instead of restarting intake User wants a diagram without p
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- OKHP3/skillz
- Source file
- process-capture/okhp3-process-intake-and-scope/SKILL.md
- Fixed revision
- 7b187777d42ab7bc7bab1e5f2c940cd3139ecebf
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: OKHP3/skillz · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T10:00:55.333Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.