[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MD9R398MDMADFAV1MZJDZE":3,"skill-same:01M6MD9R398MDMADFAV1MZJDZE":101},{"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":28,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":71,"commitSha":72,"skillDirectory":73,"forksCount":74,"repositoryHtmlUrl":75,"repositoryHomepageUrl":76,"ownerHtmlUrl":77,"ownerBlogUrl":78,"ownerDescription":79,"updatedAt":80,"install":81,"resources":94},"01M6MD9R398MDMADFAV1MZJDZE","dfmea-design",null,"Build a design risk analysis, DFMEA worksheet, or interface analysis using the AIAG-VDA FMEA Handbook 2019. Covers design intent, interface failures, boundary diagram, and design robustness before manufacturing. Use during new product development, design changes, or when a field failure reveals a design weakness. Required for IATF 16949 §8.3 scope.","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\u002Frisk-analysis\u002Fdfmea-design\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"dfmea design","design","manufacturing","new","2026","automotive","when","product development","handbook","design intent","robustness","for","interface","electronics","scope","medical","intent","general","use","analysis","risk-analysis","risk","product","development","diagram","2026-11-10 10:12:30",false,"---\nname: dfmea-design\ndescription: >-\n  Build a design risk analysis, DFMEA worksheet, or interface analysis using the AIAG-VDA\n  FMEA Handbook 2019. Covers design intent, interface failures, boundary diagram, and design\n  robustness before manufacturing. Use during new product development, design changes, or\n  when a field failure reveals a design weakness. Required for IATF 16949 §8.3 scope.\nlicense: MIT\nmetadata:\n  author: RBraga01\n  version: \"1.1\"\n  iso-9001: \"8.3\"\n  iatf-16949: \"8.3.3.3\"\n  aiag-reference: \"AIAG-VDA FMEA Handbook 2019, DFMEA chapters\"\n  domain: quality-engineering\n  subdomain: risk-analysis\n  industries: automotive,electronics,aerospace,medical,general\n  status: approved\n  created: \"2026-06-01\"\n  last_updated: \"2026-06-06\"\n  updated_by: RBraga01\n  reviewed_by: RBraga01\n  standard_edition: \"AIAG-VDA FMEA Handbook 2019\"\n---\n\n# Design FMEA (DFMEA) — AIAG-VDA 2019\n\n## Goal\n\nIdentify and mitigate design risks by analysing functions, interfaces, and failure modes — so that design weaknesses are resolved before release to manufacturing, and the results feed directly into the DVP, PFMEA, and Control Plan.\n\n## Required Execution Checklist\n\n- [ ] DFMEA scope defined: boundary diagram complete, inside\u002Foutside boundary identified\n- [ ] Product hierarchy mapped: system → subsystem → component → interface (Step 2)\n- [ ] All interfaces identified — internal (component-to-component), external (environment), and user\u002Fassembly\n- [ ] All functions defined with Verb + Noun + Measurable Standard (Step 3)\n- [ ] Each function has a measurable verification method confirmed in the DVP\n- [ ] Failure chain complete: Effect → Mode → Cause for each function (Step 4)\n- [ ] All Failure Causes validated using engineering analysis (FEA, calculation) or test evidence — not assumptions\n- [ ] S\u002FO\u002FD ratings justified using analysis, test data, or design history\n- [ ] All H-AP items have a defined action, named owner, and target date\n- [ ] DFMEA → DVP, PFMEA, and drawing linkage verified before release to manufacturing\n\n---\n\n## When to use\n\n- New product development (integrate into APQP Phase 2 — Product Design and Development)\n- Design change or engineering change request (ECR)\n- Field failure investigation revealing a design root cause\n- Periodic design review\n- Before handoff to manufacturing (DFMEA drives the PFMEA)\n\n**Key difference from PFMEA:** DFMEA analyses the design intent and design robustness. PFMEA analyses the manufacturing process. DFMEA comes first — its failure effects and severity ratings inform the PFMEA.\n\n## Prerequisites\n\n- Product requirements \u002F specification (engineering drawing, customer spec)\n- System block diagram or product breakdown structure\n- Interface matrix (if system-level analysis)\n- Team: design engineer, systems engineer, quality engineer, reliability (if available)\n\n## The 7-Step AIAG-VDA 2019 Approach for DFMEA\n\n---\n\n### Step 1 — Planning and Preparation\n\nDefine scope:\n- **Analysis object:** component, subsystem, or system\n- **Customer:** who is the next-level assembly? Who is the end user?\n- **Boundary diagram:** what is inside and outside the DFMEA scope\n- **Interface matrix:** what interacts with this component (mechanical, electrical, thermal, chemical)?\n\n---\n\n### Step 2 — Structure Analysis (Design Hierarchy)\n\nMap the product hierarchy:\n\n```\nSystem (e.g., Steering Column)\n└── Subsystem (e.g., Tilt Mechanism)\n    └── Component (e.g., Pivot Pin)\n        └── Interface (e.g., Pin-to-Bracket contact)\n```\n\n**Interface matrix:**\nFor each component, identify:\n- Interfaces to other components (internal)\n- Interfaces to the environment (external): heat, vibration, corrosion, electromagnetic\n- Interfaces to the user or assembly process\n\nInterfaces are where most design failures occur. Each interface must be analysed as a potential failure location in its own right — not just the components that share it. In practice, at least 50% of DFMEA effort should focus on interfaces and interactions; component-only analysis misses the most common field failure modes.\n\n---\n\n### Step 3 — Function Analysis\n\nFor each element in the structure, define its design function:\n\n**Format:** Verb + Noun + Measurable Standard\n\nExamples:\n- Component function: \"Transmit torque of 50 Nm ± 5 Nm without permanent deformation\"\n- Interface function: \"Maintain sealing at pressure 2.5 bar across -40°C to +120°C\"\n- System function: \"Provide steering angle feedback with latency \u003C 50ms\"\n\nIdentify **Special Characteristics** from the drawing — these get S = 9 or 10 in Step 5.\n\n**Testability rule:** Every function must be measurable and verifiable — a test or analysis method must exist in the DVP. A function with no verification method cannot receive a credible D rating in Step 5.\n\n---\n\n### Step 4 — Failure Analysis\n\nThe failure chain for DFMEA: **Failure Effect → Failure Mode → Failure Cause**\n\n**Failure Effect (FE):**\n- End-user effect: safety hazard, loss of primary function, reduced performance\n- Vehicle\u002Fsystem effect: damage to adjacent components, secondary failures\n- Manufacturing effect (if component is not to spec): inability to assemble, rework\n\n**Failure Mode (FM):**\nHow does this component fail to perform its design function?\n- Fracture, wear, corrosion, deformation, signal loss, leakage, dimensional drift, electrical short\u002Fopen\n\n**Failure Cause (FC):**\nWhat design parameter or design decision causes the failure mode?\n- Insufficient material strength (wrong grade, wrong heat treat)\n- Inadequate geometry (stress concentration, insufficient wall thickness)\n- Thermal expansion mismatch\n- Corrosion protection insufficient for environment\n- Tolerance stack-up causing interference\n- Interface design not accounting for assembly variation\n\n**Failure Cause validation:** Failure Causes must be validated using engineering analysis (FEA, structural calculation, thermal simulation) or test evidence. Unverified assumptions — \"probably,\" \"likely,\" \"may be\" — are not acceptable as final Failure Causes. Use CAE (FEA, simulation), test data, and field return data to support both the failure modes identified and their causes. For post-field-failure DFMEA updates, the FC must match the validated root cause from the 8D or field investigation.\n\n---\n\n### Step 5 — Risk Analysis\n\nUse the same S\u002FO\u002FD ratings and AP table as PFMEA (see [action-priority-ap](..\u002Faction-priority-ap\u002F) and [pfmea-process](..\u002Fpfmea-process\u002F) for the tables).\n\n**Key DFMEA-specific notes:**\n\n**Occurrence (O) in DFMEA** considers:\n- Design maturity (new design = higher O)\n- Similar design history (similar designs with this failure = higher O)\n- Prevention controls: design reviews, CAE \u002F FEA, DVP testing\n\n**Detection (D) in DFMEA** considers:\n- Design verification tests (DVP)\n- Engineering analysis (FEA, simulation)\n- Design reviews with checklists\n- Prototype testing\n\nD = 10 means no design verification for this failure mode. This is common for new features — it drives the DVP.\n\n**Ratings justification:** All S\u002FO\u002FD ratings must be justified using analysis, test data, or design history. A rating without documented justification will not withstand OEM audit. Where design history exists from similar components, reference it explicitly. Where data is absent, mark O and D as preliminary and flag the DVP entry that will confirm them.\n\n---\n\n### Step 6 — Optimization\n\nFor H-AP items in DFMEA, actions typically fall into:\n\n1. **Design change:** change geometry, material, tolerance, or coating\n2. **Add design verification:** add DVP test entry to confirm the design meets the requirement\n3. **Add prevention:** design guideline, DFM\u002FDFA rule, standard reference\n4. **Improve detection:** add inspection requirement to DVP or design review checklist\n\n**DFMEA → DVP linkage:**\nEvery detection control (D rating improvement) must have a corresponding entry in the Design Verification Plan (DVP). If you improve D because \"we will test it,\" the test must exist in the DVP.\n\n**Action tracking:** All actions must be tracked to closure with objective evidence — test results, simulation output, or updated analysis. Actions marked \"complete\" without verification evidence are not acceptable. Open H-AP items past their target date must be escalated to the design review owner or programme manager, with a revised date and documented reason for delay.\n\n---\n\n### Step 7 — Results Documentation\n\nDFMEA outputs that feed other APQP documents:\n- **Special Characteristics** identified in DFMEA → transferred to Control Plan and PFMEA\n- **Detection controls** → DVP entries\n- **Interface failure modes** → PFMEA structure analysis inputs\n- **Material \u002F geometry requirements confirmed** → released drawing\n\n## DFMEA → PFMEA handoff\n\nThe DFMEA and PFMEA are linked:\n\n| DFMEA | → | PFMEA |\n|-------|---|-------|\n| Design Failure Effects (end-user impact) | → | Severity ratings in PFMEA |\n| Special Characteristics | → | SC flagging in PFMEA process steps |\n| Interface failure modes | → | PFMEA failure modes for assembly steps |\n| Design intent (function) | → | Process step function requirements |\n\n## Mandatory DFMEA review events (APQP \u002F IATF 16949 §8.3)\n\n| Trigger | Required action |\n|---------|----------------|\n| New product development | Start DFMEA at APQP Phase 2 — before design freeze. DFMEA initiated after freeze has no corrective value. |\n| Engineering change request (ECR) | Review and update the DFMEA for all functions, failure modes, and interfaces affected by the change — before the change is released. |\n| Design milestone \u002F design review | Present DFMEA status: open H-AP items, actions, and revised ratings. DFMEA must be current at each gate. |\n| Field failure with confirmed design root cause | Update FC, ratings, and actions to match validated root cause from 8D\u002Ffield investigation. Update DVP to include the failure mode. |\n\nA DFMEA that is not updated through the programme lifecycle is a design quality assurance gap — not a living document.\n\n## Common mistakes\n\n- **Starting DFMEA after design is frozen** — DFMEA has no value if no changes can be made\n- **Only analysing the component, not the interfaces** — most design failures are interface failures\n- **Improving D without adding DVP tests** — detection credit without actual testing\n- **DFMEA and PFMEA teams working in silos** — they must share severity ratings and special characteristics\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## Reference files\n\n- [Interface matrix construction guide](references\u002Finterface-matrix.md)\n\n## Changelog\n\n| Version | Date | Author | Change |\n|---------|------|--------|--------|\n| 1.0 | 2026-06-01 | @RBraga01 | Initial release |\n| 1.1 | 2026-06-03 | @RBraga01 | Added interface matrix integration and DFMEA-to-PFMEA handoff workflow |\n","# Design FMEA (DFMEA) — AIAG-VDA 2019\n\n## Goal\n\nIdentify and mitigate design risks by analysing functions, interfaces, and failure modes — so that design weaknesses are resolved before release to manufacturing, and the results feed directly into the DVP, PFMEA, and Control Plan.\n\n## Required Execution Checklist\n\n- [ ] DFMEA scope defined: boundary diagram complete, inside\u002Foutside boundary identified\n- [ ] Product hierarchy mapped: system → subsystem → component → interface (Step 2)\n- [ ] All interfaces identified — internal (component-to-component), external (environment), and user\u002Fassembly\n- [ ] All functions defined with Verb + Noun + Measurable Standard (Step 3)\n- [ ] Each function has a measurable verification method confirmed in the DVP\n- [ ] Failure chain complete: Effect → Mode → Cause for each function (Step 4)\n- [ ] All Failure Causes validated using engineering analysis (FEA, calculation) or test evidence — not assumptions\n- [ ] S\u002FO\u002FD ratings justified using analysis, test data, or design history\n- [ ] All H-AP items have a defined action, named owner, and target date\n- [ ] DFMEA → DVP, PFMEA, and drawing linkage verified before release to manufacturing\n\n---\n\n## When to use\n\n- New product development (integrate into APQP Phase 2 — Product Design and Development)\n- Design change or engineering change request (ECR)\n- Field failure investigation revealing a design root cause\n- Periodic design review\n- Before handoff to manufacturing (DFMEA drives the PFMEA)\n\n**Key difference from PFMEA:** DFMEA analyses the design intent and design robustness. PFMEA analyses the manufacturing process. DFMEA comes first — its failure effects and severity ratings inform the PFMEA.\n\n## Prerequisites\n\n- Product requirements \u002F specification (engineering drawing, customer spec)\n- System block diagram or product breakdown structure\n- Interface matrix (if system-level analysis)\n- Team: design engineer, systems engineer, quality engineer, reliability (if available)\n\n## The 7-Step AIAG-VDA 2019 Approach for DFMEA\n\n---\n\n### Step 1 — Planning and Preparation\n\nDefine scope:\n- **Analysis object:** component, subsystem, or system\n- **Customer:** who is the next-level assembly? Who is the end user?\n- **Boundary diagram:** what is inside and outside the DFMEA scope\n- **Interface matrix:** what interacts with this component (mechanical, electrical, thermal, chemical)?\n\n---\n\n### Step 2 — Structure Analysis (Design Hierarchy)\n\nMap the product hierarchy:\n\n```\nSystem (e.g., Steering Column)\n└── Subsystem (e.g., Tilt Mechanism)\n    └── Component (e.g., Pivot Pin)\n        └── Interface (e.g., Pin-to-Bracket contact)\n```\n\n**Interface matrix:**\nFor each component, identify:\n- Interfaces to other components (internal)\n- Interfaces to the environment (external): heat, vibration, corrosion, electromagnetic\n- Interfaces to the user or assembly process\n\nInterfaces are where most design failures occur. Each interface must be analysed as a potential failure location in its own right — not just the components that share it. In practice, at least 50% of DFMEA effort should focus on interfaces and interactions; component-only analysis misses the most common field failure modes.\n\n---\n\n### Step 3 — Function Analysis\n\nFor each element in the structure, define its design function:\n\n**Format:** Verb + Noun + Measurable Standard\n\nExamples:\n- Component function: \"Transmit torque of 50 Nm ± 5 Nm without permanent deformation\"\n- Interface function: \"Maintain sealing at pressure 2.5 bar across -40°C to +120°C\"\n- System function: \"Provide steering angle feedback with latency \u003C 50ms\"\n\nIdentify **Special Characteristics** from the drawing — these get S = 9 or 10 in Step 5.\n\n**Testability rule:** Every function must be measurable and verifiable — a test or analysis method must exist in the DVP. A function with no verification method cannot receive a credible D rating in Step 5.\n\n---\n\n### Step 4 — Failure Analysis\n\nThe failure chain for DFMEA: **Failure Effect → Failure Mode → Failure Cause**\n\n**Failure Effect (FE):**\n- End-user effect: safety hazard, loss of primary function, reduced performance\n- Vehicle\u002Fsystem effect: damage to adjacent components, secondary failures\n- Manufacturing effect (if component is not to spec): inability to assemble, rework\n\n**Failure Mode (FM):**\nHow does this component fail to perform its design function?\n- Fracture, wear, corrosion, deformation, signal loss, leakage, dimensional drift, electrical short\u002Fopen\n\n**Failure Cause (FC):**\nWhat design parameter or design decision causes the failure mode?\n- Insufficient material strength (wrong grade, wrong heat treat)\n- Inadequate geometry (stress concentration, insufficient wall thickness)\n- Thermal expansion mismatch\n- Corrosion protection insufficient for environment\n- Tolerance stack-up causing interference\n- Interface design not accounting for assembly variation\n\n**Failure Cause validation:** Failure Causes must be validated using engineering analysis (FEA, structural calculation, thermal simulation) or test evidence. Unverified assumptions — \"probably,\" \"likely,\" \"may be\" — are not acceptable as final Failure Causes. Use CAE (FEA, simulation), test data, and field return data to support both the failure modes identified and their causes. For post-field-failure DFMEA updates, the FC must match the validated root cause from the 8D or field investigation.\n\n---\n\n### Step 5 — Risk Analysis\n\nUse the same S\u002FO\u002FD ratings and AP table as PFMEA (see [action-priority-ap](..\u002Faction-priority-ap\u002F) and [pfmea-process](..\u002Fpfmea-process\u002F) for the tables).\n\n**Key DFMEA-specific notes:**\n\n**Occurrence (O) in DFMEA** considers:\n- Design maturity (new design = higher O)\n- Similar design history (similar designs with this failure = higher O)\n- Prevention controls: design reviews, CAE \u002F FEA, DVP testing\n\n**Detection (D) in DFMEA** considers:\n- Design verification tests (DVP)\n- Engineering analysis (FEA, simulation)\n- Design reviews with checklists\n- Prototype testing\n\nD = 10 means no design verification for this failure mode. This is common for new features — it drives the DVP.\n\n**Ratings justification:** All S\u002FO\u002FD ratings must be justified using analysis, test data, or design history. A rating without documented justification will not withstand OEM audit. Where design history exists from similar components, reference it explicitly. Where data is absent, mark O and D as preliminary and flag the DVP entry that will confirm them.\n\n---\n\n### Step 6 — Optimization\n\nFor H-AP items in DFMEA, actions typically fall into:\n\n1. **Design change:** change geometry, material, tolerance, or coating\n2. **Add design verification:** add DVP test entry to confirm the design meets the requirement\n3. **Add prevention:** design guideline, DFM\u002FDFA rule, standard reference\n4. **Improve detection:** add inspection requirement to DVP or design review checklist\n\n**DFMEA → DVP linkage:**\nEvery detection control (D rating improvement) must have a corresponding entry in the Design Verification Plan (DVP). If you improve D because \"we will test it,\" the test must exist in the DVP.\n\n**Action tracking:** All actions must be tracked to closure with objective evidence — test results, simulation output, or updated analysis. Actions marked \"complete\" without verification evidence are not acceptable. Open H-AP items past their target date must be escalated to the design review owner or programme manager, with a revised date and documented reason for delay.\n\n---\n\n### Step 7 — Results Documentation\n\nDFMEA outputs that feed other APQP documents:\n- **Special Characteristics** identified in DFMEA → transferred to Control Plan and PFMEA\n- **Detection controls** → DVP entries\n- **Interface failure modes** → PFMEA structure analysis inputs\n- **Material \u002F geometry requirements confirmed** → released drawing\n\n## DFMEA → PFMEA handoff\n\nThe DFMEA and PFMEA are linked:\n\n| DFMEA | → | PFMEA |\n|-------|---|-------|\n| Design Failure Effects (end-user impact) | → | Severity ratings in PFMEA |\n| Special Characteristics | → | SC flagging in PFMEA process steps |\n| Interface failure modes | → | PFMEA failure modes for assembly steps |\n| Design intent (function) | → | Process step function requirements |\n\n## Mandatory DFMEA review events (APQP \u002F IATF 16949 §8.3)\n\n| Trigger | Required action |\n|---------|----------------|\n| New product development | Start DFMEA at APQP Phase 2 — before design freeze. DFMEA initiated after freeze has no corrective value. |\n| Engineering change request (ECR) | Review and update the DFMEA for all functions, failure modes, and interfaces affected by the change — before the change is released. |\n| Design milestone \u002F design review | Present DFMEA status: open H-AP items, actions, and revised ratings. DFMEA must be current at each gate. |\n| Field failure with confirmed design root cause | Update FC, ratings, and actions to match validated root cause from 8D\u002Ffield investigation. Update DVP to include the failure mode. |\n\nA DFMEA that is not updated through the programme lifecycle is a design quality assurance gap — not a living document.\n\n## Common mistakes\n\n- **Starting DFMEA after design is frozen** — DFMEA has no value if no changes can be made\n- **Only analysing the component, not the interfaces** — most design failures are interface failures\n- **Improving D without adding DVP tests** — detection credit without actual testing\n- **DFMEA and PFMEA teams working in silos** — they must share severity ratings and special characteristics\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## Reference files\n\n- [Interface matrix construction guide](references\u002Finterface-matrix.md)\n\n## Changelog\n\n| Version | Date | Author | Change |\n|---------|------|--------|--------|\n| 1.0 | 2026-06-01 | @RBraga01 | Initial release |\n| 1.1 | 2026-06-03 | @RBraga01 | Added interface matrix integration and DFMEA-to-PFMEA handoff workflow |\n",{"name":5,"license":15,"metadata":59,"description":7},{"author":60,"domain":61,"status":62,"created":63,"version":64,"iso-9001":65,"subdomain":49,"iatf-16949":66,"industries":67,"updated_by":60,"reviewed_by":60,"last_updated":68,"aiag-reference":69,"standard_edition":70},"RBraga01","quality-engineering","approved","2026-06-01","1.1","8.3","8.3.3.3","automotive,electronics,aerospace,medical,general","2026-06-06","AIAG-VDA FMEA Handbook 2019, DFMEA chapters","AIAG-VDA FMEA Handbook 2019","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Frisk-analysis\u002Fdfmea-design",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":82,"prompt":92,"zipAvailable":93},[83,86,89],{"tool":84,"command":85},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dfmea-design",{"tool":87,"command":88},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dfmea-design",{"tool":90,"command":91},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dfmea-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Frisk-analysis\u002Fdfmea-design\u002FSKILL.md",true,[95],{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Finterface-matrix.md","REFERENCE","参考文档",10620,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Frisk-analysis\u002Fdfmea-design\u002Freferences\u002Finterface-matrix.md",[102,111,119,127,135,143],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":110},"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":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":110},"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":110},"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":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":110},"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":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":110},"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":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":147,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":110},"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",[],[]]