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.
Extract manually supplied ChatGPT conversations into standalone, actionable Markdown. Use when the user pastes a ChatGPT chat, Project thread, Canvas, Deep Research report, search answer, prompt-response sequence, generated file or image reference, or export excerpt and wants its goals, reasoning, decisions, reusable assets, next actions, provenance, and missing sidecars preserved at rapid, balanced, comprehensive, essential, substantial, exhaustive, scan, distill, or catalog depth. Use for cont