okhp3-process-intake-and-scope

Conducts structured business process intake and produces a validated Process Intake Record in YAML.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/OKHP3/refoldec --skill okhp3-process-intake-and-scope-okhp3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okhp3-process-intake-and-scope
Source: https://github.com/OKHP3/refoldec/tree/main/.agents/skills/okhp3-process-intake-and-scope
Command: npx skills add https://github.com/OKHP3/refoldec --skill okhp3-process-intake-and-scope-okhp3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Business analysts and process owners often describe workflows in loose prose, making it hard to capture triggers, actors, inputs, outputs, and business rules consistently. This Skill guides a structured elicitation conversation and converts the answers into a validated, scored Process Intake Record (PIR) that downstream documentation skills can consume. ## Core Features & Use Cases - Guided Elicitation Workflow: A ten-stage intake conversation aligned with BABOK v3 techniques covering trigger, actors, inputs/outputs, scope boundaries, steps, rules, exceptions, systems, and controls. - PIR Generation and Validation: Scripts scaffold a blank PIR YAML, validate schema completeness and enum types, and compute a 0-100 weighted completeness score with a ready_for_narrative handoff gate at 70. - Scope Statement Output: Produces a scope-statement.md defining process boundaries, exclusions, and success criteria alongside the PIR. - Use Case: A user says "help me document our purchase approval workflow." The Skill interviews them stage by stage, records gaps as open_questions instead of guessing, and outputs a scored pir.yaml ready for stakeholder mapping and narrative authoring. ## Quick Start Ask the agent to run a structured intake for a business process you describe, and it will produce a validated PIR YAML file plus a scope statement.

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 document a business process from scratch with an AI agent?▼

Describe the process in natural language and the Skill runs a ten-stage elicitation conversation covering trigger, actors, inputs, outputs, steps, rules, and exceptions. It outputs a structured PIR YAML file and a scope statement without inventing details you did not provide.

What is a Process Intake Record (PIR) in business analysis?▼

A PIR is a structured YAML artifact capturing a process's trigger, actors, inputs, outputs, steps, exceptions, business rules, systems, and controls. It serves as the foundational input for downstream stakeholder mapping, narrative authoring, and process modeling skills.

How is PIR completeness scored before handoff?▼

The score-intake-completeness.mjs script computes a weighted 0-100 score across eleven sections, with actors and steps weighted highest at 15 points each. A score of 70 or above sets ready_for_narrative to true, allowing handoff to downstream skills.

Does the process intake skill require external npm dependencies?▼

No, all scripts are pure ESM Node.js with zero external dependencies, including a built-in minimal YAML parser. You only need a Node.js runtime to run the generate, validate, and scoring scripts.

When should I not use structured process intake?▼

Skip it when a validated PIR with ready_for_narrative already exists, or when the user only wants a diagram without discovery. The Skill also refuses to invent process facts, recording unresolved gaps as open_questions instead.