[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MD8Q8B0CDYXASB086J8JCM":3,"skill-same:01M6MD8Q8B0CDYXASB086J8JCM":87},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M6MD8Q8B0CDYXASB086J8JCM","dmaic",null,"DMAIC (Define-Measure-Analyze-Improve-Control) — Six Sigma structured problem-solving for chronic, data-driven quality improvement projects. Use when a problem recurs despite corrective actions, when a process needs systematic capability improvement, or when a customer requests a Six Sigma approach. Use 8D for reactive single-incident problems; use DMAIC for recurring systemic issues requiring statistical analysis. Covers IATF 16949 §10.1 and ISO 9001 §10.3.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fproblem-solving\u002Fdmaic\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"iso","2026","automotive","when","capability","reactive","data-driven","quality improvement","problem","systematic","medical","customer","incident","problem-solving","analyze","projects","improve","analysis","sigma","data","actions","issues","2026-11-10 10:12:30",false,"---\nname: dmaic\ndescription: >-\n  DMAIC (Define-Measure-Analyze-Improve-Control) — Six Sigma structured problem-solving for\n  chronic, data-driven quality improvement projects. Use when a problem recurs despite corrective\n  actions, when a process needs systematic capability improvement, or when a customer requests\n  a Six Sigma approach. Use 8D for reactive single-incident problems; use DMAIC for recurring\n  systemic issues requiring statistical analysis. Covers IATF 16949 §10.1 and ISO 9001 §10.3.\nlicense: MIT\nmetadata:\n  author: RBraga01\n  version: \"1.1\"\n  iso-9001: \"10.3\"\n  iatf-16949: \"10.1\"\n  domain: quality-engineering\n  subdomain: problem-solving\n  industries: automotive,electronics,aerospace,medical,general\n  status: approved\n  created: \"2026-06-06\"\n  last_updated: \"2026-06-06\"\n  updated_by: migmcc\n  reviewed_by: RBraga01\n  standard_edition: \"Six Sigma DMAIC \u002F ISO 9001:2015 §10.3 \u002F IATF 16949:2016 §10.1\"\n---\n\n# DMAIC (Six Sigma Problem Solving)\n\n## When to use\n\nUse DMAIC when:\n- A problem has recurred multiple times despite previous corrective actions\n- The process needs measurable, data-driven capability improvement (Cpk improvement target)\n- The root cause is unknown and requires statistical analysis to identify\n- A customer requires a Six Sigma approach or asks for a DMAIC report\n- The improvement opportunity involves eliminating chronic waste (rework, scrap, test failures)\n\n**Use 8D instead when:** The problem is a single customer complaint, an escape to the field, or requires immediate containment. 8D is reactive and fast. DMAIC is proactive and thorough — it takes weeks to months.\n\n**Use PDCA instead when:** The improvement is incremental and the root cause is already known or assumed.\n\n## Prerequisites\n\n- A defined problem with measurable impact (reject rate, Cpk, scrap cost, defect count)\n- Baseline data available or collectable\n- Process owner and cross-functional team assigned\n- Management support and a time budget (minimum 4–12 weeks depending on project scope)\n\n## Workflow\n\n### Phase 1 — DEFINE\n\n**Objective:** Define the problem, the scope, the team, and the goal in measurable terms.\n\n**Key tools and deliverables:**\n\n**Project Charter** — The DMAIC starts and ends here. Contains:\n- Problem statement: what is happening, where, since when, how much (measured impact)\n- Goal statement: specific, measurable target (e.g., \"Reduce connector reject rate from 3.2% to 0.5% by Q3\")\n- Scope: what is IN and OUT of scope (use Is\u002FIs-Not to define boundaries)\n- Business case: financial or customer impact ($, PPM, warranty cost)\n- Team: Champion, Black Belt\u002FGreen Belt, process owner, operators, engineering\n\n**SIPOC diagram:**\n- Suppliers → Inputs → Process → Outputs → Customers\n- Defines the process at a high level before diving into detail\n- Identifies all inputs that could affect the output (Y)\n\n**Voice of the Customer (VOC) → CTQ:**\n- What does the customer care about? (VOC)\n- Translate to a measurable Critical to Quality (CTQ) characteristic\n- The CTQ becomes the Y (output) the project will improve\n\n**Gate criteria to exit Define:**\n- Problem is specific and measurable\n- Goal is agreed with the Champion\n- Scope is bounded\n- Team is assigned and available\n\n---\n\n### Phase 2 — MEASURE\n\n**Objective:** Establish the current baseline and validate the measurement system.\n\n**Key tools and deliverables:**\n\n**Process map (detailed):**\n- Map every step of the process as it IS (not as it should be)\n- Identify where defects are created or detected\n- Mark each step: Value-Added (VA), Non-Value-Added (NVA), or Required Non-Value-Added\n\n**Data collection plan:**\n- What will be measured? (the Y and key process inputs Xs)\n- How will it be measured? (gauge, method)\n- How many samples? (for capability: minimum 100 pieces)\n- Who will collect data? When? Where?\n\n**MSA (Gauge R&R):**\n- Validate the measurement system for the CTQ before collecting data\n- %GRR \u003C 30% required; \u003C10% preferred\n- If measurement system is inadequate: fix it before proceeding\n\n**Baseline capability:**\n- Calculate current Cpk\u002FPpk for the CTQ\n- Establish current defect rate (PPM or %)\n- This baseline is the MEASURE gate deliverable — do not proceed without it\n\n**Gate criteria to exit Measure:**\n- Baseline Cpk\u002FPPM established with statistical confidence\n- MSA complete and measurement system adequate\n- Data collection plan executed with sufficient data\n\n---\n\n### Phase 3 — ANALYZE\n\n**Objective:** Identify and confirm the root cause(s) of the problem using data.\n\n**Key tools and deliverables:**\n\n**Fishbone \u002F Cause & Effect diagram:**\n- Brainstorm potential causes using 6M (Man, Machine, Method, Material, Measurement, Mother Nature)\n- All potential causes are hypotheses at this stage — none are confirmed\n\n**Is\u002FIs-Not analysis:**\n- Scope the problem precisely — what IS affected vs. what IS NOT\n- Narrows the hypothesis list before investing in analysis\n\n**Multi-Vari study:**\n- Understand whether variation is: positional (within-part), cyclical (part-to-part), or temporal (time-based)\n- Identifies the dominant family of variation — directs the investigation\n\n**Hypothesis testing:**\nConfirm or reject hypotheses statistically. Selection guide:\n\n| Situation | Tool |\n|-----------|------|\n| Compare means of 2 groups (continuous Y, e.g., Shift A vs. B) | t-test (paired if same parts measured twice) |\n| Compare means of 3+ groups (e.g., 3 machines, 4 operators) | One-way ANOVA |\n| Categorical Y (pass\u002Ffail) vs. categorical X (supplier, shift) | Chi-square test |\n| Continuous Y vs. continuous X (does temperature predict dimension?) | Pearson correlation; then regression to quantify |\n| Multiple Xs affecting one Y | Multiple regression; confirm no multicollinearity |\n\nUse p \u003C 0.05 as the significance threshold unless a different risk level is warranted. Always check the test's assumptions (normality for t-test\u002FANOVA; independence for chi-square).\n\n**Root cause confirmation:**\n- A root cause is NOT confirmed until data proves it\n- Reject \"human error\" as a root cause — it is a symptom; ask why the error was possible\n- Confirmed root causes: demonstrate that when the Xs change, the Y changes predictably\n\n**Gate criteria to exit Analyze:**\n- Root cause(s) confirmed with data (not assumed)\n- Cause-and-effect quantified (Y = f(X) relationship established)\n- Team agrees on which Xs to improve\n\n---\n\n### Phase 4 — IMPROVE\n\n**Objective:** Develop, test, and implement solutions that address the confirmed root causes.\n\n**Key tools and deliverables:**\n\n**Solution generation:**\n- Brainstorm solutions for each confirmed root cause\n- Evaluate solutions: impact vs. effort vs. risk\n- Do NOT select solutions based on opinion — test them\n\n**Pilot \u002F Design of Experiment (DOE):**\n- Test the proposed solution on a small scale before full implementation\n- DOE: systematically vary multiple factors to find the optimal process settings\n- Simple experiments: OFAT (One Factor At A Time) for straightforward improvements\n\n**Solution validation:**\n- Run a production pilot with the solution in place\n- Collect data: does the Y improve as predicted?\n- Calculate new Cpk\u002FPPM — compare to baseline and goal\n\n**Implementation plan:**\n- Who does what, by when, to implement the solution at full scale\n- Change management: update Process Flow, PFMEA, Control Plan, Work Instructions, training\n\n**Gate criteria to exit Improve:**\n- Solution tested and statistically validated (not just \"it seems better\")\n- Cpk\u002FPPM improvement demonstrated in pilot data\n- Implementation plan complete and approved\n\n---\n\n### Phase 5 — CONTROL\n\n**Objective:** Sustain the gains — prevent the process from reverting to the old state.\n\n**Key tools and deliverables:**\n\n**Updated Control Plan:**\n- Add new controls for the Xs identified in Analyze\n- Define monitoring frequency and reaction plan for out-of-control conditions\n\n**SPC \u002F Statistical monitoring:**\n- Install control charts on the critical Xs and the Y\n- Set control limits from the improved process data\n- Define who monitors and how often\n\n**Updated PFMEA:**\n- New failure modes identified during the project must be added\n- Controls added in Improve must be reflected in the PFMEA current controls column\n\n**Updated Work Instructions:**\n- Document the new process steps, settings, or behaviours required\n- Train operators and verify understanding\n\n**Mistake-proofing (Poka-yoke):**\n- For any root cause that was behavioural or procedural: add error-proofing to prevent recurrence\n- Error-proofing is the highest-reliability control — prefer it over inspection or SPC alone\n\n**Project handover:**\n- Transfer ownership from the project team to the process owner\n- Establish a 3–6 month monitoring period with defined Cpk targets; specify the minimum Cpk that constitutes \"sustained improvement\" (e.g., Cpk ≥ 1.33 for a minimum of 3 consecutive months of production data — not 3 months of calendar time)\n- Close the project only when the monitoring criterion is met with actual production data — not lab data or pilot data\n\n**Final project report:**\n- Before and after: Cpk, PPM, financial savings\n- Lessons learned for future projects\n\n**Gate criteria to close the project:**\n- Cpk\u002FPPM goal achieved and sustained for minimum 3 months post-implementation\n- All documents updated (PFMEA, CP, WIs)\n- Process ownership transferred to process owner\n- Financial benefits validated by Finance (if business case required it)\n\n---\n\n### DMAIC vs. 8D — quick reference\n\n| Dimension | 8D | DMAIC |\n|-----------|-----|-------|\n| Trigger | Customer complaint, single escape | Recurring problem, capability gap |\n| Timeline | Days to weeks | Weeks to months |\n| Root cause method | 5-Why, Fishbone | Hypothesis testing, statistical analysis |\n| Output | Corrective action to prevent recurrence | Optimised process with sustained capability |\n| Standards | ISO 9001 §10.2, IATF 16949 §10.2.3 | ISO 9001 §10.3, IATF 16949 §10.1 |\n\n## Validation criteria\n\nA DMAIC project is complete when:\n- Baseline and improved Cpk\u002FPPM both quantified with data\n- Root causes confirmed statistically (not assumed)\n- Solution validated in a pilot before full implementation\n- PFMEA, Control Plan, and Work Instructions updated\n- Improved Cpk sustained for minimum 3 months post-implementation\n- Financial or quality benefit measured and reported\n\n## Common mistakes\n\n- Jumping to Improve before confirming root cause (the most common DMAIC failure)\n- Not performing MSA before collecting baseline data — baseline may be measurement noise\n- Selecting the solution in Define before data analysis — biases the entire project\n- Closing the project at Implementation without monitoring for sustainability\n- Not updating PFMEA and Control Plan — process reverts within months\n- Using DMAIC for a single-event problem that needs 8D containment first\n\n## Output Format\n\nAt the start of each use, ask the user:\n\n> \"How would you like to receive the output?\n> **A** — Structured Markdown (formatted tables and sections, ready to copy)\n> **B** — Plain tables (simplified structure for Excel or Word)\n> **C** — Narrative report (flowing text for a formal document or email)\n>\n> Default: A.\"\n\nAdapt all output sections to the chosen format. If the platform or session context already defines a format preference, skip this question.\n\n## Changelog\n\n| Version | Date | Author | Change |\n|---------|------|--------|--------|\n| 1.0 | 2026-06-06 | @RBraga01 | Initial release |\n| 1.1 | 2026-06-06 | @migmcc | Added hypothesis test selection guide in Phase 3; added monitoring period closure criteria in Phase 5 (Cpk sustained on production data, not pilot) |\n","# DMAIC (Six Sigma Problem Solving)\n\n## When to use\n\nUse DMAIC when:\n- A problem has recurred multiple times despite previous corrective actions\n- The process needs measurable, data-driven capability improvement (Cpk improvement target)\n- The root cause is unknown and requires statistical analysis to identify\n- A customer requires a Six Sigma approach or asks for a DMAIC report\n- The improvement opportunity involves eliminating chronic waste (rework, scrap, test failures)\n\n**Use 8D instead when:** The problem is a single customer complaint, an escape to the field, or requires immediate containment. 8D is reactive and fast. DMAIC is proactive and thorough — it takes weeks to months.\n\n**Use PDCA instead when:** The improvement is incremental and the root cause is already known or assumed.\n\n## Prerequisites\n\n- A defined problem with measurable impact (reject rate, Cpk, scrap cost, defect count)\n- Baseline data available or collectable\n- Process owner and cross-functional team assigned\n- Management support and a time budget (minimum 4–12 weeks depending on project scope)\n\n## Workflow\n\n### Phase 1 — DEFINE\n\n**Objective:** Define the problem, the scope, the team, and the goal in measurable terms.\n\n**Key tools and deliverables:**\n\n**Project Charter** — The DMAIC starts and ends here. Contains:\n- Problem statement: what is happening, where, since when, how much (measured impact)\n- Goal statement: specific, measurable target (e.g., \"Reduce connector reject rate from 3.2% to 0.5% by Q3\")\n- Scope: what is IN and OUT of scope (use Is\u002FIs-Not to define boundaries)\n- Business case: financial or customer impact ($, PPM, warranty cost)\n- Team: Champion, Black Belt\u002FGreen Belt, process owner, operators, engineering\n\n**SIPOC diagram:**\n- Suppliers → Inputs → Process → Outputs → Customers\n- Defines the process at a high level before diving into detail\n- Identifies all inputs that could affect the output (Y)\n\n**Voice of the Customer (VOC) → CTQ:**\n- What does the customer care about? (VOC)\n- Translate to a measurable Critical to Quality (CTQ) characteristic\n- The CTQ becomes the Y (output) the project will improve\n\n**Gate criteria to exit Define:**\n- Problem is specific and measurable\n- Goal is agreed with the Champion\n- Scope is bounded\n- Team is assigned and available\n\n---\n\n### Phase 2 — MEASURE\n\n**Objective:** Establish the current baseline and validate the measurement system.\n\n**Key tools and deliverables:**\n\n**Process map (detailed):**\n- Map every step of the process as it IS (not as it should be)\n- Identify where defects are created or detected\n- Mark each step: Value-Added (VA), Non-Value-Added (NVA), or Required Non-Value-Added\n\n**Data collection plan:**\n- What will be measured? (the Y and key process inputs Xs)\n- How will it be measured? (gauge, method)\n- How many samples? (for capability: minimum 100 pieces)\n- Who will collect data? When? Where?\n\n**MSA (Gauge R&R):**\n- Validate the measurement system for the CTQ before collecting data\n- %GRR \u003C 30% required; \u003C10% preferred\n- If measurement system is inadequate: fix it before proceeding\n\n**Baseline capability:**\n- Calculate current Cpk\u002FPpk for the CTQ\n- Establish current defect rate (PPM or %)\n- This baseline is the MEASURE gate deliverable — do not proceed without it\n\n**Gate criteria to exit Measure:**\n- Baseline Cpk\u002FPPM established with statistical confidence\n- MSA complete and measurement system adequate\n- Data collection plan executed with sufficient data\n\n---\n\n### Phase 3 — ANALYZE\n\n**Objective:** Identify and confirm the root cause(s) of the problem using data.\n\n**Key tools and deliverables:**\n\n**Fishbone \u002F Cause & Effect diagram:**\n- Brainstorm potential causes using 6M (Man, Machine, Method, Material, Measurement, Mother Nature)\n- All potential causes are hypotheses at this stage — none are confirmed\n\n**Is\u002FIs-Not analysis:**\n- Scope the problem precisely — what IS affected vs. what IS NOT\n- Narrows the hypothesis list before investing in analysis\n\n**Multi-Vari study:**\n- Understand whether variation is: positional (within-part), cyclical (part-to-part), or temporal (time-based)\n- Identifies the dominant family of variation — directs the investigation\n\n**Hypothesis testing:**\nConfirm or reject hypotheses statistically. Selection guide:\n\n| Situation | Tool |\n|-----------|------|\n| Compare means of 2 groups (continuous Y, e.g., Shift A vs. B) | t-test (paired if same parts measured twice) |\n| Compare means of 3+ groups (e.g., 3 machines, 4 operators) | One-way ANOVA |\n| Categorical Y (pass\u002Ffail) vs. categorical X (supplier, shift) | Chi-square test |\n| Continuous Y vs. continuous X (does temperature predict dimension?) | Pearson correlation; then regression to quantify |\n| Multiple Xs affecting one Y | Multiple regression; confirm no multicollinearity |\n\nUse p \u003C 0.05 as the significance threshold unless a different risk level is warranted. Always check the test's assumptions (normality for t-test\u002FANOVA; independence for chi-square).\n\n**Root cause confirmation:**\n- A root cause is NOT confirmed until data proves it\n- Reject \"human error\" as a root cause — it is a symptom; ask why the error was possible\n- Confirmed root causes: demonstrate that when the Xs change, the Y changes predictably\n\n**Gate criteria to exit Analyze:**\n- Root cause(s) confirmed with data (not assumed)\n- Cause-and-effect quantified (Y = f(X) relationship established)\n- Team agrees on which Xs to improve\n\n---\n\n### Phase 4 — IMPROVE\n\n**Objective:** Develop, test, and implement solutions that address the confirmed root causes.\n\n**Key tools and deliverables:**\n\n**Solution generation:**\n- Brainstorm solutions for each confirmed root cause\n- Evaluate solutions: impact vs. effort vs. risk\n- Do NOT select solutions based on opinion — test them\n\n**Pilot \u002F Design of Experiment (DOE):**\n- Test the proposed solution on a small scale before full implementation\n- DOE: systematically vary multiple factors to find the optimal process settings\n- Simple experiments: OFAT (One Factor At A Time) for straightforward improvements\n\n**Solution validation:**\n- Run a production pilot with the solution in place\n- Collect data: does the Y improve as predicted?\n- Calculate new Cpk\u002FPPM — compare to baseline and goal\n\n**Implementation plan:**\n- Who does what, by when, to implement the solution at full scale\n- Change management: update Process Flow, PFMEA, Control Plan, Work Instructions, training\n\n**Gate criteria to exit Improve:**\n- Solution tested and statistically validated (not just \"it seems better\")\n- Cpk\u002FPPM improvement demonstrated in pilot data\n- Implementation plan complete and approved\n\n---\n\n### Phase 5 — CONTROL\n\n**Objective:** Sustain the gains — prevent the process from reverting to the old state.\n\n**Key tools and deliverables:**\n\n**Updated Control Plan:**\n- Add new controls for the Xs identified in Analyze\n- Define monitoring frequency and reaction plan for out-of-control conditions\n\n**SPC \u002F Statistical monitoring:**\n- Install control charts on the critical Xs and the Y\n- Set control limits from the improved process data\n- Define who monitors and how often\n\n**Updated PFMEA:**\n- New failure modes identified during the project must be added\n- Controls added in Improve must be reflected in the PFMEA current controls column\n\n**Updated Work Instructions:**\n- Document the new process steps, settings, or behaviours required\n- Train operators and verify understanding\n\n**Mistake-proofing (Poka-yoke):**\n- For any root cause that was behavioural or procedural: add error-proofing to prevent recurrence\n- Error-proofing is the highest-reliability control — prefer it over inspection or SPC alone\n\n**Project handover:**\n- Transfer ownership from the project team to the process owner\n- Establish a 3–6 month monitoring period with defined Cpk targets; specify the minimum Cpk that constitutes \"sustained improvement\" (e.g., Cpk ≥ 1.33 for a minimum of 3 consecutive months of production data — not 3 months of calendar time)\n- Close the project only when the monitoring criterion is met with actual production data — not lab data or pilot data\n\n**Final project report:**\n- Before and after: Cpk, PPM, financial savings\n- Lessons learned for future projects\n\n**Gate criteria to close the project:**\n- Cpk\u002FPPM goal achieved and sustained for minimum 3 months post-implementation\n- All documents updated (PFMEA, CP, WIs)\n- Process ownership transferred to process owner\n- Financial benefits validated by Finance (if business case required it)\n\n---\n\n### DMAIC vs. 8D — quick reference\n\n| Dimension | 8D | DMAIC |\n|-----------|-----|-------|\n| Trigger | Customer complaint, single escape | Recurring problem, capability gap |\n| Timeline | Days to weeks | Weeks to months |\n| Root cause method | 5-Why, Fishbone | Hypothesis testing, statistical analysis |\n| Output | Corrective action to prevent recurrence | Optimised process with sustained capability |\n| Standards | ISO 9001 §10.2, IATF 16949 §10.2.3 | ISO 9001 §10.3, IATF 16949 §10.1 |\n\n## Validation criteria\n\nA DMAIC project is complete when:\n- Baseline and improved Cpk\u002FPPM both quantified with data\n- Root causes confirmed statistically (not assumed)\n- Solution validated in a pilot before full implementation\n- PFMEA, Control Plan, and Work Instructions updated\n- Improved Cpk sustained for minimum 3 months post-implementation\n- Financial or quality benefit measured and reported\n\n## Common mistakes\n\n- Jumping to Improve before confirming root cause (the most common DMAIC failure)\n- Not performing MSA before collecting baseline data — baseline may be measurement noise\n- Selecting the solution in Define before data analysis — biases the entire project\n- Closing the project at Implementation without monitoring for sustainability\n- Not updating PFMEA and Control Plan — process reverts within months\n- Using DMAIC for a single-event problem that needs 8D containment first\n\n## Output Format\n\nAt the start of each use, ask the user:\n\n> \"How would you like to receive the output?\n> **A** — Structured Markdown (formatted tables and sections, ready to copy)\n> **B** — Plain tables (simplified structure for Excel or Word)\n> **C** — Narrative report (flowing text for a formal document or email)\n>\n> Default: A.\"\n\nAdapt all output sections to the chosen format. If the platform or session context already defines a format preference, skip this question.\n\n## Changelog\n\n| Version | Date | Author | Change |\n|---------|------|--------|--------|\n| 1.0 | 2026-06-06 | @RBraga01 | Initial release |\n| 1.1 | 2026-06-06 | @migmcc | Added hypothesis test selection guide in Phase 3; added monitoring period closure criteria in Phase 5 (Cpk sustained on production data, not pilot) |\n",{"name":5,"license":15,"metadata":46,"description":7},{"author":47,"domain":48,"status":49,"created":50,"version":51,"iso-9001":52,"subdomain":32,"iatf-16949":53,"industries":54,"updated_by":55,"reviewed_by":47,"last_updated":50,"standard_edition":56},"RBraga01","quality-engineering","approved","2026-06-06","1.1","10.3","10.1","automotive,electronics,aerospace,medical,general","migmcc","Six Sigma DMAIC \u002F ISO 9001:2015 §10.3 \u002F IATF 16949:2016 §10.1","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fproblem-solving\u002Fdmaic",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dmaic",{"tool":73,"command":74},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dmaic",{"tool":76,"command":77},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dmaic","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fproblem-solving\u002Fdmaic\u002FSKILL.md",true,[81],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fstatistical-tools.md","REFERENCE","参考文档",21000,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fproblem-solving\u002Fdmaic\u002Freferences\u002Fstatistical-tools.md",[88,97,105,113,121,129],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":96},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":96},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":96},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":96},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":96},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":96},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]