[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MD7RVQKKJ6YV4FT8BY4PBP":3,"skill-same:01M6MD7RVQKKJ6YV4FT8BY4PBP":90},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6MD7RVQKKJ6YV4FT8BY4PBP","apqp",null,"Advanced Product Quality Planning (APQP) — plan and track a new product launch through all 5 phases, identify deliverables per phase, run gate reviews, and ensure quality outputs are complete before Start of Production (SOP). Use when launching a new part, managing an APQP project, or auditing APQP completeness. Covers AIAG APQP 2nd edition and IATF 16949 §8.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\u002Fplanning\u002Fapqp\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,41,42,43],"completeness","new","2026","automotive","when","outputs","phase","track","reviews","deliverables","advanced","electronics","run","complete","medical","project","general","ensure quality","use","sop","quality","plan","start","product","planning","2026-11-10 10:12:30",false,"---\nname: apqp\ndescription: >-\n  Advanced Product Quality Planning (APQP) — plan and track a new product launch through all 5 phases,\n  identify deliverables per phase, run gate reviews, and ensure quality outputs are complete before\n  Start of Production (SOP). Use when launching a new part, managing an APQP project, or auditing\n  APQP completeness. Covers AIAG APQP 2nd edition and IATF 16949 §8.3.\nlicense: MIT\nmetadata:\n  author: RBraga01\n  version: \"1.1\"\n  iso-9001: \"8.3\"\n  iatf-16949: \"8.3\"\n  aiag-reference: \"AIAG APQP 2nd Edition\"\n  domain: quality-engineering\n  subdomain: planning\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: \"AIAG APQP 2nd Edition (2008) \u002F IATF 16949:2016 §8.3\"\n---\n\n# Advanced Product Quality Planning (APQP)\n\n## When to use\n\nUse this skill when:\n- A new product or part is being launched and a structured quality plan is needed\n- Managing an APQP project and tracking deliverables across phases\n- Conducting an APQP gate review to assess launch readiness\n- A customer requests an APQP status report or phase completion confirmation\n- Auditing whether a supplier's APQP process is adequate\n\n## Prerequisites\n\n- Customer requirements, specifications, and drawings (or RFQ package)\n- Programme timing (SOP date, PPAP submission date, prototype gates)\n- Nominated APQP team (cross-functional: engineering, quality, purchasing, manufacturing, logistics)\n- Customer APQP template if OEM-specific format required\n\n## Workflow\n\n### Overview — The 5 APQP Phases\n\n```\nPhase 1          Phase 2          Phase 3          Phase 4          Phase 5\nPlan & Define → Product Design → Process Design → Product & Process → Feedback &\n                & Development   & Development      Validation         Corrective Action\n     ↓               ↓               ↓                ↓                  ↓\n  Program         Prototype       Pre-launch         PPAP              SOP +\n  approval         build           build           submission          Production\n```\n\nAll phases run with concurrent engineering — phases overlap and teams work in parallel.\n\n---\n\n### Phase 1 — Plan and Define Program\n\n**Objective:** Understand customer requirements and define what the product must do.\n\n**Key deliverables:**\n\n| Deliverable | Description |\n|-------------|-------------|\n| Voice of the Customer (VOC) | Customer wants, needs, expectations — translated to measurable requirements |\n| Design Goals | Product performance targets derived from VOC |\n| Reliability and Quality Goals | Target failure rate, warranty targets, Cpk targets |\n| Preliminary Bill of Materials | Draft BOM from design intent |\n| Preliminary Process Flow | High-level process sequence |\n| Preliminary Special Characteristics | Initial list of critical\u002Fsignificant characteristics |\n| Product Assurance Plan | Quality plan for the programme |\n| Management Support | Signed-off programme charter with resources and timing |\n\n**Gate 1 pass criteria:**\n- Customer requirements documented and agreed\n- Feasibility confirmed (technical and commercial)\n- Team chartered and timing plan approved\n- Special characteristics list preliminary but complete\n\n---\n\n### Phase 2 — Product Design and Development\n\n**Objective:** Translate customer requirements into a product design with verified characteristics.\n\n**Key deliverables:**\n\n| Deliverable | Description |\n|-------------|-------------|\n| DFMEA | Design FMEA — all failure modes analysed, H-AP items addressed |\n| Design Verification Plan (DVP) | Test plan linked to DFMEA failure modes |\n| Drawing and Specification Release | Fully released engineering drawings and 3D data |\n| Material Specifications | Raw material specs, supplier approval plan |\n| Drawing and Specification Changes | Change management process in place |\n| New Equipment and Tooling | List of new equipment\u002Ftooling required |\n| Special Product and Process Characteristics | Updated with design detail |\n| Gauge Plan | MSA requirement list — which characteristics need MSA studies |\n| Prototype Control Plan | Control plan for prototype builds |\n| Prototype Build | Prototype parts manufactured and tested |\n| Engineering Drawings | Released and approved |\n\n**Gate 2 pass criteria:**\n- DFMEA complete with all H-AP actions closed\n- DVP complete and test execution started\n- Prototype build results acceptable\n- All special characteristics identified and confirmed\n- No outstanding major design concerns\n\n---\n\n### Phase 3 — Process Design and Development\n\n**Objective:** Design and verify the manufacturing process.\n\n**Key deliverables:**\n\n| Deliverable | Description |\n|-------------|-------------|\n| Packaging Standards | Packaging design, labelling, MMOG\u002FLE if required |\n| Product\u002FProcess Quality System Review | Internal quality system audit against customer requirements |\n| Process Flow Chart | Detailed process flow for all operations |\n| Floor Plan Layout | Manufacturing floor layout approved |\n| Characteristics Matrix | Matrix linking process steps to product characteristics |\n| PFMEA | Process FMEA — all failure modes, AP ratings, H-AP actions complete |\n| Pre-Launch Control Plan | Control plan for pre-launch production |\n| Process Instructions | Work instructions for all operations |\n| MSA Plan | Gauge R&R plan for all measurement systems |\n| Preliminary Process Capability Study Plan | Plan for capability studies on special characteristics |\n| Packaging Specifications | Final packaging specs including OEM labelling |\n\n**Gate 3 pass criteria:**\n- PFMEA complete, H-AP actions closed or formally accepted\n- Pre-launch Control Plan approved\n- Process instructions complete for all operations\n- Tooling and equipment installed and qualified\n- No unresolved open issues blocking pre-launch build\n\n---\n\n### Phase 4 — Product and Process Validation\n\n**Objective:** Validate the production process and prepare for PPAP submission.\n\n**Key deliverables:**\n\n| Deliverable | Description |\n|-------------|-------------|\n| Production Trial Run | Significant Production Run (minimum run to PPAP requirements) |\n| MSA Studies | Gauge R&R completed for all special characteristics |\n| Preliminary Process Capability | Cpk study on special characteristics (target ≥ 1.67) |\n| Production Part Approval (PPAP) | All 18 PPAP elements complete and submitted |\n| Production Validation Testing | Final validation tests on production parts |\n| Packaging Evaluation | Production packaging validated |\n| Production Control Plan | Final production control plan approved |\n| Quality Planning Sign-Off | Customer approval of PPAP and APQP completion |\n| Management Support Sign-Off | Internal management approval for SOP |\n\n**Gate 4 pass criteria (= PPAP approval):**\n- Significant production run completed (minimum 300 consecutive parts per AIAG PPAP 4th ed §4.0, unless the customer specifies otherwise in writing)\n- Dimensional results 100% conforming\n- Cpk ≥ 1.67 on all special characteristics (or customer-approved deviation)\n- %GRR \u003C 30% for all MSA studies\n- PPAP submitted and customer approval received\n- No open concerns from validation testing\n\n---\n\n### Phase 5 — Feedback, Assessment and Corrective Action\n\n**Objective:** Continuous improvement after SOP — close the loop on any issues found in production.\n\n**Key activities:**\n\n| Activity | Description |\n|----------|-------------|\n| Reduced variation | Monitor process capability, reduce common-cause variation |\n| Improved customer satisfaction | Track warranty, field returns, and customer scorecards |\n| Improved delivery and service | Monitor OTD (on-time delivery) and logistics performance |\n| Lessons learned | Document lessons learned for future programmes |\n| Control Plan updates | Update based on production data and any quality escapes |\n| PFMEA updates | Update based on field failures and warranty data |\n\n**Phase 5 is ongoing.** There is no defined end gate — it runs for the life of the programme.\n\n---\n\n### APQP timing — rule of thumb\n\n| Milestone | Typical timing before SOP |\n|-----------|--------------------------|\n| Programme approval \u002F Phase 1 complete | 18–24 months |\n| Design release \u002F Phase 2 complete | 12–15 months |\n| Process design complete \u002F Phase 3 complete | 8–10 months |\n| PPAP submission | 4–6 months |\n| PPAP approval (customer) | 3–4 months |\n| Pre-production builds | 2–3 months |\n| SOP | 0 |\n\nAutomotive OEM programmes vary — always confirm with the customer's APQP coordinator.\n\n## Validation criteria\n\nAt each gate review, verify:\n- All deliverables for the phase are complete (not \"in progress\")\n- No open H-AP items in DFMEA or PFMEA without approved actions\n- No outstanding design or process concerns without a documented resolution plan\n- Team sign-off obtained from all functions (quality, engineering, manufacturing, purchasing)\n- Customer confirmation received before advancing to next phase\n\nGate reviews are STOP gates — do not advance until all criteria are met.\n\n## Common mistakes\n\n- Starting Phase 2 before customer requirements are fully understood and documented (Phase 1 incomplete)\n- PFMEA created after process is already running — it must drive process design, not document it\n- Production trial run shorter than 300 consecutive parts without written customer authorisation — the PPAP samples must come from this run; a shorter run requires an explicit customer waiver\n- Capability studies run on off-tool or pre-production parts — must be from production tooling\n- Prototype Control Plan used for PPAP submission — production control plan must be separate\n- MSA studies done after PPAP submission — must be complete before PSW is signed\n- Phase 5 never started — APQP is treated as \"done\" at SOP rather than as a continuous loop\n- Lessons learned not captured — same problems recur on next programme\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 300-part production trial run minimum to Gate 4 criteria and Common Mistakes |\n","# Advanced Product Quality Planning (APQP)\n\n## When to use\n\nUse this skill when:\n- A new product or part is being launched and a structured quality plan is needed\n- Managing an APQP project and tracking deliverables across phases\n- Conducting an APQP gate review to assess launch readiness\n- A customer requests an APQP status report or phase completion confirmation\n- Auditing whether a supplier's APQP process is adequate\n\n## Prerequisites\n\n- Customer requirements, specifications, and drawings (or RFQ package)\n- Programme timing (SOP date, PPAP submission date, prototype gates)\n- Nominated APQP team (cross-functional: engineering, quality, purchasing, manufacturing, logistics)\n- Customer APQP template if OEM-specific format required\n\n## Workflow\n\n### Overview — The 5 APQP Phases\n\n```\nPhase 1          Phase 2          Phase 3          Phase 4          Phase 5\nPlan & Define → Product Design → Process Design → Product & Process → Feedback &\n                & Development   & Development      Validation         Corrective Action\n     ↓               ↓               ↓                ↓                  ↓\n  Program         Prototype       Pre-launch         PPAP              SOP +\n  approval         build           build           submission          Production\n```\n\nAll phases run with concurrent engineering — phases overlap and teams work in parallel.\n\n---\n\n### Phase 1 — Plan and Define Program\n\n**Objective:** Understand customer requirements and define what the product must do.\n\n**Key deliverables:**\n\n| Deliverable | Description |\n|-------------|-------------|\n| Voice of the Customer (VOC) | Customer wants, needs, expectations — translated to measurable requirements |\n| Design Goals | Product performance targets derived from VOC |\n| Reliability and Quality Goals | Target failure rate, warranty targets, Cpk targets |\n| Preliminary Bill of Materials | Draft BOM from design intent |\n| Preliminary Process Flow | High-level process sequence |\n| Preliminary Special Characteristics | Initial list of critical\u002Fsignificant characteristics |\n| Product Assurance Plan | Quality plan for the programme |\n| Management Support | Signed-off programme charter with resources and timing |\n\n**Gate 1 pass criteria:**\n- Customer requirements documented and agreed\n- Feasibility confirmed (technical and commercial)\n- Team chartered and timing plan approved\n- Special characteristics list preliminary but complete\n\n---\n\n### Phase 2 — Product Design and Development\n\n**Objective:** Translate customer requirements into a product design with verified characteristics.\n\n**Key deliverables:**\n\n| Deliverable | Description |\n|-------------|-------------|\n| DFMEA | Design FMEA — all failure modes analysed, H-AP items addressed |\n| Design Verification Plan (DVP) | Test plan linked to DFMEA failure modes |\n| Drawing and Specification Release | Fully released engineering drawings and 3D data |\n| Material Specifications | Raw material specs, supplier approval plan |\n| Drawing and Specification Changes | Change management process in place |\n| New Equipment and Tooling | List of new equipment\u002Ftooling required |\n| Special Product and Process Characteristics | Updated with design detail |\n| Gauge Plan | MSA requirement list — which characteristics need MSA studies |\n| Prototype Control Plan | Control plan for prototype builds |\n| Prototype Build | Prototype parts manufactured and tested |\n| Engineering Drawings | Released and approved |\n\n**Gate 2 pass criteria:**\n- DFMEA complete with all H-AP actions closed\n- DVP complete and test execution started\n- Prototype build results acceptable\n- All special characteristics identified and confirmed\n- No outstanding major design concerns\n\n---\n\n### Phase 3 — Process Design and Development\n\n**Objective:** Design and verify the manufacturing process.\n\n**Key deliverables:**\n\n| Deliverable | Description |\n|-------------|-------------|\n| Packaging Standards | Packaging design, labelling, MMOG\u002FLE if required |\n| Product\u002FProcess Quality System Review | Internal quality system audit against customer requirements |\n| Process Flow Chart | Detailed process flow for all operations |\n| Floor Plan Layout | Manufacturing floor layout approved |\n| Characteristics Matrix | Matrix linking process steps to product characteristics |\n| PFMEA | Process FMEA — all failure modes, AP ratings, H-AP actions complete |\n| Pre-Launch Control Plan | Control plan for pre-launch production |\n| Process Instructions | Work instructions for all operations |\n| MSA Plan | Gauge R&R plan for all measurement systems |\n| Preliminary Process Capability Study Plan | Plan for capability studies on special characteristics |\n| Packaging Specifications | Final packaging specs including OEM labelling |\n\n**Gate 3 pass criteria:**\n- PFMEA complete, H-AP actions closed or formally accepted\n- Pre-launch Control Plan approved\n- Process instructions complete for all operations\n- Tooling and equipment installed and qualified\n- No unresolved open issues blocking pre-launch build\n\n---\n\n### Phase 4 — Product and Process Validation\n\n**Objective:** Validate the production process and prepare for PPAP submission.\n\n**Key deliverables:**\n\n| Deliverable | Description |\n|-------------|-------------|\n| Production Trial Run | Significant Production Run (minimum run to PPAP requirements) |\n| MSA Studies | Gauge R&R completed for all special characteristics |\n| Preliminary Process Capability | Cpk study on special characteristics (target ≥ 1.67) |\n| Production Part Approval (PPAP) | All 18 PPAP elements complete and submitted |\n| Production Validation Testing | Final validation tests on production parts |\n| Packaging Evaluation | Production packaging validated |\n| Production Control Plan | Final production control plan approved |\n| Quality Planning Sign-Off | Customer approval of PPAP and APQP completion |\n| Management Support Sign-Off | Internal management approval for SOP |\n\n**Gate 4 pass criteria (= PPAP approval):**\n- Significant production run completed (minimum 300 consecutive parts per AIAG PPAP 4th ed §4.0, unless the customer specifies otherwise in writing)\n- Dimensional results 100% conforming\n- Cpk ≥ 1.67 on all special characteristics (or customer-approved deviation)\n- %GRR \u003C 30% for all MSA studies\n- PPAP submitted and customer approval received\n- No open concerns from validation testing\n\n---\n\n### Phase 5 — Feedback, Assessment and Corrective Action\n\n**Objective:** Continuous improvement after SOP — close the loop on any issues found in production.\n\n**Key activities:**\n\n| Activity | Description |\n|----------|-------------|\n| Reduced variation | Monitor process capability, reduce common-cause variation |\n| Improved customer satisfaction | Track warranty, field returns, and customer scorecards |\n| Improved delivery and service | Monitor OTD (on-time delivery) and logistics performance |\n| Lessons learned | Document lessons learned for future programmes |\n| Control Plan updates | Update based on production data and any quality escapes |\n| PFMEA updates | Update based on field failures and warranty data |\n\n**Phase 5 is ongoing.** There is no defined end gate — it runs for the life of the programme.\n\n---\n\n### APQP timing — rule of thumb\n\n| Milestone | Typical timing before SOP |\n|-----------|--------------------------|\n| Programme approval \u002F Phase 1 complete | 18–24 months |\n| Design release \u002F Phase 2 complete | 12–15 months |\n| Process design complete \u002F Phase 3 complete | 8–10 months |\n| PPAP submission | 4–6 months |\n| PPAP approval (customer) | 3–4 months |\n| Pre-production builds | 2–3 months |\n| SOP | 0 |\n\nAutomotive OEM programmes vary — always confirm with the customer's APQP coordinator.\n\n## Validation criteria\n\nAt each gate review, verify:\n- All deliverables for the phase are complete (not \"in progress\")\n- No open H-AP items in DFMEA or PFMEA without approved actions\n- No outstanding design or process concerns without a documented resolution plan\n- Team sign-off obtained from all functions (quality, engineering, manufacturing, purchasing)\n- Customer confirmation received before advancing to next phase\n\nGate reviews are STOP gates — do not advance until all criteria are met.\n\n## Common mistakes\n\n- Starting Phase 2 before customer requirements are fully understood and documented (Phase 1 incomplete)\n- PFMEA created after process is already running — it must drive process design, not document it\n- Production trial run shorter than 300 consecutive parts without written customer authorisation — the PPAP samples must come from this run; a shorter run requires an explicit customer waiver\n- Capability studies run on off-tool or pre-production parts — must be from production tooling\n- Prototype Control Plan used for PPAP submission — production control plan must be separate\n- MSA studies done after PPAP submission — must be complete before PSW is signed\n- Phase 5 never started — APQP is treated as \"done\" at SOP rather than as a continuous loop\n- Lessons learned not captured — same problems recur on next programme\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 300-part production trial run minimum to Gate 4 criteria and Common Mistakes |\n",{"name":5,"license":15,"metadata":49,"description":7},{"author":50,"domain":51,"status":52,"created":53,"version":54,"iso-9001":55,"subdomain":43,"iatf-16949":55,"industries":56,"updated_by":57,"reviewed_by":50,"last_updated":53,"aiag-reference":58,"standard_edition":59},"RBraga01","quality-engineering","approved","2026-06-06","1.1","8.3","automotive,electronics,aerospace,medical,general","migmcc","AIAG APQP 2nd Edition","AIAG APQP 2nd Edition (2008) \u002F IATF 16949:2016 §8.3","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fplanning\u002Fapqp",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":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill apqp",{"tool":76,"command":77},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill apqp",{"tool":79,"command":80},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill apqp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fplanning\u002Fapqp\u002FSKILL.md",true,[84],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fphase-deliverables.md","REFERENCE","参考文档",15223,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fplanning\u002Fapqp\u002Freferences\u002Fphase-deliverables.md",[91,100,108,116,124,132],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":99},"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":99},"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":99},"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":99},"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":99},"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":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":99},"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",[],[]]