okhp3-process-intake-and-scope

Generates a structured Process Intake Record in YAML using BABOK v3 elicitation techniques.

2|1|Updated Jun 12, 2026

Search Tags:#business analysis #scope definition #PIR #BABOK v3 #process intake

Ready to run

npx skills add https://github.com/OKHP3/skillz --skill okhp3-process-intake-and-scope

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: okhp3-process-intake-and-scope
Source: https://github.com/OKHP3/skillz/tree/main/process-capture/okhp3-process-intake-and-scope
Command: npx skills add https://github.com/OKHP3/skillz --skill okhp3-process-intake-and-scope

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, yaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill facilitates structured process intake and scope definition, helping users capture business processes effectively using BABOK v3 techniques.

Core Features & Use Cases

Structured Process Intake: Guides through structured process intake using BABOK v3 elicitation techniques.
Process Intake Record (PIR): Generates a structured YAML file capturing all aspects of the process.
PIR Validation: Scores the completeness of the PIR and determines readiness for narrative authoring.
Use Case: When a user needs to document a new business process or scope an existing one, this skill helps create a comprehensive PIR that can be used for further analysis and documentation.

Quick Start

Use the okhp3-process-intake-and-scope skill to capture the intake and scope of a new business process.

Frequently Asked Questions about okhp3-process-intake-and-scope

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I structure business process intake for scope definition?▼

Business process intake requires structured elicitation using BABOK v3 techniques to capture process scope effectively. This Skill guides you through creating a comprehensive Process Intake Record (PIR) in YAML format, ensuring all critical process aspects are documented for downstream analysis.

What is a Process Intake Record and when do I need one?▼

A Process Intake Record (PIR) is a structured YAML file capturing all aspects of a business process for documentation. You need a PIR when scoping a new process or documenting an existing one, as it determines readiness for narrative authoring and downstream modeling tasks.

Does this process intake approach use BABOK v3 elicitation techniques?▼

Yes, this process intake approach uses BABOK v3 elicitation techniques to structure the capture of business process information. It applies these established business analysis methods to guide users through comprehensive scope definition and generate a validated Process Intake Record (PIR).

Can I validate the completeness of my scope definition before documentation?▼

Yes, you can validate scope definition completeness because this Skill scores the generated Process Intake Record (PIR) and determines its readiness for narrative authoring. The validation mechanism checks the structured YAML output to ensure all critical process aspects are captured before downstream documentation begins.

Do I need Python and YAML libraries to generate a Process Intake Record?▼

Yes, you need Python and YAML processing libraries to generate a Process Intake Record because this Skill relies on them for data handling and validation. These dependencies are required to process the structured YAML output file capturing your business process intake information.