dmaic-define

Guides the Define phase of DMAIC projects by producing a Project Charter with VOC, CTQs, SIPOC, and RACI.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/NestorMonroy/thyrox --skill dmaic-define-nestormonroy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dmaic-define
Source: https://github.com/NestorMonroy/thyrox/tree/main/.claude/skills/dmaic-define
Command: npx skills add https://github.com/NestorMonroy/thyrox --skill dmaic-define-nestormonroy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Starting a Six Sigma improvement project without a clear problem definition, measurable customer requirements, or sponsor authorization leads to scope creep and failed projects. This Skill structures the DMAIC Define phase so the team produces an approved Project Charter before any measurement begins. ## Core Features & Use Cases - VOC to CTQ conversion: Collects Voice of Customer data using six documented techniques (interviews, surveys, complaint analysis, Gemba, focus groups, support data) and converts it into measurable Critical-to-Quality requirements. - Project Charter generation: Produces a formal charter with Problem Statement, Goal Statement, Business Case, SIPOC map, scope boundaries, RACI matrix, and DMAIC timeline using a ready-made template. - Tollgate discipline: Enforces sponsor approval as a hard gate before advancing to the Measure phase, with red-flag detection and anti-rationalization guidance. - Use Case: A logistics team sees 18% of orders delivered late. Use this Skill to interview customers, define CTQs like on-time delivery percentage, map the fulfillment SIPOC, and get a signed charter authorizing the improvement project. ## Quick Start Start the DMAIC Define phase for my late-delivery problem and help me build the Project Charter with VOC, CTQs, and a SIPOC map.

Frequently Asked Questions about dmaic-define

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

FAQPage Schema
How do I write a Six Sigma problem statement?▼

A good problem statement describes an observable symptom with a quantified magnitude, a time period, and a business impact, without mentioning causes or solutions. For example: 18% of orders delivered late in Q1 2026, generating $45K in monthly credits.

How do I convert VOC into CTQs?▼

Convert Voice of Customer statements by identifying the underlying need, then defining a measurable metric with a specification. For example, 'orders arrive late' becomes the need for on-time delivery, measured as percentage of orders delivered by the promised date with a target of 95% or higher.

What is the correct order to build a SIPOC diagram?▼

Build a SIPOC starting with the Process (5-7 high-level steps), then Outputs, Customers, Inputs, and finally Suppliers. Starting with Suppliers leads to listing irrelevant inputs; the process definition anchors everything else.

When should I not use DMAIC for a process problem?▼

Skip DMAIC for simple improvements solvable in a PDCA cycle, when the root cause is already confirmed (go directly to Improve), or when no sponsor exists. DMAIC requires formal authorization and resources; without a sponsor the project lacks traction.

Why do CTQs fail without real VOC data?▼

CTQs defined without direct customer input are team assumptions, not validated requirements. The skill requires at least one direct elicitation technique such as interviews or Gemba observation, and recommends combining qualitative and quantitative sources to reduce bias.