process-engineering

Advises on methodology selection, flow metrics, and team design for software delivery processes.

1|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill process-engineering-theviziusgroup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: process-engineering
Source: https://github.com/TheViziusGroup/vibe-engineering-skills/tree/main/plugins/engineering-process/skills/process-engineering
Command: npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill process-engineering-theviziusgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing and running the right delivery process is hard: teams cargo-cult frameworks, misread Agile success statistics, scale prematurely, and adopt AI tooling without fixing underlying flow problems. This Skill provides an evidence-grounded reference for selecting methodologies, measuring flow, scaling deliberately, and designing teams. ## Core Features & Use Cases - Methodology Selection: Uses the Cynefin framework to match work type (Clear, Complicated, Complex, Chaotic) to predictive, Agile, Kanban, or hybrid approaches, with honest assessments of Scrum, SAFe, LeSS, Nexus, Shape Up, PMBOK, and PRINCE2. - Flow Metrics & Forecasting: Covers DORA metrics, Little's Law, cycle time, throughput, WIP limits, Monte Carlo forecasting, and Flow Framework metrics for data-driven delivery management. - Team & Org Design: Applies Team Topologies, psychological safety research, OKRs, Continuous Discovery, and staged adoption roadmaps, including guidance on AI's measured impact on delivery performance. - Use Case: A VP of Engineering asks whether to adopt SAFe for 12 teams. The Skill walks through Cynefin classification, checks whether teams have stable flow and healthy DORA baselines first, and recommends starting with Nexus or LeSS before committing to full SAFe. ## Quick Start Ask the assistant to recommend a delivery methodology for your team's context, for example by describing your team size, work type, and predictability requirements.

Frequently Asked Questions about process-engineering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between Scrum, Kanban, and SAFe for my team?

Use the Cynefin framework to classify your work first. Complex product work fits Scrum or Kanban, operational flow fits Kanban, and scaling frameworks like SAFe should only be considered after at least one team demonstrates stable flow and healthy DORA metrics.

What are DORA metrics and how do I use them?

DORA metrics measure delivery performance through deployment frequency, lead time, change failure rate, and recovery time. They are survey-based correlations, not causal benchmarks, so use them to track your own baseline trends rather than comparing across organizations.

Is the claim that Agile projects succeed 3x more than Waterfall true?

No, that Standish CHAOS statistic is methodologically discredited. Eveleens and Verhoef's 2010 peer-reviewed critique showed the definitions produce meaningless figures, and Standish stopped publishing the report. Defensible evidence supports iterative delivery and fast feedback correlating with better outcomes.

When should an organization adopt a scaling framework like SAFe?

Only after individual teams show stable flow and healthy delivery metrics. Prefer the lightest framework that resolves actual dependencies, such as Nexus or LeSS, before Full SAFe, which is widely criticized for bureaucracy and diluting team-level agility.

How does AI adoption affect software delivery performance?

DORA 2025 research frames AI as a mirror and multiplier: it amplifies the system it enters. Early 2024 data showed AI adoption correlated with reduced throughput and stability due to larger batch sizes, so enforce WIP limits and testing discipline before scaling AI tooling.

What are the limitations of Little's Law for forecasting?

Little's Law only describes past flow and cannot itself predict the future. Its assumptions of stable flow and comparable item sizes must hold, and enforced WIP limits are a prerequisite since without them there is no flow and no predictability.