standard-interpretation

Decompose medical device standard clauses into executable test cases exported as a 12-column Excel workbook.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/HalseyYang/Skills-HY --skill standard-interpretation-halseyyang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: standard-interpretation
Source: https://github.com/HalseyYang/Skills-HY/tree/main/standard-interpretation
Command: npx skills add https://github.com/HalseyYang/Skills-HY --skill standard-interpretation-halseyyang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openpyxl, pymupdf, pdfplumber, and includes scripts (resource) and references (resource) components.

What problem does it solve? Manually converting medical device standards (GB 9706, YY 9706 series) into registration-submission test cases is slow and error-prone: clauses get skipped, limits get invented from memory, and coverage gaps surface only during audits. This Skill decomposes every clause of a standard into minimal executable test units with verbatim-sourced limits and generates a fixed-format Excel test case library. ## Core Features & Use Cases - Clause-by-clause decomposition: Splits standard text into minimal executable test units using four case forms (chapter-level fallback, clause body, document review, normative-reference expansion) to prevent systematic omissions. - Traceable limits and criteria: Test environments and acceptance criteria are quoted verbatim from clause text or normative references, with source annotations and manual-review flags instead of invented parameters. - Fixed 12-column Excel output: Generates a frozen-header workbook with dropdown validation, dual product/module code classification (8 + 11 codes), clause-index existence and continuity checks, and blocking validation against real coverage gaps. - Use Case: Upload YY 9706.262-2021 or GB 9706.224-2021 and receive a complete, clause-ordered Excel test case library ready for registration submission or QA review. ## Quick Start Upload the standard PDF and ask the assistant to decompose all clauses of this standard into test cases and generate the Excel file with medium granularity and reference expansion enabled.

Frequently Asked Questions about standard-interpretation

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

FAQPage Schema
How do I convert a medical device standard into test cases?

Upload the standard PDF or Word file and specify the product category code and standard number. The Skill decomposes each clause into minimal executable test units, classifies them by product and test module codes, and generates a 12-column Excel workbook.

How to generate test cases from GB 9706 or YY 9706 standards?

Provide the standard document and choose granularity (coarse, medium, or fine) plus whether to expand normative references. The Skill handles chapter-level fallback clauses, document review clauses, and referenced-standard expansion, then outputs a clause-ordered Excel file.

Does it work with scanned PDF standards without a text layer?

Yes. The Skill runs a 30-second text-layer precheck first; scanned documents are processed via visual recognition of page images, with OCR-related clause gaps flagged as manual-review items in the output.

What happens if some standard clauses are missed during generation?

The generation script blocks delivery when indexed clauses lack test cases and have no declared exemption in _meta.exempt_clauses. This prevents incomplete coverage from being silently delivered as a finished Excel file.

Can the Excel column layout be customized?

No. The 12-column header is frozen by design; new requirements such as verification-method tags are carried inside existing columns, for example as the first entry in the Keywords column, rather than by adding columns.