okhp3-future-state-change-strategy

Topics in the source

• okhp3-future-state-change-strategy
• Purpose
• When to use this skill
• When NOT to use this skill
• Scope Firewall
• Future-State Design Workflow
• Step 1: Prioritise gaps
• Step 2: Design to-be steps

BP-SKILL: Business Process Agent Skill Suite · part of mermaid-diagram-bpmn · OverKill Hill P³ -- Design the target-state (to-be) process and a structured change strategy based on gap analysis findings. The future-state artifact documents the intended process design; the change strategy documents how to get there. -- gap-analysis.yaml exists with at least one critical or major gap User wants to redesign a process based on identified gaps User needs a change management plan to accompany process redesign Preparing the target-state PNS input for okhp3-process-narrative-authoring No gap analysis exists: run okhp3-process-gap-exception-analysis first User wants to document only the current state: use okhp3-as-is-process-capture Scope firewall: do not include confidential employer constraints, proprietary system names, or commercially sensitive process details without explicit user instruction -- This skill operates on process abstractions. Before authoring the future state: Confirm all described gaps are based on user-provided information Do not infer proprietary business rules from industry knowledge without flagging them as assumptions Flag all assumed constraints with confidence: ass

This is an excerpt. Refer to the complete source and its current requirements.