Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From workflow-optimizer
Maps the current development workflow, measures lead/cycle times, identifies bottlenecks and friction points, and prioritizes improvements by impact-to-effort ratio.
How this command is triggered — by the user, by Claude, or both
Slash command
/workflow-optimizer:analyze-workflowThe summary Claude sees in its command listing — used to decide when to auto-load this command
Analyze the development workflow to identify bottlenecks, friction, and improvement opportunities. ## Steps 1. Map the current development workflow: 2. Measure workflow metrics: 3. Identify bottlenecks: 4. Categorize friction points: 5. Calculate the cost of each bottleneck: 6. Prioritize improvements by impact-to-effort ratio. ## Format ## Rules - Measure before proposing changes; intuition is unreliable. - Focus on the biggest bottleneck first (Theory of Constraints). - Include developer experience in the analysis, not just metrics.
Analyze the development workflow to identify bottlenecks, friction, and improvement opportunities.
Workflow Analysis: <team or project>
Current Metrics:
Lead Time: <X days>
Cycle Time: <X hours>
6plugins reuse this command
First indexed Mar 30, 2026
npx claudepluginhub samuelj90/awesome-claude-code-toolkit --plugin workflow-optimizer/analyze-workflowMaps the current development workflow, measures lead/cycle times, identifies bottlenecks and friction points, and prioritizes improvements by impact-to-effort ratio.
/audit-dxIdentify developer experience friction points and plan improvements.
/improve-processIdentify bottlenecks and plan data-driven process improvements.
/analyze-projectAnalyzes a project across multiple dimensions (velocity, quality, risk, dependencies, team, architecture) and produces actionable insights, metrics, and recommendations. Supports specific focus areas via arguments.
/tooling-reviewAnalyzes the project's developer tooling and workflows, identifies pain points, and generates a prioritized improvement plan saved as a markdown report. Also supports scoping to specific paths, uncommitted changes, recent commits, or a pull request.
/upgrade-roadmapGenerates prioritized sequenced upgrade roadmap with dependency chains, effort estimates adjusted for team size, cumulative impact curves, and directed graph visualization.