okhp3-future-state-strategy

Designs to-be processes and ADKAR-aligned change strategies from gap analysis YAML.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? After a gap analysis identifies weaknesses in a business process, teams still need a structured way to design the target-state process and plan how to get there. This Skill turns gap-analysis findings into a future-state process artifact and a change strategy document grounded in ADKAR and Kotter frameworks. ## Core Features & Use Cases - Future-State Design: Converts critical and major gaps from gap-analysis.yaml into to-be steps with roles, entry/exit criteria, effort/risk classification, and flagged assumptions. - Change Strategy Authoring: Produces a change plan covering stakeholder impact, transition sequencing, risk register, communication plan, and success criteria aligned to ADKAR and Kotter. - Scope Firewall: Prevents inclusion of employer-proprietary constraints or inferred business rules unless explicitly authorized, flagging assumptions with confidence markers. - Use Case: A business analyst finishes a gap analysis on a purchase-approval process and needs a redesigned to-be workflow plus a change plan to present to stakeholders before narrative authoring. ## Quick Start Ask the agent to design the future-state process and change strategy from your existing gap-analysis.yaml file.

Frequently Asked Questions about okhp3-future-state-strategy

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

FAQPage Schema
How do I design a to-be process from a gap analysis?▼

Run this Skill after gap analysis has produced gap-analysis.yaml with at least one critical or major gap. It prioritizes gaps by severity, defines replacement steps with named roles and entry/exit criteria, and outputs future-state.yaml plus a change strategy document.

What change management frameworks does this process redesign use?▼

The change strategy aligns with the ADKAR model (Awareness, Desire, Knowledge, Ability, Reinforcement) and Kotter's 8-Step Change Model for high-effort changes. Each change item is assessed against ADKAR to identify the primary change risk.

Can I generate the future-state YAML automatically from gap analysis?▼

Yes, run node scripts/generate-future-state.mjs with your gap-analysis.yaml file. The script converts critical and major gaps into stub change items with change type, effort, and risk classifications, which you then refine.

When should I not use this future-state design skill?▼

Do not use it when no gap analysis exists; run process-gap-and-exception-analysis first. It is also unsuitable for documenting only the current state, and it must not include employer-proprietary constraints without explicit user authorization.

What happens to the future-state output after design?▼

The future-state.yaml is handed off to process-intake-and-scope or process-narrative-authoring to create the target-state process narrative. Its to-be steps map directly to activity_sequence.activities in the new process narrative structure.