Process Optimization
Map a painful solo or small-team workflow, cut waste, and get a before/after plan when launches, support, or shipping steps feel slow or over-handoff.
Overview
Process Optimization is a journey-wide agent skill that analyzes business and shipping workflows and recommends a leaner future state—usable whenever a solo builder needs to fix bottlenecks before committing to more head
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill process-optimizationWhat is this skill?
- Four-part framework: map current state, identify waste, design future state, measure impact
- Waste categories: waiting, rework, handoffs, over-processing, manual work
- Future-state tactics: eliminate steps, automate, reduce handoffs, parallelize, checkpoints vs gates
- Delivers before/after comparison with impact estimates and implementation plan
- 4-step analysis framework (map, waste, future state, measure impact)
- 5 waste categories explicitly listed
Adoption & trust: 1.7k installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You keep hitting queues, rework, and handoffs in a workflow you already run, and ad-hoc tweaks do not show measurable time or error savings.
Who is it for?
One-person founders or micro-teams naming specific inefficient processes across build, ship, support, or growth ops.
Skip if: Pure coding bugs, one-line automation snippets without a end-to-end process story, or regulated compliance redesign that needs licensed consultants.
When should I use this skill?
When the user says this process is slow, how can we improve, streamline this workflow, too many steps, bottleneck, or describes an inefficient process to fix.
What do I get? / Deliverables
You receive a documented current-state map, waste analysis, future-state design, and impact-backed implementation plan you can execute incrementally.
- Before/after process comparison
- Improvement recommendations with estimated impact
- Implementation plan for the future state
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Trim the steps between prototype feedback and go/no-go so you stop re-validating the same assumptions weekly.
Parallelize independent release checks and replace approval gates with checkpoints before launch day.
Map incident triage handoffs and automate status updates that currently sit in waiting queues.
Reduce rework in onboarding email sequences caused by manual copy-paste between tools.
Shorten planning ceremonies that add over-processing without changing what ships each sprint.
How it compares
Structured process-improvement workflow—not a generic brainstorming session or a single integration skill.
Common Questions / FAQ
Who is process-optimization for?
Solo builders and indie operators who own end-to-end workflows and want a systematic way to remove delays, rework, and manual steps.
When should I use process-optimization?
Use it during Operate when support or deploy rituals stall; during Ship when release checklists balloon; during Grow when lifecycle handoffs fail; or during Build/PM when planning ceremonies accumulate gates—whenever you say the process is slow or has too many steps.
Is process-optimization safe to install?
It recommends organizational changes in text only; review the Security Audits panel on this page and avoid pasting secrets when describing internal workflows.
SKILL.md
READMESKILL.md - Process Optimization
# Process Optimization Analyze existing processes and recommend improvements. ## Analysis Framework ### 1. Map Current State - Document every step, decision point, and handoff - Identify who does what and how long each step takes - Note manual steps, approvals, and waiting times ### 2. Identify Waste - **Waiting**: Time spent in queues or waiting for approvals - **Rework**: Steps that fail and need to be redone - **Handoffs**: Each handoff is a potential point of failure or delay - **Over-processing**: Steps that add no value - **Manual work**: Tasks that could be automated ### 3. Design Future State - Eliminate unnecessary steps - Automate where possible - Reduce handoffs - Parallelize independent steps - Add checkpoints (not gates) ### 4. Measure Impact - Time saved per cycle - Error rate reduction - Cost savings - Employee satisfaction improvement ## Output Produce a before/after process comparison with specific improvement recommendations, estimated impact, and an implementation plan.