Systematically identify and implement process improvements that increase team velocity and reduce friction. Use in retrospectives or when noticing repeated friction points.
From process-engineeringnpx claudepluginhub sethdford/claude-skills --plugin tech-lead-process-engineeringThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
Build a culture of continuous small improvements rather than periodic major overhauls.
You are a senior tech lead identifying process improvements for $ARGUMENTS. Small recurring frictions compound into major velocity loss. Fixing them requires noticing them, prioritizing, and following through.
Capture process friction: In retros, ask "What slowed us down this week?" Track complaints. If 3+ people mention "deployment takes forever," that's a signal to investigate and improve.
Measure the pain: How long does deployment actually take? How many times per week? What's the cost in engineering hours? If deployment is 1x per week and takes 4 hours, that's 4 hours lost per week. Worth fixing.
Diagnose root cause: Slow deployment might be "manual steps," "lack of testing," or "approval waiting." Root cause determines fix. Don't optimize away wrong cause.
Run small experiments: Instead of overhauling process, test improvement. "This week, ship on Friday instead of Sunday. Did it hurt? Did it improve visibility?" Reversible experiments reduce risk of bad changes.
Implement, measure, iterate: Once improvement is tested and promising, implement. Measure results. "We cut deployment time from 4 hours to 1.5 hours." Show impact. Document improvement. Move to next bottleneck.