← ClaudeAtlas

okhp3-future-state-strategylisted

Design a target-state process and a structured change strategy from a gap analysis. Use this skill when the user wants to redesign a process after gaps have been identified; when they ask "what should the process look like", "how do we fix this", "design the to-be process", or "build a change plan". Produces a future-state process artifact and a change strategy document. This is a recommended extension skill — use after process-gap-and-exception-analysis has produced a gap analysis. Scope firewall applies: never include employer-proprietary constraints without explicit user authorisation.
OKHP3/skillz · ★ 3 · AI & Automation · score 75
Install: claude install-skill OKHP3/skillz
# okhp3-future-state-strategy **OverKill Hill P³** · [overkillhill.com](https://overkillhill.com) · [github.com/OKHP3](https://github.com/OKHP3) ## Purpose 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. --- ## When to use this skill - `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 `process-narrative-authoring` ## When NOT to use this skill - No gap analysis exists — run `process-gap-and-exception-analysis` first - User wants to document only the current state — use `as-is-process-capture` - Scope firewall: do not include confidential employer constraints, proprietary system names, or commercially sensitive process details without explicit user instruction --- ## Scope Firewall 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: assumed` in the future-state YAML - Do not include employer-identifying details in any generated artifact --- ## Future-State Design Wo