okhp3-future-state-strategy
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.
Target: Office & team collaboration. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- okhp3-future-state-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
OverKill Hill P³ · overkillhill.com · github.com/OKHP3 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 process-narrative-authoring 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 -- 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-i
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- OKHP3/skillz
- Source file
- .agents/skills/okhp3-future-state-strategy/SKILL.md
- Fixed revision
- 7b187777d42ab7bc7bab1e5f2c940cd3139ecebf
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: OKHP3/skillz · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T10:00:53.617Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.