[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DSK1KBNDSGSQPSSJ0PW400":3,"skill-same:01M6DSK1KBNDSGSQPSSJ0PW400":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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M6DSK1KBNDSGSQPSSJ0PW400","atlassian-templates",null,"Atlassian Template and Files Creator\u002FModifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts, reusable components, and standardized content structures. Use when building org-wide templates, custom blueprints, page layouts, and automated content generation.","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\u002Fproject-management\u002Fatlassian-templates\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"templates","atlassian templates","atlassian","components","jira","content","confluence","template","page","use","files","reusable","expert","generation","2026-11-10 10:12:30",false,"---\nname: \"atlassian-templates\"\ndescription: Atlassian Template and Files Creator\u002FModifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts, reusable components, and standardized content structures. Use when building org-wide templates, custom blueprints, page layouts, and automated content generation.\n---\n\n# Atlassian Template & Files Creator Expert\n\nSpecialist in creating, modifying, and managing reusable templates and files for Jira and Confluence. Ensures consistency, accelerates content creation, and maintains org-wide standards.\n\n---\n\n## Workflows\n\n### Template Creation Process\n1. **Discover**: Interview stakeholders to understand needs\n2. **Analyze**: Review existing content patterns\n3. **Design**: Create template structure and placeholders\n4. **Implement**: Build template with macros and formatting\n5. **Test**: Validate with sample data — confirm template renders correctly in preview before publishing\n6. **Document**: Create usage instructions\n7. **Publish**: Deploy to appropriate space\u002Fproject via MCP (see MCP Operations below)\n8. **Verify**: Confirm deployment success; roll back to previous version if errors occur\n9. **Train**: Educate users on template usage\n10. **Monitor**: Track adoption and gather feedback\n11. **Iterate**: Refine based on usage\n\n### Template Modification Process\n1. **Assess**: Review change request and impact\n2. **Version**: Create new version, keep old available\n3. **Modify**: Update template structure\u002Fcontent\n4. **Test**: Validate changes don't break existing usage; preview updated template before publishing\n5. **Migrate**: Provide migration path for existing content\n6. **Communicate**: Announce changes to users\n7. **Support**: Assist users with migration\n8. **Archive**: Deprecate old version after transition; confirm deprecated template is unlisted, not deleted\n\n### Blueprint Development\n1. Define blueprint scope and purpose\n2. Design multi-page structure\n3. Create page templates for each section\n4. Configure page creation rules\n5. Add dynamic content (Jira queries, user data)\n6. Test blueprint creation flow end-to-end with a sample space\n7. Verify all macro references resolve correctly before deployment\n8. **HANDOFF TO**: Atlassian Admin for global deployment\n\n---\n\n## Confluence Templates Library\n\nSee **TEMPLATES.md** for full reference tables and copy-paste-ready template structures. The following summarises the standard types this skill creates and maintains.\n\n### Confluence Template Types\n| Template | Purpose | Key Macros Used |\n|----------|---------|-----------------|\n| **Meeting Notes** | Structured meeting records with agenda, decisions, and action items | `{date}`, `{tasks}`, `{panel}`, `{info}`, `{note}` |\n| **Project Charter** | Org-level project scope, stakeholder RACI, timeline, and budget | `{panel}`, `{status}`, `{timeline}`, `{info}` |\n| **Sprint Retrospective** | Agile ceremony template with What Went Well \u002F Didn't Go Well \u002F Actions | `{panel}`, `{expand}`, `{tasks}`, `{status}` |\n| **PRD** | Feature definition with goals, user stories, functional\u002Fnon-functional requirements, and release plan | `{panel}`, `{status}`, `{jira}`, `{warning}` |\n| **Decision Log** | Structured option analysis with decision matrix and implementation tracking | `{panel}`, `{status}`, `{info}`, `{tasks}` |\n\n**Standard Sections** included across all Confluence templates:\n- Header panel with metadata (owner, date, status)\n- Clearly labelled content sections with inline placeholder instructions\n- Action items block using `{tasks}` macro\n- Related links and references\n\n### Complete Example: Meeting Notes Template\n\nThe following is a copy-paste-ready Meeting Notes template in Confluence storage format (wiki markup):\n\n```\n{panel:title=Meeting Metadata|borderColor=#0052CC|titleBGColor=#0052CC|titleColor=#FFFFFF}\n*Date:* {date}\n*Owner \u002F Facilitator:* @[facilitator name]\n*Attendees:* @[name], @[name]\n*Status:* {status:colour=Yellow|title=In Progress}\n{panel}\n\nh2. Agenda\n# [Agenda item 1]\n# [Agenda item 2]\n# [Agenda item 3]\n\nh2. Discussion & Decisions\n{panel:title=Key Decisions|borderColor=#36B37E|titleBGColor=#36B37E|titleColor=#FFFFFF}\n* *Decision 1:* [What was decided and why]\n* *Decision 2:* [What was decided and why]\n{panel}\n\n{info:title=Notes}\n[Detailed discussion notes, context, or background here]\n{info}\n\nh2. Action Items\n{tasks}\n* [ ] [Action item] — Owner: @[name] — Due: {date}\n* [ ] [Action item] — Owner: @[name] — Due: {date}\n{tasks}\n\nh2. Next Steps & Related Links\n* Next meeting: {date}\n* Related pages: [link]\n* Related Jira issues: {jira:key=PROJ-123}\n```\n\n> Full examples for all other template types (Project Charter, Sprint Retrospective, PRD, Decision Log) and all Jira templates can be generated on request or found in **TEMPLATES.md**.\n\n---\n\n## Jira Templates Library\n\n### Jira Template Types\n| Template | Purpose | Key Sections |\n|----------|---------|--------------|\n| **User Story** | Feature requests in As a \u002F I want \u002F So that format | Acceptance Criteria (Given\u002FWhen\u002FThen), Design links, Technical Notes, Definition of Done |\n| **Bug Report** | Defect capture with reproduction steps | Environment, Steps to Reproduce, Expected vs Actual Behavior, Severity, Workaround |\n| **Epic** | High-level initiative scope | Vision, Goals, Success Metrics, Story Breakdown, Dependencies, Timeline |\n\n**Standard Sections** included across all Jira templates:\n- Clear summary line\n- Acceptance or success criteria as checkboxes\n- Related issues and dependencies block\n- Definition of Done (for stories)\n\n---\n\n## Macro Usage Guidelines\n\n**Dynamic Content**: Use macros for auto-updating content (dates, user mentions, Jira queries)\n**Visual Hierarchy**: Use `{panel}`, `{info}`, and `{note}` to create visual distinction\n**Interactivity**: Use `{expand}` for collapsible sections in long templates\n**Integration**: Embed Jira charts and tables via `{jira}` macro for live data\n\n---\n\n## Atlassian MCP Integration\n\n**Primary Tools**: Confluence MCP, Jira MCP\n\n### Template Operations via MCP\n\nAll MCP calls below use the exact parameter names expected by the Atlassian MCP server. Replace angle-bracket placeholders with real values before executing.\n\n**Create a Confluence page template:**\n```json\n{\n  \"tool\": \"confluence_create_page\",\n  \"parameters\": {\n    \"space_key\": \"PROJ\",\n    \"title\": \"Template: Meeting Notes\",\n    \"body\": \"\u003Cstorage-format template content>\",\n    \"labels\": [\"template\", \"meeting-notes\"],\n    \"parent_id\": \"\u003Coptional parent page id>\"\n  }\n}\n```\n\n**Update an existing template:**\n```json\n{\n  \"tool\": \"confluence_update_page\",\n  \"parameters\": {\n    \"page_id\": \"\u003Cexisting page id>\",\n    \"version\": \"\u003Ccurrent_version + 1>\",\n    \"title\": \"Template: Meeting Notes\",\n    \"body\": \"\u003Cupdated storage-format content>\",\n    \"version_comment\": \"v2 — added status macro to header\"\n  }\n}\n```\n\n**Create a Jira issue description template (via field configuration):**\n```json\n{\n  \"tool\": \"jira_update_field_configuration\",\n  \"parameters\": {\n    \"project_key\": \"PROJ\",\n    \"field_id\": \"description\",\n    \"default_value\": \"\u003Ctemplate markdown or Atlassian Document Format JSON>\"\n  }\n}\n```\n\n**Deploy template to multiple spaces (batch):**\n```json\n\u002F\u002F Repeat for each target space key\n{\n  \"tool\": \"confluence_create_page\",\n  \"parameters\": {\n    \"space_key\": \"\u003CSPACE_KEY>\",\n    \"title\": \"Template: Meeting Notes\",\n    \"body\": \"\u003Cstorage-format template content>\",\n    \"labels\": [\"template\"]\n  }\n}\n\u002F\u002F After each create, verify:\n{\n  \"tool\": \"confluence_get_page\",\n  \"parameters\": {\n    \"space_key\": \"\u003CSPACE_KEY>\",\n    \"title\": \"Template: Meeting Notes\"\n  }\n}\n\u002F\u002F Assert response status == 200 and page body is non-empty before proceeding to next space\n```\n\n**Validation checkpoint after deployment:**\n- Retrieve the created\u002Fupdated page and assert it renders without macro errors\n- Check that `{jira}` embeds resolve against the target Jira project\n- Confirm `{tasks}` blocks are interactive in the published view\n- If any check fails: revert using `confluence_update_page` with `version: \u003Ccurrent + 1>` and the previous version body\n\n---\n\n## Best Practices & Governance\n\n**Org-Specific Standards:**\n- Track template versions with version notes in the page header\n- Mark outdated templates with a `{warning}` banner before archiving; archive (do not delete)\n- Maintain usage guides linked from each template\n- Gather feedback on a quarterly review cycle; incorporate usage metrics before deprecating\n\n**Quality Gates (apply before every deployment):**\n- Example content provided for each section\n- Tested with sample data in preview\n- Version comment added to change log\n- Feedback mechanism in place (comments enabled or linked survey)\n\n**Governance Process**:\n1. Request and justification\n2. Design and review\n3. Testing with pilot users\n4. Documentation\n5. Approval\n6. Deployment (via MCP or manual)\n7. Training\n8. Monitoring\n\n---\n\n## Handoff Protocols\n\nSee **HANDOFFS.md** for the full handoff matrix. Summary:\n\n| Partner | Receives FROM | Sends TO |\n|---------|--------------|---------|\n| **Senior PM** | Template requirements, reporting templates, executive formats | Completed templates, usage analytics, optimization suggestions |\n| **Scrum Master** | Sprint ceremony needs, team-specific requests, retro format preferences | Sprint-ready templates, agile ceremony structures, velocity tracking templates |\n| **Jira Expert** | Issue template requirements, custom field display needs | Issue description templates, field config templates, JQL query templates |\n| **Confluence Expert** | Space-specific needs, global template requests, blueprint requirements | Configured page templates, blueprint structures, deployment plans |\n| **Atlassian Admin** | Org-wide standards, global deployment requirements, compliance templates | Global templates for approval, usage reports, compliance status |\n","# Atlassian Template & Files Creator Expert\n\nSpecialist in creating, modifying, and managing reusable templates and files for Jira and Confluence. Ensures consistency, accelerates content creation, and maintains org-wide standards.\n\n---\n\n## Workflows\n\n### Template Creation Process\n1. **Discover**: Interview stakeholders to understand needs\n2. **Analyze**: Review existing content patterns\n3. **Design**: Create template structure and placeholders\n4. **Implement**: Build template with macros and formatting\n5. **Test**: Validate with sample data — confirm template renders correctly in preview before publishing\n6. **Document**: Create usage instructions\n7. **Publish**: Deploy to appropriate space\u002Fproject via MCP (see MCP Operations below)\n8. **Verify**: Confirm deployment success; roll back to previous version if errors occur\n9. **Train**: Educate users on template usage\n10. **Monitor**: Track adoption and gather feedback\n11. **Iterate**: Refine based on usage\n\n### Template Modification Process\n1. **Assess**: Review change request and impact\n2. **Version**: Create new version, keep old available\n3. **Modify**: Update template structure\u002Fcontent\n4. **Test**: Validate changes don't break existing usage; preview updated template before publishing\n5. **Migrate**: Provide migration path for existing content\n6. **Communicate**: Announce changes to users\n7. **Support**: Assist users with migration\n8. **Archive**: Deprecate old version after transition; confirm deprecated template is unlisted, not deleted\n\n### Blueprint Development\n1. Define blueprint scope and purpose\n2. Design multi-page structure\n3. Create page templates for each section\n4. Configure page creation rules\n5. Add dynamic content (Jira queries, user data)\n6. Test blueprint creation flow end-to-end with a sample space\n7. Verify all macro references resolve correctly before deployment\n8. **HANDOFF TO**: Atlassian Admin for global deployment\n\n---\n\n## Confluence Templates Library\n\nSee **TEMPLATES.md** for full reference tables and copy-paste-ready template structures. The following summarises the standard types this skill creates and maintains.\n\n### Confluence Template Types\n| Template | Purpose | Key Macros Used |\n|----------|---------|-----------------|\n| **Meeting Notes** | Structured meeting records with agenda, decisions, and action items | `{date}`, `{tasks}`, `{panel}`, `{info}`, `{note}` |\n| **Project Charter** | Org-level project scope, stakeholder RACI, timeline, and budget | `{panel}`, `{status}`, `{timeline}`, `{info}` |\n| **Sprint Retrospective** | Agile ceremony template with What Went Well \u002F Didn't Go Well \u002F Actions | `{panel}`, `{expand}`, `{tasks}`, `{status}` |\n| **PRD** | Feature definition with goals, user stories, functional\u002Fnon-functional requirements, and release plan | `{panel}`, `{status}`, `{jira}`, `{warning}` |\n| **Decision Log** | Structured option analysis with decision matrix and implementation tracking | `{panel}`, `{status}`, `{info}`, `{tasks}` |\n\n**Standard Sections** included across all Confluence templates:\n- Header panel with metadata (owner, date, status)\n- Clearly labelled content sections with inline placeholder instructions\n- Action items block using `{tasks}` macro\n- Related links and references\n\n### Complete Example: Meeting Notes Template\n\nThe following is a copy-paste-ready Meeting Notes template in Confluence storage format (wiki markup):\n\n```\n{panel:title=Meeting Metadata|borderColor=#0052CC|titleBGColor=#0052CC|titleColor=#FFFFFF}\n*Date:* {date}\n*Owner \u002F Facilitator:* @[facilitator name]\n*Attendees:* @[name], @[name]\n*Status:* {status:colour=Yellow|title=In Progress}\n{panel}\n\nh2. Agenda\n# [Agenda item 1]\n# [Agenda item 2]\n# [Agenda item 3]\n\nh2. Discussion & Decisions\n{panel:title=Key Decisions|borderColor=#36B37E|titleBGColor=#36B37E|titleColor=#FFFFFF}\n* *Decision 1:* [What was decided and why]\n* *Decision 2:* [What was decided and why]\n{panel}\n\n{info:title=Notes}\n[Detailed discussion notes, context, or background here]\n{info}\n\nh2. Action Items\n{tasks}\n* [ ] [Action item] — Owner: @[name] — Due: {date}\n* [ ] [Action item] — Owner: @[name] — Due: {date}\n{tasks}\n\nh2. Next Steps & Related Links\n* Next meeting: {date}\n* Related pages: [link]\n* Related Jira issues: {jira:key=PROJ-123}\n```\n\n> Full examples for all other template types (Project Charter, Sprint Retrospective, PRD, Decision Log) and all Jira templates can be generated on request or found in **TEMPLATES.md**.\n\n---\n\n## Jira Templates Library\n\n### Jira Template Types\n| Template | Purpose | Key Sections |\n|----------|---------|--------------|\n| **User Story** | Feature requests in As a \u002F I want \u002F So that format | Acceptance Criteria (Given\u002FWhen\u002FThen), Design links, Technical Notes, Definition of Done |\n| **Bug Report** | Defect capture with reproduction steps | Environment, Steps to Reproduce, Expected vs Actual Behavior, Severity, Workaround |\n| **Epic** | High-level initiative scope | Vision, Goals, Success Metrics, Story Breakdown, Dependencies, Timeline |\n\n**Standard Sections** included across all Jira templates:\n- Clear summary line\n- Acceptance or success criteria as checkboxes\n- Related issues and dependencies block\n- Definition of Done (for stories)\n\n---\n\n## Macro Usage Guidelines\n\n**Dynamic Content**: Use macros for auto-updating content (dates, user mentions, Jira queries)\n**Visual Hierarchy**: Use `{panel}`, `{info}`, and `{note}` to create visual distinction\n**Interactivity**: Use `{expand}` for collapsible sections in long templates\n**Integration**: Embed Jira charts and tables via `{jira}` macro for live data\n\n---\n\n## Atlassian MCP Integration\n\n**Primary Tools**: Confluence MCP, Jira MCP\n\n### Template Operations via MCP\n\nAll MCP calls below use the exact parameter names expected by the Atlassian MCP server. Replace angle-bracket placeholders with real values before executing.\n\n**Create a Confluence page template:**\n```json\n{\n  \"tool\": \"confluence_create_page\",\n  \"parameters\": {\n    \"space_key\": \"PROJ\",\n    \"title\": \"Template: Meeting Notes\",\n    \"body\": \"\u003Cstorage-format template content>\",\n    \"labels\": [\"template\", \"meeting-notes\"],\n    \"parent_id\": \"\u003Coptional parent page id>\"\n  }\n}\n```\n\n**Update an existing template:**\n```json\n{\n  \"tool\": \"confluence_update_page\",\n  \"parameters\": {\n    \"page_id\": \"\u003Cexisting page id>\",\n    \"version\": \"\u003Ccurrent_version + 1>\",\n    \"title\": \"Template: Meeting Notes\",\n    \"body\": \"\u003Cupdated storage-format content>\",\n    \"version_comment\": \"v2 — added status macro to header\"\n  }\n}\n```\n\n**Create a Jira issue description template (via field configuration):**\n```json\n{\n  \"tool\": \"jira_update_field_configuration\",\n  \"parameters\": {\n    \"project_key\": \"PROJ\",\n    \"field_id\": \"description\",\n    \"default_value\": \"\u003Ctemplate markdown or Atlassian Document Format JSON>\"\n  }\n}\n```\n\n**Deploy template to multiple spaces (batch):**\n```json\n\u002F\u002F Repeat for each target space key\n{\n  \"tool\": \"confluence_create_page\",\n  \"parameters\": {\n    \"space_key\": \"\u003CSPACE_KEY>\",\n    \"title\": \"Template: Meeting Notes\",\n    \"body\": \"\u003Cstorage-format template content>\",\n    \"labels\": [\"template\"]\n  }\n}\n\u002F\u002F After each create, verify:\n{\n  \"tool\": \"confluence_get_page\",\n  \"parameters\": {\n    \"space_key\": \"\u003CSPACE_KEY>\",\n    \"title\": \"Template: Meeting Notes\"\n  }\n}\n\u002F\u002F Assert response status == 200 and page body is non-empty before proceeding to next space\n```\n\n**Validation checkpoint after deployment:**\n- Retrieve the created\u002Fupdated page and assert it renders without macro errors\n- Check that `{jira}` embeds resolve against the target Jira project\n- Confirm `{tasks}` blocks are interactive in the published view\n- If any check fails: revert using `confluence_update_page` with `version: \u003Ccurrent + 1>` and the previous version body\n\n---\n\n## Best Practices & Governance\n\n**Org-Specific Standards:**\n- Track template versions with version notes in the page header\n- Mark outdated templates with a `{warning}` banner before archiving; archive (do not delete)\n- Maintain usage guides linked from each template\n- Gather feedback on a quarterly review cycle; incorporate usage metrics before deprecating\n\n**Quality Gates (apply before every deployment):**\n- Example content provided for each section\n- Tested with sample data in preview\n- Version comment added to change log\n- Feedback mechanism in place (comments enabled or linked survey)\n\n**Governance Process**:\n1. Request and justification\n2. Design and review\n3. Testing with pilot users\n4. Documentation\n5. Approval\n6. Deployment (via MCP or manual)\n7. Training\n8. Monitoring\n\n---\n\n## Handoff Protocols\n\nSee **HANDOFFS.md** for the full handoff matrix. Summary:\n\n| Partner | Receives FROM | Sends TO |\n|---------|--------------|---------|\n| **Senior PM** | Template requirements, reporting templates, executive formats | Completed templates, usage analytics, optimization suggestions |\n| **Scrum Master** | Sprint ceremony needs, team-specific requests, retro format preferences | Sprint-ready templates, agile ceremony structures, velocity tracking templates |\n| **Jira Expert** | Issue template requirements, custom field display needs | Issue description templates, field config templates, JQL query templates |\n| **Confluence Expert** | Space-specific needs, global template requests, blueprint requirements | Configured page templates, blueprint structures, deployment plans |\n| **Atlassian Admin** | Org-wide standards, global deployment requirements, compliance templates | Global templates for approval, usage reports, compliance status |\n",{"name":5,"description":7},"main","c0a12fc98d85642fa8893e31fc5cf5dfad879de6","project-management\u002Fatlassian-templates",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":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill atlassian-templates",{"tool":51,"command":52},"bunx","bunx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill atlassian-templates",{"tool":54,"command":55},"pnpm","pnpm dlx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill atlassian-templates","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fproject-management\u002Fatlassian-templates\u002FSKILL.md",true,[59,65,69],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fgovernance-framework.md","REFERENCE","参考文档",8900,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fproject-management\u002Fatlassian-templates\u002Freferences\u002Fgovernance-framework.md",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Ftemplate-design-patterns.md",6521,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fproject-management\u002Fatlassian-templates\u002Freferences\u002Ftemplate-design-patterns.md",{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Ftemplate_scaffolder.py","SCRIPT","脚本",16975,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fproject-management\u002Fatlassian-templates\u002Fscripts\u002Ftemplate_scaffolder.py",[76,102,128,159,179,202],{"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":33},"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,28,95,96,97,98,99,100,101],"risk","risk management specialist","management","risk management","risk analysis","risk evaluation","product","Evaluation","Production","lifecycle","analysis","user","risk matrix","Market","device","control","iso","medical","iso 14971",{"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":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":33},"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",[],[109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,100,127],"regulatory affairs head","regulatory","head","documentation","documents","packages","planning","devices","plan","access","write","strategy","evidence","standards","manage","intelligence","across","strategies","clinical",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":144,"publishedAt":33},"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",[134,139],{"categoryNo":135,"categoryName":136,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[145,146,147,148,149,150,112,151,152,153,154,155,28,110,156,157,158,98,99,100],"quality manager qms iso13485","quality","design","review","support","workflows","audit","actions","compliance","system","process","up","maintenance","document",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":33},"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",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000037","律师与法务",[169,146,148,170,171,172,173,153,174,154,85,175,110,176,177,178,99],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":189,"publishedAt":33},"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",[185,188],{"categoryNo":186,"categoryName":187,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":166,"categoryName":167,"taxonomyType":142,"taxonomyTypeDesc":143},[112,190,146,148,191,192,151,92,193,154,194,195,28,196,197,198,100,199,200,201],"quality documentation manager","workflow","change","document lifecycle","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":208,"publishedAt":33},"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",[],[151,209,31,115,210,211,212,213,85,28,214,97,99,100],"qms audit expert","verification","execution","classification","schedule","checklist"]