Simplify user workflows

Removes unnecessary steps and repeated input while preserving meaningful decisions and complete task progress.

workflow-simplification

See how it helps

When is it useful?

Use when a simple user goal requires too many disconnected screens.

What does it help you do?

Maps the entire task including prerequisites and handoffs.
Combines cohesive steps and reuses already available information.
Preserves distinct approval, save and completion semantics.

Try asking this

Simplify project setup across four screens without merging draft saving with final project activation. Reuse organization details already known during setup, but keep activation explicit. A user should save an incomplete draft and resume without accidentally starting live work.

Detailed documentation

Read the skill’s original instructions, examples and checks in their authored language.

Details…Show less

Workflow Simplification

Use this skill to trace a user workflow from initial intent to final outcome and remove every unnecessary step, context switch, memory burden, and repetitive input.

Workflow

Map the full user task across screens:
- Count not just mouse clicks, but cognitive transitions:
  - How many times does the user have to remember a value from Screen A to type it into Screen B?
  - How many modals, drawers, or page loads interrupt a single continuous thought?
  - Where is the user forced to leave the current page just to look up context needed to make a decision?
Eliminate redundant data entry and friction:
- Carry context forward: When creating an item from inside a project, category, or filtered view, pre-select that project/category automatically instead of forcing the user to pick it again from a dropdown.
- Replace unnecessary confirmation modals with Undo or inline state:
  - Do not pop up "Are you sure you want to archive this item?" for easily reversible actions — execute immediately and offer a one-click Undo toast.
  - Reserve blocking confirmation dialogs strictly for destructive, irreversible, or high-cost actions (Delete project, Revoke active key, Publish live workflow), and state the exact consequence in the dialog.
Keep cohesive tasks together; support progress on long ones:
- Do not chop a 3-field task into a multi-page wizard, and do not cram a 40-field enterprise onboarding flow into a single cramped modal.
- For genuinely multi-stage workflows, provide visible progress, automatic draft saving, and the ability to pause and resume without losing work.
Verify that merging steps preserves distinct semantics:
- Before combining two features or steps into one, verify that their underlying permissions, side effects, and user expectations are truly shared so merging them does not create a confusing hybrid control.

Included files 1

SKILL.md