value-stream-map

Map concept-to-production delivery pipelines across eight SDLC phases to measure flow efficiency.

1|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill value-stream-map
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: value-stream-map
Source: https://github.com/shafibabar/SDLC-Artifact-Factory/tree/main/skills/value-stream-map
Command: npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill value-stream-map

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the hidden inefficiencies in the software development lifecycle by distinguishing between active process time and idle wait time, allowing teams to identify and eliminate bottlenecks in their delivery pipeline.

Core Features & Use Cases

  • Flow Efficiency Analysis: Calculates the ratio of active work to total lead time to reveal the true speed of the factory.
  • Waste Identification: Pinpoints specific friction points like approval-gate delays, rework loops, and handoff friction.
  • Use Case: Use this during a retrospective to analyze why a specific user story took six days to ship, identifying that 46 hours were spent waiting for external validation, allowing you to adjust your planning for future sprints.

Quick Start

Use the value-stream-map skill to generate a performance report for the current story by providing the entry and exit timestamps for each of the eight SDLC phases.

Frequently Asked Questions about value-stream-map

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

FAQPage Schema
How do I measure flow efficiency to identify delivery bottlenecks in the SDLC?

Map process and wait times across eight SDLC phases to calculate the ratio of active work to total lead time, revealing hidden idle delays and pinpointing specific delivery bottlenecks for continuous improvement.

What is the best way to analyze why a specific user story took so long to ship?

The best way to analyze delayed user story shipping is using a value stream map during a retrospective to trace process and wait times per phase, isolating exact friction points like external validation delays or handoff friction.

Can I calculate DORA metrics using phase timestamps from a retrospective?

Yes, you can calculate DORA-aligned performance metrics by providing the precise entry and exit timestamps for each of the eight SDLC phases to generate a detailed performance report for continuous improvement.

Do I need precise tracking data to perform value stream mapping for continuous improvement?

Yes, precise tracking of process and wait times per phase is required to accurately calculate lead time, measure flow efficiency, and distinguish active process time from idle wait time across the delivery pipeline.

What types of process waste can I identify when mapping the concept-to-production delivery pipeline?

Mapping the concept-to-production delivery pipeline identifies process waste such as approval-gate delays, rework loops, and handoff friction by distinguishing between active process time and idle wait time across SDLC phases.