process-design
/process-design
Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold. Use this when the same failure keeps recurring, when a handoff between teams is unreliable, when onboarding a repeated task, when work takes far longer than the work itself, or when deciding whether to automate, standardize, or eliminate a process.
- Author
- cbrock84 ↗
- Repository
- headcount ↗
- Licence
- MIT
- Last repository change
- 18.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 18.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold. Use this when the same failure keeps recurring, when a handoff between teams is unreliable, when onboarding a repeated task, when work takes far longer than the work itself, or when deciding whether to automate, standardize, or eliminate a process.
Original author description
Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold. Use this when the same failure keeps recurring, when a handoff between teams is unreliable, when onboarding a repeated task, when work takes far longer than the work itself, or when deciding whether to automate, standardize, or eliminate a process.
How it works
- Map what happens, not what is supposed to happen
- Find the real constraint
- Redesign
- Make it hold
- Sources
- Never
- Return contract
SKILL.md preview
--- name: process-design description: Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold. Use this when the same failure keeps recurring, when a handoff between teams is unreliable, when onboarding a repeated task, when work takes far longer than the work itself, or when deciding whether to automate, standardize, or eliminate a process. --- # Process design ## Map what happens, not what is supposed to happen Follow a real instance end to end and record every step, handoff, wait, and rework loop. Talk to the people doing it, who will describe several steps that exist nowhere in the documentation and one or two that everyone has quietly stopped doing. Then measure two things: - **Touch time** — how long the work actually takes. - **Elapsed time** — how long it takes to get through. The gap between them is the process. In most broken processes, work is waiting more than ninety percent of the time, which means speeding up the work changes almost nothing. Attack the waits. ## Find the real constraint One step governs throughput. Improving anything else produces inventory in front of the constraint and no more output. Find it: the step with a queue in front of it. Common constraints that are not the obvious step: a single approver, a specialist everything routes through, a system that only one team can access, and a batch cycle that makes everything wait for the weekly run. ## Redesign In this order, because the order is the leverage: 1. **Eliminate.** Does this step need to exist? Many exist to catch a failure that a different fix would prevent entirely. 2. **Simplify.** Fewer handoffs, fewer approvals, fewer systems. Every handoff is a place work stops. 3. **Standardize.** One way of doing it, written down, with the decision rules explicit. 4. **Automate.** Last. Automating an unexamined process makes a bad process faster and much harder to change. Push approval to the lowest level that can be accountable, and set thresholds so routine cases do not queue behind exceptional ones. ## Make it hold A documented process that relies on discipline degrades within a quarter. Build the control into the system: required fields, blocking gates, defaults that are correct, automated handoffs. **Never fix a recurring failure with a reminder.** If people are forgetting a step, the system permits forgetting it. Fix that. ## Sources `references/sources.md` in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding. ## Never - Redesign from the documented process. Map what people actually do first. - Optimize a step that is not the constraint. Everything you speed up ahead of it just queues. - Add an approval to prevent a failure that happened once. - Hand over a process with no owner and no measure. It reverts within a quarter. ## Return contract Current state with elapsed and touch time, the constraint and its evidence, the redesign, what it costs to implement, and the measure that will show it worked.
Files in this package (2)
- SKILL.md 3 KB
- references/sources.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · cbrock84/headcount | 90 | MIT |
| ChemE-as-Code/core | 100 | AGPL-3.0 |
Database snapshot: 13.11.2026 · package version b49410bfcb7d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100automation-process-design
Redesigns a business process before it is automated - removing waste, standardising inputs, writing down decision rules, defining exceptions and owners - and produces a future-state design that marks each step as human, flow, AI or desktop flow. Use when an assessment says a… - 100process-doc
Documents recurring processes as step-by-step SOPs with decision points, edge cases, and a named owner, so anyone can run the process correctly without asking. Use when someone asks "write an SOP for this", "document our onboarding process", "this only lives in one person's… - 100process-mapping
Map as-is and to-be business processes using structured flow notation. Use when analyzing workflows, identifying bottlenecks, or designing process improvements. - 91process-mapping
梳理业务流程——绘制流程图、明确控制节点、识别流程瓶颈和冗余环节。 在审计预备阶段或了解业务阶段使用。 - 100value-stream-mapping
Build current-state and future-state value stream maps for a business or delivery process, quantifying process time, wait time, percent complete and accurate, lead time, and flow efficiency, and identifying the eight wastes. Use when a process is slow, handoff-heavy, or full of… - 100process-mapper
Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work…