[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DS5B2YMAMV6ZVHHK55VBKD":3,"skill-same:01M6DS5B2YMAMV6ZVHHK55VBKD":75},{"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":21,"linkOnly":22,"markdownContent":23,"markdownBody":24,"frontMatter":25,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M6DS5B2YMAMV6ZVHHK55VBKD","changelog-generator",null,"Changelog Generator","zhangzhang-111-i\u002Fclaude-skills111","zhangzhang-111-i","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F251344927?v=4","01M6DRBP4NCM1ZCHTT0FW0SQHD","lixiying","01M6DRBPAMFDJSGQ69XPK9KM9J",4,"MIT","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fchangelog-generator\u002FSKILL.md",[],[19,20],"changelog","changelog generator","2026-11-10 10:12:30",false,"---\nname: \"changelog-generator\"\ndescription: \"Changelog Generator\"\n---\n\n# Changelog Generator\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** Release Management \u002F Documentation\n\n## Overview\n\nUse this skill to produce consistent, auditable release notes from Conventional Commits. It separates commit parsing, semantic bump logic, and changelog rendering so teams can automate releases without losing editorial control.\n\n## Core Capabilities\n\n- Parse commit messages using Conventional Commit rules\n- Detect semantic bump (`major`, `minor`, `patch`) from commit stream\n- Render Keep a Changelog sections (`Added`, `Changed`, `Fixed`, etc.)\n- Generate release entries from git ranges or provided commit input\n- Enforce commit format with a dedicated linter script\n- Support CI integration via machine-readable JSON output\n\n## When to Use\n\n- Before publishing a release tag\n- During CI to generate release notes automatically\n- During PR checks to block invalid commit message formats\n- In monorepos where package changelogs require scoped filtering\n- When converting raw git history into user-facing notes\n\n## Key Workflows\n\n### 1. Generate Changelog Entry From Git\n\n```bash\npython3 scripts\u002Fgenerate_changelog.py \\\n  --from-tag v1.3.0 \\\n  --to-tag v1.4.0 \\\n  --next-version v1.4.0 \\\n  --format markdown\n```\n\n### 2. Generate Entry From stdin\u002FFile Input\n\n```bash\ngit log v1.3.0..v1.4.0 --pretty=format:'%s' | \\\n  python3 scripts\u002Fgenerate_changelog.py --next-version v1.4.0 --format markdown\n\npython3 scripts\u002Fgenerate_changelog.py --input commits.txt --next-version v1.4.0 --format json\n```\n\n### 3. Update `CHANGELOG.md`\n\n```bash\npython3 scripts\u002Fgenerate_changelog.py \\\n  --from-tag v1.3.0 \\\n  --to-tag HEAD \\\n  --next-version v1.4.0 \\\n  --write CHANGELOG.md\n```\n\n### 4. Lint Commits Before Merge\n\n```bash\npython3 scripts\u002Fcommit_linter.py --from-ref origin\u002Fmain --to-ref HEAD --strict --format text\n```\n\nOr file\u002Fstdin:\n\n```bash\npython3 scripts\u002Fcommit_linter.py --input commits.txt --strict\ncat commits.txt | python3 scripts\u002Fcommit_linter.py --format json\n```\n\n## Conventional Commit Rules\n\nSupported types:\n\n- `feat`, `fix`, `perf`, `refactor`, `docs`, `test`, `build`, `ci`, `chore`\n- `security`, `deprecated`, `remove`\n\nBreaking changes:\n\n- `type(scope)!: summary`\n- Footer\u002Fbody includes `BREAKING CHANGE:`\n\nSemVer mapping:\n\n- breaking -> `major`\n- non-breaking `feat` -> `minor`\n- all others -> `patch`\n\n## Script Interfaces\n\n- `python3 scripts\u002Fgenerate_changelog.py --help`\n  - Reads commits from git or stdin\u002F`--input`\n  - Renders markdown or JSON\n  - Optional in-place changelog prepend\n- `python3 scripts\u002Fcommit_linter.py --help`\n  - Validates commit format\n  - Returns non-zero in `--strict` mode on violations\n\n## Common Pitfalls\n\n1. Mixing merge commit messages with release commit parsing\n2. Using vague commit summaries that cannot become release notes\n3. Failing to include migration guidance for breaking changes\n4. Treating docs\u002Fchore changes as user-facing features\n5. Overwriting historical changelog sections instead of prepending\n\n## Best Practices\n\n1. Keep commits small and intent-driven.\n2. Scope commit messages (`feat(api): ...`) in multi-package repos.\n3. Enforce linter checks in PR pipelines.\n4. Review generated markdown before publishing.\n5. Tag releases only after changelog generation succeeds.\n6. Keep an `[Unreleased]` section for manual curation when needed.\n\n## References\n\n- [references\u002Fci-integration.md](references\u002Fci-integration.md)\n- [references\u002Fchangelog-formatting-guide.md](references\u002Fchangelog-formatting-guide.md)\n- [references\u002Fmonorepo-strategy.md](references\u002Fmonorepo-strategy.md)\n- [README.md](README.md)\n\n## Release Governance\n\nUse this release flow for predictability:\n\n1. Lint commit history for target release range.\n2. Generate changelog draft from commits.\n3. Manually adjust wording for customer clarity.\n4. Validate semver bump recommendation.\n5. Tag release only after changelog is approved.\n\n## Output Quality Checks\n\n- Each bullet is user-meaningful, not implementation noise.\n- Breaking changes include migration action.\n- Security fixes are isolated in `Security` section.\n- Sections with no entries are omitted.\n- Duplicate bullets across sections are removed.\n\n## CI Policy\n\n- Run `commit_linter.py --strict` on all PRs.\n- Block merge on invalid conventional commits.\n- Auto-generate draft release notes on tag push.\n- Require human approval before writing into `CHANGELOG.md` on main branch.\n\n## Monorepo Guidance\n\n- Prefer commit scopes aligned to package names.\n- Filter commit stream by scope for package-specific releases.\n- Keep infra-wide changes in root changelog.\n- Store package changelogs near package roots for ownership clarity.\n\n## Failure Handling\n\n- If no valid conventional commits found: fail early, do not generate misleading empty notes.\n- If git range invalid: surface explicit range in error output.\n- If write target missing: create safe changelog header scaffolding.\n","# Changelog Generator\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** Release Management \u002F Documentation\n\n## Overview\n\nUse this skill to produce consistent, auditable release notes from Conventional Commits. It separates commit parsing, semantic bump logic, and changelog rendering so teams can automate releases without losing editorial control.\n\n## Core Capabilities\n\n- Parse commit messages using Conventional Commit rules\n- Detect semantic bump (`major`, `minor`, `patch`) from commit stream\n- Render Keep a Changelog sections (`Added`, `Changed`, `Fixed`, etc.)\n- Generate release entries from git ranges or provided commit input\n- Enforce commit format with a dedicated linter script\n- Support CI integration via machine-readable JSON output\n\n## When to Use\n\n- Before publishing a release tag\n- During CI to generate release notes automatically\n- During PR checks to block invalid commit message formats\n- In monorepos where package changelogs require scoped filtering\n- When converting raw git history into user-facing notes\n\n## Key Workflows\n\n### 1. Generate Changelog Entry From Git\n\n```bash\npython3 scripts\u002Fgenerate_changelog.py \\\n  --from-tag v1.3.0 \\\n  --to-tag v1.4.0 \\\n  --next-version v1.4.0 \\\n  --format markdown\n```\n\n### 2. Generate Entry From stdin\u002FFile Input\n\n```bash\ngit log v1.3.0..v1.4.0 --pretty=format:'%s' | \\\n  python3 scripts\u002Fgenerate_changelog.py --next-version v1.4.0 --format markdown\n\npython3 scripts\u002Fgenerate_changelog.py --input commits.txt --next-version v1.4.0 --format json\n```\n\n### 3. Update `CHANGELOG.md`\n\n```bash\npython3 scripts\u002Fgenerate_changelog.py \\\n  --from-tag v1.3.0 \\\n  --to-tag HEAD \\\n  --next-version v1.4.0 \\\n  --write CHANGELOG.md\n```\n\n### 4. Lint Commits Before Merge\n\n```bash\npython3 scripts\u002Fcommit_linter.py --from-ref origin\u002Fmain --to-ref HEAD --strict --format text\n```\n\nOr file\u002Fstdin:\n\n```bash\npython3 scripts\u002Fcommit_linter.py --input commits.txt --strict\ncat commits.txt | python3 scripts\u002Fcommit_linter.py --format json\n```\n\n## Conventional Commit Rules\n\nSupported types:\n\n- `feat`, `fix`, `perf`, `refactor`, `docs`, `test`, `build`, `ci`, `chore`\n- `security`, `deprecated`, `remove`\n\nBreaking changes:\n\n- `type(scope)!: summary`\n- Footer\u002Fbody includes `BREAKING CHANGE:`\n\nSemVer mapping:\n\n- breaking -> `major`\n- non-breaking `feat` -> `minor`\n- all others -> `patch`\n\n## Script Interfaces\n\n- `python3 scripts\u002Fgenerate_changelog.py --help`\n  - Reads commits from git or stdin\u002F`--input`\n  - Renders markdown or JSON\n  - Optional in-place changelog prepend\n- `python3 scripts\u002Fcommit_linter.py --help`\n  - Validates commit format\n  - Returns non-zero in `--strict` mode on violations\n\n## Common Pitfalls\n\n1. Mixing merge commit messages with release commit parsing\n2. Using vague commit summaries that cannot become release notes\n3. Failing to include migration guidance for breaking changes\n4. Treating docs\u002Fchore changes as user-facing features\n5. Overwriting historical changelog sections instead of prepending\n\n## Best Practices\n\n1. Keep commits small and intent-driven.\n2. Scope commit messages (`feat(api): ...`) in multi-package repos.\n3. Enforce linter checks in PR pipelines.\n4. Review generated markdown before publishing.\n5. Tag releases only after changelog generation succeeds.\n6. Keep an `[Unreleased]` section for manual curation when needed.\n\n## References\n\n- [references\u002Fci-integration.md](references\u002Fci-integration.md)\n- [references\u002Fchangelog-formatting-guide.md](references\u002Fchangelog-formatting-guide.md)\n- [references\u002Fmonorepo-strategy.md](references\u002Fmonorepo-strategy.md)\n- [README.md](README.md)\n\n## Release Governance\n\nUse this release flow for predictability:\n\n1. Lint commit history for target release range.\n2. Generate changelog draft from commits.\n3. Manually adjust wording for customer clarity.\n4. Validate semver bump recommendation.\n5. Tag release only after changelog is approved.\n\n## Output Quality Checks\n\n- Each bullet is user-meaningful, not implementation noise.\n- Breaking changes include migration action.\n- Security fixes are isolated in `Security` section.\n- Sections with no entries are omitted.\n- Duplicate bullets across sections are removed.\n\n## CI Policy\n\n- Run `commit_linter.py --strict` on all PRs.\n- Block merge on invalid conventional commits.\n- Auto-generate draft release notes on tag push.\n- Require human approval before writing into `CHANGELOG.md` on main branch.\n\n## Monorepo Guidance\n\n- Prefer commit scopes aligned to package names.\n- Filter commit stream by scope for package-specific releases.\n- Keep infra-wide changes in root changelog.\n- Store package changelogs near package roots for ownership clarity.\n\n## Failure Handling\n\n- If no valid conventional commits found: fail early, do not generate misleading empty notes.\n- If git range invalid: surface explicit range in error output.\n- If write target missing: create safe changelog header scaffolding.\n",{"name":5,"description":7},"main","c0a12fc98d85642fa8893e31fc5cf5dfad879de6","engineering\u002Fchangelog-generator",0,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i","2026-03-13 21:49:18",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill changelog-generator",{"tool":39,"command":40},"bunx","bunx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill changelog-generator",{"tool":42,"command":43},"pnpm","pnpm dlx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill changelog-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fchangelog-generator\u002FSKILL.md",true,[47,53,57,61,65,71],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"README.md","REFERENCE","参考文档",1163,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fchangelog-generator\u002FREADME.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fchangelog-formatting-guide.md",316,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fchangelog-generator\u002Freferences\u002Fchangelog-formatting-guide.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fci-integration.md",509,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fchangelog-generator\u002Freferences\u002Fci-integration.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fmonorepo-strategy.md",1356,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fchangelog-generator\u002Freferences\u002Fmonorepo-strategy.md",{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"scripts\u002Fcommit_linter.py","SCRIPT","脚本",4013,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fchangelog-generator\u002Fscripts\u002Fcommit_linter.py",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Fgenerate_changelog.py",7911,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fchangelog-generator\u002Fscripts\u002Fgenerate_changelog.py",[76,103,129,160,180,203],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":21},"01M6DSNYM8PZKEXGYMRX53PVPH","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102],"risk","risk management specialist","management","risk management","risk analysis","risk evaluation","product","Evaluation","Production","lifecycle","analysis","user","use","risk matrix","Market","device","control","iso","medical","iso 14971",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":21},"01M6DSNSRBGVZWS23TK0ZQ52QC","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,101,128],"regulatory affairs head","regulatory","head","documentation","documents","packages","planning","devices","plan","access","write","strategy","evidence","standards","manage","intelligence","across","strategies","clinical",{"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":6,"sourceHtmlUrl":133,"categories":134,"keywords":145,"publishedAt":21},"01M6DSNN7GNR2HZE66S4D31EP8","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[135,140],{"categoryNo":136,"categoryName":137,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":141,"categoryName":142,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[146,147,148,149,150,151,113,152,153,154,155,156,95,111,157,158,159,99,100,101],"quality manager qms iso13485","quality","design","review","support","workflows","audit","actions","compliance","system","process","up","maintenance","document",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":169,"publishedAt":21},"01M6DSNE5PQM106PM4EDGPBWGZ","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[166],{"categoryNo":167,"categoryName":168,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000037","律师与法务",[170,147,149,171,172,173,174,154,175,155,85,176,111,177,178,179,100],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":190,"publishedAt":21},"01M6DSN7MYXB6X42TB1GH2TNSB","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[186,189],{"categoryNo":187,"categoryName":188,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":167,"categoryName":168,"taxonomyType":143,"taxonomyTypeDesc":144},[113,191,147,149,192,193,152,92,194,155,195,196,95,197,198,199,101,200,201,202],"quality documentation manager","workflow","change","document lifecycle","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":209,"publishedAt":21},"01M6DSN3R749H3R20K15QE8X8W","qms-audit-expert","ISO 13485 internal audit expertise for medical device QMS. Covers audit planning, execution, nonconformity classification, and CAPA verification. Use for internal audit planning, audit execution, finding classification, external audit preparation, or audit program management.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fqms-audit-expert\u002FSKILL.md",[],[152,210,211,116,212,213,214,215,85,95,216,98,100,101],"qms audit expert","expert","verification","execution","classification","schedule","checklist"]