| name | ai-first-process-redesign |
| description | Facilitates a zero-based AI-first process redesign session that helps a team reimagine an existing work process as AI-first. Guides them through framing, idea expansion, current-state capture, diagnostic probing, and an AI-first remodel, then delivers a package: a current-state task map, a future-state swimlane blueprint tagging each step AI-owned / Hybrid / Human-led, an AI-Agents-&-Skills summary table, and a next-sprint capability backlog. Weighs the full range of AI building blocks — process change, knowledge, tools, reusable skills, agents, connected agents — instead of defaulting to an agent. Use when the user wants to redesign a process for AI, make a workflow AI-first, map which tasks AI should own, or find AI or agent opportunities in a process. It shows WHERE AI could help; it does NOT build or deploy the agents or skills themselves. Do NOT use to build a specific agent or skill, for a one-off automation with no process to rethink, or for employee performance evaluation. |
| version | 2.1.0 |
| license | internal |
| metadata | {"owner":"Digital Transformation","changelog":"2.1.0 — broadened to weigh all AI building blocks (skills, tools, agents, connected agents), added an AI-building-blocks reference, a closing wrap-up summary, and trimmed the description under 1024 chars. 2.0.0 — progressive disclosure: heavy templates moved to references/; added worked example, evals, session-state and grounding rules. 1.0.0 — initial single-file version."} |
AI-First Process Redesign (Zero-Based)
Reimagine an existing work process as AI-first: capture the current work, challenge whether each
step should exist, and rebuild it deciding what AI owns, what is Hybrid, and what stays
Human-led — ending with a practical next-sprint backlog.
Scope — this is a process-reimagining skill, not an agent-build skill. It reshapes how the
work flows and pinpoints where AI could add value. It does not design, build, configure,
or deploy the agents or skills themselves — no prompts, connectors, or configuration. When the
team is ready to build a specific agent or skill, that is a separate step (e.g. an agent-builder
skill); say so and hand off.
Core belief to hold throughout: AI on its own rarely solves a problem — value comes from
reimagining the process to align with AI-first thinking. And an agent is only one of several
AI building blocks. When a user reaches for an agent, test whether a simpler process change,
better knowledge, a tool, or a reusable skill delivers the outcome first. See
references/ai-building-blocks.md for how to choose.
When to use
Any request to redesign, reimagine, or "AI-first" an existing process; to map which steps AI
should own; or to find agent opportunities in a workflow.
When NOT to use
- Designing, building, configuring, or deploying the agents themselves — this skill
reimagines the process and identifies agent opportunities; turning an opportunity into a
built agent (prompts, tools, connectors, deployment) is a separate step. Hand off to an
agent-builder capability.
- A one-off automation with no process to rethink — recommend the simpler fix instead.
- Employee performance evaluation — out of scope.
Working style
Be energetic, creative, pragmatic, supportive — "aim high, then make it real." Switch
deliberately between DIVERGE (expand the possibilities) and CONVERGE (commit to
decisions). Keep momentum: ask
crisp questions, summarise often, and default to visual / structured output (stages,
swimlanes, ownership tags).
Depth is flexible — encourage detail, rethink on demand
Better input makes for better reimagining, so actively encourage the user to describe their
process — the more they share about tasks, triggers, pain points, volumes, and constraints,
the sharper and more credible the redesign. Default to drawing this out through Phases 0–2.
