okhp3-future-state-strategy

okhp3-future-state-strategy is a skill for Claude Code, Codex from OKHP3/skillz. It costs 0 tokens per session (1,528 once invoked), scanned A, original, MIT.

A method for designing the desired future version of a business process and planning how to move from the current version to it. It starts with a documented gap analysis, which lists important problems or differences.

In plain words
What is it for?
Use it to redesign a workflow, define how the process should work, prepare input for process documentation, and plan the changes needed to adopt the new process.
Why use it?
It turns identified process problems into a clear target design and an organized change plan. Without a gap analysis, it does not provide the required starting point.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to redesign a workflow, define how the process should work, prepare input for process documentation, and plan the changes needed to adopt the new process.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/okhp3/skillz/okhp3-future-state-strategy
View source ↗ OKHP3/skillz
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add OKHP3/skillz --skill okhp3-future-state-strategy
Clone the repo
git clone --depth 1 https://github.com/OKHP3/skillz

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for okhp3-future-state-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-future-state-strategy/github.svg)](https://agentmods.dev/skills/okhp3/skillz/okhp3-future-state-strategy)
Your own site
<a href="https://agentmods.dev/skills/okhp3/skillz/okhp3-future-state-strategy"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-future-state-strategy/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for okhp3-future-state-strategy

Your own site · 80×15
<a href="https://agentmods.dev/skills/okhp3/skillz/okhp3-future-state-strategy"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-future-state-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,528 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01528
Opus 5 $0.00000 $0.00764
Sonnet 5 $0.00000 $0.00306
Haiku 4.5 $0.00000 $0.00153

Measured 9d ago against content hash ce9c7414a1a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

okhp3-future-state-strategy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/generate-future-state.mjs, tests/validate-skill.test.mjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/okhp3-future-state-strategy/SKILL.md · 156 lines

How it starts

The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.

okhp3-future-state-strategy

OverKill Hill P³ · overkillhill.com · 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 Workflow

Step 1 — Prioritise gaps

Rank gaps from gap-analysis.yaml by severity: critical → major → minor → observation.

Focus the future-state design on resolving all critical and major gaps.

Step 2 — Design to-be steps

For each resolved gap, define the replacement or new step:

  • State the intended action in a single imperative statement
  • Assign a named role (not a person)
  • Define entry and exit criteria
  • Specify any system or tool involved

Step 3 — Validate completeness

Read the full file on GitHub · 156 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 156 lines · 0 tokens per session scan A ce9c7414a1a0

Subscribe to this mod's changes

okhp3-future-state-strategy is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,528 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.