[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MFSMHZVXZCSKR1SR34RM1":3,"skill-same:01M71MFSMHZVXZCSKR1SR34RM1":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M71MFSMHZVXZCSKR1SR34RM1","change-request",null,"Create a change management request with impact analysis and rollback plan. Use when proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fchange-request\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fchange-request\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"request","change request","change","deployment","for","planning","risk","steps","plan","work","create","communications","review","rollback plan","analysis","rollout","when","impact","knowledge","change management","2026-11-10 10:56:23",false,"---\nname: change-request\ndescription: \"Create a change management request with impact analysis and rollback plan. Use when proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout.\"\ntags: []\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\nsource_path: \"operations\u002Fskills\u002Fchange-request\"\nsource_commit: 8444efcd48f7012f09797778a36a33e73d0861f4\n---\n# \u002Fchange-request\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nCreate a structured change request with impact analysis, risk assessment, and rollback plan.\n\n## Usage\n\n```\n\u002Fchange-request $ARGUMENTS\n```\n\n## Change Management Framework\n\nApply the assess-plan-execute-sustain framework when building the request:\n\n### 1. Assess\n- What is changing?\n- Who is affected?\n- How significant is the change? (Low \u002F Medium \u002F High)\n- What resistance should we expect?\n\n### 2. Plan\n- Communication plan (who, what, when, how)\n- Training plan (what skills are needed, how to deliver)\n- Support plan (help desk, champions, FAQs)\n- Timeline with milestones\n\n### 3. Execute\n- Announce and explain the \"why\"\n- Train and support\n- Monitor adoption\n- Address resistance\n\n### 4. Sustain\n- Measure adoption and effectiveness\n- Reinforce new behaviors\n- Address lingering issues\n- Document lessons learned\n\n## Communication Principles\n\n- Explain the **why** before the **what**\n- Communicate early and often\n- Use multiple channels\n- Acknowledge what's being lost, not just what's being gained\n- Provide a clear path for questions and concerns\n\n## Output\n\n```markdown\n## Change Request: [Title]\n**Requester:** [Name] | **Date:** [Date] | **Priority:** [Critical\u002FHigh\u002FMedium\u002FLow]\n**Status:** Draft | Pending Approval | Approved | In Progress | Complete\n\n### Description\n[What is changing and why]\n\n### Business Justification\n[Why this change is needed — cost savings, compliance, efficiency, risk reduction]\n\n### Impact Analysis\n| Area | Impact | Details |\n|------|--------|---------|\n| Users | [High\u002FMed\u002FLow\u002FNone] | [Who is affected and how] |\n| Systems | [High\u002FMed\u002FLow\u002FNone] | [What systems are affected] |\n| Processes | [High\u002FMed\u002FLow\u002FNone] | [What workflows change] |\n| Cost | [High\u002FMed\u002FLow\u002FNone] | [Budget impact] |\n\n### Risk Assessment\n| Risk | Likelihood | Impact | Mitigation |\n|------|-----------|--------|------------|\n| [Risk] | [H\u002FM\u002FL] | [H\u002FM\u002FL] | [How to mitigate] |\n\n### Implementation Plan\n| Step | Owner | Timeline | Dependencies |\n|------|-------|----------|--------------|\n| [Step] | [Person] | [Date] | [What it depends on] |\n\n### Communication Plan\n| Audience | Message | Channel | Timing |\n|----------|---------|---------|--------|\n| [Who] | [What to tell them] | [How] | [When] |\n\n### Rollback Plan\n[Step-by-step plan to reverse the change if needed]\n- Trigger: [When to roll back]\n- Steps: [How to roll back]\n- Verification: [How to confirm rollback worked]\n\n### Approvals Required\n| Approver | Role | Status |\n|----------|------|--------|\n| [Name] | [Role] | Pending |\n```\n\n## If Connectors Available\n\nIf **~~ITSM** is connected:\n- Create the change request ticket automatically\n- Pull change advisory board schedule and approval workflows\n\nIf **~~project tracker** is connected:\n- Link to related implementation tasks and dependencies\n- Track change progress against milestones\n\nIf **~~chat** is connected:\n- Draft stakeholder notifications for the communication plan\n- Post change updates to the relevant team channels\n\n## Tips\n\n1. **Be specific about impact** — \"Everyone\" is not an impact assessment. \"200 users in the billing team\" is.\n2. **Always have a rollback plan** — Even if you're confident, plan for failure.\n3. **Communicate early** — Surprises create resistance. Previews create buy-in.\n","# \u002Fchange-request\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nCreate a structured change request with impact analysis, risk assessment, and rollback plan.\n\n## Usage\n\n```\n\u002Fchange-request $ARGUMENTS\n```\n\n## Change Management Framework\n\nApply the assess-plan-execute-sustain framework when building the request:\n\n### 1. Assess\n- What is changing?\n- Who is affected?\n- How significant is the change? (Low \u002F Medium \u002F High)\n- What resistance should we expect?\n\n### 2. Plan\n- Communication plan (who, what, when, how)\n- Training plan (what skills are needed, how to deliver)\n- Support plan (help desk, champions, FAQs)\n- Timeline with milestones\n\n### 3. Execute\n- Announce and explain the \"why\"\n- Train and support\n- Monitor adoption\n- Address resistance\n\n### 4. Sustain\n- Measure adoption and effectiveness\n- Reinforce new behaviors\n- Address lingering issues\n- Document lessons learned\n\n## Communication Principles\n\n- Explain the **why** before the **what**\n- Communicate early and often\n- Use multiple channels\n- Acknowledge what's being lost, not just what's being gained\n- Provide a clear path for questions and concerns\n\n## Output\n\n```markdown\n## Change Request: [Title]\n**Requester:** [Name] | **Date:** [Date] | **Priority:** [Critical\u002FHigh\u002FMedium\u002FLow]\n**Status:** Draft | Pending Approval | Approved | In Progress | Complete\n\n### Description\n[What is changing and why]\n\n### Business Justification\n[Why this change is needed — cost savings, compliance, efficiency, risk reduction]\n\n### Impact Analysis\n| Area | Impact | Details |\n|------|--------|---------|\n| Users | [High\u002FMed\u002FLow\u002FNone] | [Who is affected and how] |\n| Systems | [High\u002FMed\u002FLow\u002FNone] | [What systems are affected] |\n| Processes | [High\u002FMed\u002FLow\u002FNone] | [What workflows change] |\n| Cost | [High\u002FMed\u002FLow\u002FNone] | [Budget impact] |\n\n### Risk Assessment\n| Risk | Likelihood | Impact | Mitigation |\n|------|-----------|--------|------------|\n| [Risk] | [H\u002FM\u002FL] | [H\u002FM\u002FL] | [How to mitigate] |\n\n### Implementation Plan\n| Step | Owner | Timeline | Dependencies |\n|------|-------|----------|--------------|\n| [Step] | [Person] | [Date] | [What it depends on] |\n\n### Communication Plan\n| Audience | Message | Channel | Timing |\n|----------|---------|---------|--------|\n| [Who] | [What to tell them] | [How] | [When] |\n\n### Rollback Plan\n[Step-by-step plan to reverse the change if needed]\n- Trigger: [When to roll back]\n- Steps: [How to roll back]\n- Verification: [How to confirm rollback worked]\n\n### Approvals Required\n| Approver | Role | Status |\n|----------|------|--------|\n| [Name] | [Role] | Pending |\n```\n\n## If Connectors Available\n\nIf **~~ITSM** is connected:\n- Create the change request ticket automatically\n- Pull change advisory board schedule and approval workflows\n\nIf **~~project tracker** is connected:\n- Link to related implementation tasks and dependencies\n- Track change progress against milestones\n\nIf **~~chat** is connected:\n- Draft stakeholder notifications for the communication plan\n- Post change updates to the relevant team channels\n\n## Tips\n\n1. **Be specific about impact** — \"Everyone\" is not an impact assessment. \"200 users in the billing team\" is.\n2. **Always have a rollback plan** — Even if you're confident, plan for failure.\n3. **Communicate early** — Surprises create resistance. Previews create buy-in.\n",{"name":5,"tags":44,"tools":45,"source":46,"license":14,"description":7,"source_path":47,"source_commit":48},[],[],"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","operations\u002Fskills\u002Fchange-request","8444efcd48f7012f09797778a36a33e73d0861f4","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fchange-request",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add monoes\u002Fmonomind --skill change-request",{"tool":64,"command":65},"bunx","bunx skills add monoes\u002Fmonomind --skill change-request",{"tool":67,"command":68},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill change-request","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fchange-request\u002FSKILL.md",true,[72],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",11607,[78,103,138,163,187,214],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":102},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[85,86,87,88,89,90,91,37,36,92,93,31,94,95,96,97,98,99,100,101],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","query","snark","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":107,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":121,"publishedAt":102},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[111,116],{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[122,123,124,89,125,126,35,127,92,128,129,27,130,131,132,133,134,135,136,137],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":148,"publishedAt":102},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[145],{"categoryNo":146,"categoryName":147,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000031","产品经理",[131,149,150,151,152,37,153,35,154,155,28,130,19,156,157,158,159,160,161,162],"write spec","spec","user request","problem","acceptance","ask","vague","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":173,"publishedAt":102},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[170],{"categoryNo":171,"categoryName":172,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000033","数据分析师",[92,131,174,175,23,176,37,161,35,177,178,179,180,28,181,182,183,184,185,186],"write query","postgres","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":199,"publishedAt":102},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[193,196],{"categoryNo":194,"categoryName":195,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":197,"categoryName":198,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000023","Skill与智能体开发",[200,201,202,203,23,204,205,206,207,36,208,209,210,92,94,181,211,212,213,183],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":221,"publishedAt":102},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[220],{"categoryNo":197,"categoryName":198,"taxonomyType":114,"taxonomyTypeDesc":115},[202,222,223,224,225,226,24,23,227,228,128,229,230,231,94,181,232,233,183,234],"workflow architect","architect","trees","user journeys","branch","map","workflows","architecture","state","leadership","recovery","operations","systems"]