Process Improvement
Analyze process bottlenecks and propose improvements for "$ARGUMENTS". Identify recurring themes across retrospectives, map the value stream, and create a prioritized improvement backlog based on impact and effort.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"project-management-process-improvement","workflow":"project-management","phase":4,"project":"<project>","event":"skipped","artifact":"04-improve.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 4 (Improve) of the Scrum workflow (project-management); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or project-management when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"project-management-process-improvement","workflow":"project-management","phase":4,"project":"<project>","event":"refused","artifact":"04-improve.md","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"project-management-process-improvement","workflow":"project-management","phase":4,"project":"<project>","event":"started","artifact":"04-improve.md","note":""}.
Check that .singularskills/project-management/<project>/00-initiate.md exists. If it does not, tell the user to run an Initiate skill first (e.g., project-charter) and stop.
Process
Read existing context:
- Read
.singularskills/project-management/<project>/00-initiate.md for project context and team setup
- Read
.singularskills/project-management/<project>/03-review.md if it exists (for sprint review results, sprint metrics, velocity trends, and commitment ratios)
- Read
.singularskills/project-management/<project>/04-improve.md if it exists (for retrospective action items, previous process improvements, and team health data)
- Read
.singularskills/project-management/<project>/02-sprint.md if it exists (for standup history, blocker log, and daily flow patterns)
- Read
.singularskills/project-management/<project>/01-plan.md if it exists (for sprint planning data and estimation accuracy)
Identify recurring themes across retrospectives:
- Review all retrospective action items and themes from
.singularskills/project-management/<project>/04-improve.md
- Flag any blocker, complaint, or theme that has appeared in 2 or more retrospectives
- Categorize recurring themes: process issues, tooling gaps, communication breakdowns, skill gaps, external dependencies
- Note which action items were committed to but never completed — these represent systemic resistance to change
- Identify the top 3 recurring themes by frequency and severity
Analyze flow bottlenecks:
- Examine where work piles up in the team's workflow by reviewing sprint data
- Check each stage for signs of bottleneck:
- Backlog refinement — are stories entering sprints without clear requirements?
- Development — are developers blocked waiting for decisions, designs, or dependencies?
- Code review — are PRs sitting in review for more than 1 day on average?
- Testing — is QA a single point of failure? Are bugs found late in the cycle?
- Deployment — is the release process manual, risky, or infrequent?
- Quantify each bottleneck where possible: average wait time, number of items stuck, frequency of occurrence
- Rank bottlenecks by their impact on overall flow (the biggest constraint limits the whole system)
Map the current value stream:
- Document the journey of a typical story from idea to production
- For each stage, estimate:
- Process time — how long active work takes at this stage
- Wait time — how long the item sits idle between stages
- Rework rate — how often items are sent back to a previous stage
- Calculate total lead time (idea to production) and total process time (actual work)
- Calculate flow efficiency: process time / lead time x 100% (typical teams are 15-25% efficient)
- Identify the stages with the highest wait time — these are the improvement opportunities
Propose specific process changes:
- For each identified bottleneck or recurring theme, propose a concrete process change
- Each proposal must include:
- Problem statement — what is happening and its measurable impact
- Proposed change — what specifically to do differently
- Expected outcome — what improvement to expect and how to measure it
- Risks — what could go wrong with this change
- Ensure proposals are actionable by the team (not "management should do X" but things the team controls)
- Consider both technical solutions (automation, tooling) and process solutions (ceremonies, agreements)
Estimate effort for each change:
- Rate each proposed change on implementation effort: Low (< 1 day), Medium (1-5 days), High (> 5 days)
- Consider the type of effort required: tooling setup, habit change, organizational approval, training
- Note which changes require buy-in from outside the team (stakeholders, other teams, leadership)
- Identify any changes that can be tried as experiments with easy rollback
Prioritize improvements by impact/effort ratio:
- Score each improvement on impact (1-5) and effort (1-5, where 1 is lowest effort)
- Calculate the impact/effort ratio for each improvement
- Categorize into quadrants:
- Quick wins (high impact, low effort) — do these first
- Strategic investments (high impact, high effort) — plan and schedule these
- Easy fills (low impact, low effort) — do when convenient
- Avoid (low impact, high effort) — deprioritize or discard
- Recommend the top 3 improvements to pursue in the next sprint or iteration
Create improvement backlog:
- List all proposed improvements as backlog items, ordered by priority
- For each item, include: description, expected impact, effort estimate, owner (if assigned), target date
- Mark which items are experiments (time-boxed trials) vs. permanent changes
- Note dependencies between improvements (e.g., "automate deployment" before "increase release frequency")
- Schedule a review checkpoint to evaluate whether implemented changes had the expected effect
Write the artifact — append to .singularskills/project-management/<project>/04-improve.md under a ## Process Improvement section. Create the file with a # Improve — <project> heading if it does not exist; if a ## Process Improvement section already exists, replace only that section. The section contains:
- Recurring Themes — top themes from retrospectives with frequency and severity
- Flow Bottlenecks — ranked bottlenecks with quantified impact
- Value Stream Map — stages from idea to production with process time, wait time, and flow efficiency
- Proposed Changes — each proposal with problem, solution, expected outcome, and risks
- Impact/Effort Matrix — all improvements plotted by impact and effort with quadrant classification
- Improvement Backlog — prioritized list of improvements with owners and target dates
- Review Checkpoint — date and criteria for evaluating whether changes are working
Output
Process improvement analysis appended to .singularskills/project-management/<project>/04-improve.md. Present a summary highlighting:
- Top 3 recurring themes across retrospectives
- Biggest flow bottleneck and its measured impact
- Flow efficiency percentage (process time vs. lead time)
- Top 3 recommended improvements (quick wins first)
- Review checkpoint date for evaluating results
Record the run. After you have written your section, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"project-management-process-improvement","workflow":"project-management","phase":4,"project":"<project>","event":"finished","artifact":"04-improve.md","note":""}.
This artifact is shared by every skill of phase 4 (Improve). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (skill is the phase title, started the time of that first write; gate is passed when the gate ran clean and skipped under --skip-checks); if it already exists, leave the block alone except to update finished and to set gate to the worst value among the sections (skipped over passed).
---
skill: Improve
workflow: project-management
phase: 4
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
Open your ## Process Improvement section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is project-management-process-improvement).
End your section with ### Decisions and ### Open questions (one level under your ## Process Improvement heading, so the section stays one block), in this shape:
### Decisions
- <what was chosen> — <why> — <what was rejected>
### Open questions
- <what the next phase or a reviewer must settle>
1---2name: project-management-process-improvement3description: Analyze process bottlenecks across sprints — recurring retro themes, flow bottlenecks, a value stream map with flow efficiency — into a prioritized improvement backlog. Use when the same problems keep coming up sprint after sprint and the user wants to find the constraint and decide what to change. Not for running a single retro; see /project-management-retrospective.4metadata:5 source: https://skillmd.com/skills/bromso/project-management-process-improvement6 argument-hint: "[project] [--skip-checks]"7 workflow: project-management8 phase: 49 artifact: 04-improve.md10---1112# Process Improvement1314Analyze process bottlenecks and propose improvements for "$ARGUMENTS". Identify recurring themes across retrospectives, map the value stream, and create a prioritized improvement backlog based on impact and effort.1516**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"project-management-process-improvement","workflow":"project-management","phase":4,"project":"<project>","event":"skipped","artifact":"04-improve.md","note":"<reason or \"none given\">"}`.1718## Prerequisites1920**Part of a workflow.** This skill is phase 4 (Improve) of the Scrum workflow (`project-management`); cross-domain workflows run it too. First check `.singularskills/log.jsonl` for an open run for this project: a `run-started` line with `"project":"<project>"` and no later `run-finished` line for the same `workflow` and `project`. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the `workflow` skill with the workflow the user asked for, or `project-management` when they named none, followed by `<project>`; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.2122Run this skill's gate before writing: `sh <this skill's folder>/scripts/gate.sh <project> <project root>`, where `<project root>` is the folder that contains `.singularskills/` (use `.` when you are already there). If it exits non-zero, stop and tell the user what it printed, unless `--skip-checks` was given (see Arguments). On a refusal, before you stop, append this line to `.singularskills/log.jsonl` (create the folder and file if missing): `{"ts":"<ISO timestamp>","skill":"project-management-process-improvement","workflow":"project-management","phase":4,"project":"<project>","event":"refused","artifact":"04-improve.md","note":"<what the gate printed>"}`. Once the gate has passed, or under `--skip-checks` once you have appended the `skipped` line, append this line before you start work: `{"ts":"<ISO timestamp>","skill":"project-management-process-improvement","workflow":"project-management","phase":4,"project":"<project>","event":"started","artifact":"04-improve.md","note":""}`.2324Check that `.singularskills/project-management/<project>/00-initiate.md` exists. If it does not, tell the user to run an Initiate skill first (e.g., project-charter) and stop.2526## Process27281. **Read existing context:**29 - Read `.singularskills/project-management/<project>/00-initiate.md` for project context and team setup30 - Read `.singularskills/project-management/<project>/03-review.md` if it exists (for sprint review results, sprint metrics, velocity trends, and commitment ratios)31 - Read `.singularskills/project-management/<project>/04-improve.md` if it exists (for retrospective action items, previous process improvements, and team health data)32 - Read `.singularskills/project-management/<project>/02-sprint.md` if it exists (for standup history, blocker log, and daily flow patterns)33 - Read `.singularskills/project-management/<project>/01-plan.md` if it exists (for sprint planning data and estimation accuracy)34352. **Identify recurring themes across retrospectives:**36 - Review all retrospective action items and themes from `.singularskills/project-management/<project>/04-improve.md`37 - Flag any blocker, complaint, or theme that has appeared in 2 or more retrospectives38 - Categorize recurring themes: process issues, tooling gaps, communication breakdowns, skill gaps, external dependencies39 - Note which action items were committed to but never completed — these represent systemic resistance to change40 - Identify the top 3 recurring themes by frequency and severity41423. **Analyze flow bottlenecks:**43 - Examine where work piles up in the team's workflow by reviewing sprint data44 - Check each stage for signs of bottleneck:45 - **Backlog refinement** — are stories entering sprints without clear requirements?46 - **Development** — are developers blocked waiting for decisions, designs, or dependencies?47 - **Code review** — are PRs sitting in review for more than 1 day on average?48 - **Testing** — is QA a single point of failure? Are bugs found late in the cycle?49 - **Deployment** — is the release process manual, risky, or infrequent?50 - Quantify each bottleneck where possible: average wait time, number of items stuck, frequency of occurrence51 - Rank bottlenecks by their impact on overall flow (the biggest constraint limits the whole system)52534. **Map the current value stream:**54 - Document the journey of a typical story from idea to production55 - For each stage, estimate:56 - **Process time** — how long active work takes at this stage57 - **Wait time** — how long the item sits idle between stages58 - **Rework rate** — how often items are sent back to a previous stage59 - Calculate total lead time (idea to production) and total process time (actual work)60 - Calculate flow efficiency: process time / lead time x 100% (typical teams are 15-25% efficient)61 - Identify the stages with the highest wait time — these are the improvement opportunities62635. **Propose specific process changes:**64 - For each identified bottleneck or recurring theme, propose a concrete process change65 - Each proposal must include:66 - **Problem statement** — what is happening and its measurable impact67 - **Proposed change** — what specifically to do differently68 - **Expected outcome** — what improvement to expect and how to measure it69 - **Risks** — what could go wrong with this change70 - Ensure proposals are actionable by the team (not "management should do X" but things the team controls)71 - Consider both technical solutions (automation, tooling) and process solutions (ceremonies, agreements)72736. **Estimate effort for each change:**74 - Rate each proposed change on implementation effort: Low (< 1 day), Medium (1-5 days), High (> 5 days)75 - Consider the type of effort required: tooling setup, habit change, organizational approval, training76 - Note which changes require buy-in from outside the team (stakeholders, other teams, leadership)77 - Identify any changes that can be tried as experiments with easy rollback78797. **Prioritize improvements by impact/effort ratio:**80 - Score each improvement on impact (1-5) and effort (1-5, where 1 is lowest effort)81 - Calculate the impact/effort ratio for each improvement82 - Categorize into quadrants:83 - **Quick wins** (high impact, low effort) — do these first84 - **Strategic investments** (high impact, high effort) — plan and schedule these85 - **Easy fills** (low impact, low effort) — do when convenient86 - **Avoid** (low impact, high effort) — deprioritize or discard87 - Recommend the top 3 improvements to pursue in the next sprint or iteration88898. **Create improvement backlog:**90 - List all proposed improvements as backlog items, ordered by priority91 - For each item, include: description, expected impact, effort estimate, owner (if assigned), target date92 - Mark which items are experiments (time-boxed trials) vs. permanent changes93 - Note dependencies between improvements (e.g., "automate deployment" before "increase release frequency")94 - Schedule a review checkpoint to evaluate whether implemented changes had the expected effect95969. **Write the artifact** — append to `.singularskills/project-management/<project>/04-improve.md` under a `## Process Improvement` section. Create the file with a `# Improve — <project>` heading if it does not exist; if a `## Process Improvement` section already exists, replace only that section. The section contains:97 - **Recurring Themes** — top themes from retrospectives with frequency and severity98 - **Flow Bottlenecks** — ranked bottlenecks with quantified impact99 - **Value Stream Map** — stages from idea to production with process time, wait time, and flow efficiency100 - **Proposed Changes** — each proposal with problem, solution, expected outcome, and risks101 - **Impact/Effort Matrix** — all improvements plotted by impact and effort with quadrant classification102 - **Improvement Backlog** — prioritized list of improvements with owners and target dates103 - **Review Checkpoint** — date and criteria for evaluating whether changes are working104105## Output106107Process improvement analysis appended to `.singularskills/project-management/<project>/04-improve.md`. Present a summary highlighting:108- Top 3 recurring themes across retrospectives109- Biggest flow bottleneck and its measured impact110- Flow efficiency percentage (process time vs. lead time)111- Top 3 recommended improvements (quick wins first)112- Review checkpoint date for evaluating results113114**Record the run.** After you have written your section, append this line to `.singularskills/log.jsonl` (the `started` line of Prerequisites, with `"event":"finished"`): `{"ts":"<ISO timestamp>","skill":"project-management-process-improvement","workflow":"project-management","phase":4,"project":"<project>","event":"finished","artifact":"04-improve.md","note":""}`.115116This artifact is shared by every skill of phase 4 (Improve). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (`skill` is the phase title, `started` the time of that first write; `gate` is `passed` when the gate ran clean and `skipped` under `--skip-checks`); if it already exists, leave the block alone except to update `finished` and to set `gate` to the worst value among the sections (`skipped` over `passed`).117118```yaml119---120skill: Improve121workflow: project-management122phase: 4123project: <project>124started: <ISO timestamp>125finished: <ISO timestamp>126agent: <the agent you run in, or "unknown">127gate: <passed|skipped>128---129```130131Open your `## Process Improvement` section with one italic line, `*<skill name> · <ISO timestamp> · gate: <passed|skipped>*` (your skill name is `project-management-process-improvement`).132133End your section with `### Decisions` and `### Open questions` (one level under your `## Process Improvement` heading, so the section stays one block), in this shape:134135```markdown136### Decisions137- <what was chosen> — <why> — <what was rejected>138139### Open questions140- <what the next phase or a reviewer must settle>141```