skills.rest
OKHP3
OKHP3COMMUNITY
Explore all skills by this author →
WebsiteGitHub

okhp3-as-is-process-capture

Normalize current-state business process descriptions into structured YAML artifacts.

2|1|Updated Jun 12, 2026
Search Tags:#business process#process documentation#yaml#gap analysis#as-is
One-click install
npx skills add https://github.com/OKHP3/skillz --skill okhp3-as-is-process-capture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okhp3-as-is-process-capture
Source: https://github.com/OKHP3/skillz/tree/main/process-capture/okhp3-as-is-process-capture
Command: npx skills add https://github.com/OKHP3/skillz --skill okhp3-as-is-process-capture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires process-intake-and-scope, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill captures and normalizes current-state process descriptions into structured YAML artifacts, streamlining gap analysis and documentation.

Core Features & Use Cases

  • Capture & Normalize: Gather and standardize process steps into a YAML format with stable identifiers.
  • Gap Analysis Preparation: Create a baseline for process improvement projects.
  • Use Case: Utilize this Skill when documenting an existing process, setting a benchmark for improvement efforts.

Quick Start

Execute the okhp3-as-is-process-capture skill on the current process steps.

Frequently Asked Questions about okhp3-as-is-process-capture

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

FAQPage Schema
How do I document as-is business processes for gap analysis?▼

Normalizing as-is process descriptions into structured YAML artifacts captures step sequences, actors, and stable identifiers. This creates a baseline for process improvement and gap analysis.

What is the best way to normalize current-state process steps into YAML?▼

Normalizing as-is process steps into YAML requires assigning stable identifiers, identifying step sequences, and mapping actors. This structured format automates gap analysis preparation.

Do I need process scoping data before capturing current-state process documentation?▼

Capturing as-is process documentation requires process intake and scoping data as a prerequisite. This preliminary input defines the boundaries for normalizing steps into YAML artifacts.

Can I integrate normalized YAML process descriptions with other business process tools?▼

Normalized YAML process descriptions support integration with other BP-SKILL suite components. This integration facilitates downstream process gap analysis and continuous improvement workflows.

Does as-is process capture support identification of step sequences and actors?▼

As-is process capture supports identifying step sequences and actors during normalization. It assigns stable identifiers to each element, creating a structured YAML baseline for gap analysis.

Related Skills

Explore More Software Engineering Skills→
OKHP3OKHP3
2

okhp3-process-intake-and-scope

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

Community
Advanced
OKHP3OKHP3
2

okhp3-future-state-and-change-strategy

Design future-state processes and ADKAR-aligned change strategies from gap analysis.

Community
Intermediate
deanpetersdeanpeters
6.4k

customer-journey-map

Visualize end-to-end customer journeys with stages, touchpoints, emotions, and KPIs.

Community
Basic
ebrahim-saniebrahim-sani

candlestick

Detect candlestick patterns and generate composite bullish or bearish signals from OHLCV data.

Community
Intermediate