[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K454KV0FMEHQQJSPA3C5A9":3,"skill-same:01M6K454KV0FMEHQQJSPA3C5A9":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M6K454KV0FMEHQQJSPA3C5A9","engagement-plan-designer",null,"Design a proportionate public engagement plan for a city decision, matching methods to the decision, audience, legal notice duties, and timeline.","BrianPillmore\u002FMayorGPT","BrianPillmore","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F89977304?v=4","01M6K3S5PAA7GX17DJCHR5QFZ2","01M6K3S5TAA6HKGD1BY6VTV0QB",1,"MIT","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fengagement-plan-designer\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"engagement plan","plan","designer","engagement","engagement plan designer","design","timeline","decision","public","legal","methods","project","matching","notice","public engagement plan","for","2026-11-10 10:12:30",false,"---\nname: engagement-plan-designer\ndescription: Design a proportionate public engagement plan for a city decision, matching methods to the decision, audience, legal notice duties, and timeline.\nargument-hint: [project-or-decision]\n---\n\n# Engagement Plan Designer\n\n**Purpose:** Plan engagement before a decision is made, so input can still change the outcome. Match depth to the stakes, using a spectrum such as inform, consult, involve, collaborate, and decide (IAP2 framework) rather than defaulting to a single open house.\n\n## Required inputs\n- Decision to be made, who decides, and the decision date\n- What is fixed (law, budget, safety) vs. what can change\n- Affected groups, past controversy, and previous engagement\n- Budget, staff, and timeline; legal notice duties (hearings, mailed notice, comment periods)\n\n## Workflow\n1. **Define the promise.** Write what the city will do with input (\"We will consider all input and publish how it shaped the recommendation by ___\"). Never overpromise influence.\n2. **Stakeholder map:** directly affected, interested, those usually missed (renters, workers, youth, non-English speakers, people with disabilities), and decision makers. Consider geographic and demographic data to see who is absent.\n3. **Choose methods per audience and level:** inform (mailers, web page, FAQ), consult (survey, comment period, open house), involve (workshops, advisory group), collaborate (task force, co-design). Pair online with in-person options and meet people where they are.\n4. **Legal layer:** statutory notices and hearings are the floor, not the plan. Advisory groups may be subject to open-meetings law; check membership and quorum (see `open-meeting-risk-check`). Avoid advocacy for ballot measures with public funds (verify).\n5. **Schedule backward from the decision date:** allow time for analysis of input (see `public-comment-summarizer`), response, and staff report drafting.\n6. **Access:** language and disability access (see `language-access-plan`), childcare, time and place, compensation for participation where feasible.\n7. **Messages and materials:** FAQ (see `faq-builder`), clear maps, plain summary, neutral survey wording (no leading questions); collect comparable demographic data.\n8. **Evaluate:** participation counts vs. community makeup, quality of input, satisfaction, and what changed because of it. Publish a \"you said, we did\" summary.\n\n## Output structure\n- One-page plan: purpose, promise, decision timeline\n- Stakeholder and method matrix: group | level | method | date | owner\n- Notice and hearing calendar\n- Budget and risks; evaluation metrics\n\n## Red flags \u002F escalate to the city attorney\n- Predetermined outcome presented as consultation\n- Advisory body forming that may be a covered public body\n- Survey or incentive design that could be viewed as campaigning\n- Data collection with privacy implications\n\n## Common mistakes\n- Engaging after the decision is effectively made\n- Counting online clicks as representative\n- No report-back to participants\n\n*Not legal advice.*\n","# Engagement Plan Designer\n\n**Purpose:** Plan engagement before a decision is made, so input can still change the outcome. Match depth to the stakes, using a spectrum such as inform, consult, involve, collaborate, and decide (IAP2 framework) rather than defaulting to a single open house.\n\n## Required inputs\n- Decision to be made, who decides, and the decision date\n- What is fixed (law, budget, safety) vs. what can change\n- Affected groups, past controversy, and previous engagement\n- Budget, staff, and timeline; legal notice duties (hearings, mailed notice, comment periods)\n\n## Workflow\n1. **Define the promise.** Write what the city will do with input (\"We will consider all input and publish how it shaped the recommendation by ___\"). Never overpromise influence.\n2. **Stakeholder map:** directly affected, interested, those usually missed (renters, workers, youth, non-English speakers, people with disabilities), and decision makers. Consider geographic and demographic data to see who is absent.\n3. **Choose methods per audience and level:** inform (mailers, web page, FAQ), consult (survey, comment period, open house), involve (workshops, advisory group), collaborate (task force, co-design). Pair online with in-person options and meet people where they are.\n4. **Legal layer:** statutory notices and hearings are the floor, not the plan. Advisory groups may be subject to open-meetings law; check membership and quorum (see `open-meeting-risk-check`). Avoid advocacy for ballot measures with public funds (verify).\n5. **Schedule backward from the decision date:** allow time for analysis of input (see `public-comment-summarizer`), response, and staff report drafting.\n6. **Access:** language and disability access (see `language-access-plan`), childcare, time and place, compensation for participation where feasible.\n7. **Messages and materials:** FAQ (see `faq-builder`), clear maps, plain summary, neutral survey wording (no leading questions); collect comparable demographic data.\n8. **Evaluate:** participation counts vs. community makeup, quality of input, satisfaction, and what changed because of it. Publish a \"you said, we did\" summary.\n\n## Output structure\n- One-page plan: purpose, promise, decision timeline\n- Stakeholder and method matrix: group | level | method | date | owner\n- Notice and hearing calendar\n- Budget and risks; evaluation metrics\n\n## Red flags \u002F escalate to the city attorney\n- Predetermined outcome presented as consultation\n- Advisory body forming that may be a covered public body\n- Survey or incentive design that could be viewed as campaigning\n- Data collection with privacy implications\n\n## Common mistakes\n- Engaging after the decision is effectively made\n- Counting online clicks as representative\n- No report-back to participants\n\n*Not legal advice.*\n",{"name":5,"description":7,"argument-hint":39},[40],"project-or-decision","master","edf1fceb08dc8ba63f1ad9159df28c1e0ef449fb","skills\u002Fpublic-engagement\u002Fengagement-plan-designer",0,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT","https:\u002F\u002Fgithub.com\u002FBrianPillmore","2026-11-02 04:58:40",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add BrianPillmore\u002FMayorGPT --skill engagement-plan-designer",{"tool":54,"command":55},"bunx","bunx skills add BrianPillmore\u002FMayorGPT --skill engagement-plan-designer",{"tool":57,"command":58},"pnpm","pnpm dlx skills add BrianPillmore\u002FMayorGPT --skill engagement-plan-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fengagement-plan-designer\u002FSKILL.md",true,[],[63,82,95,127,145,158],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":34},"01M6K466QB0Q2EVZRJ5X1XY21C","town-hall-kit","Prepare a town hall kit with agenda, ground rules, likely questions, follow-up method, and message priorities.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Ftown-hall-kit\u002FSKILL.md",[],[70,71,72,73,74,75,76,77,78,79,80,81],"town hall kit","kit","follow-up","questions","with","event","agenda","prepare","priorities","message","Rules","up",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":34},"01M6K462B8XJ2FFYH8BAXR0ZM5","speechwriter","Draft remarks for the mayor, council, manager, or department head in a strong but grounded municipal voice.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fspeechwriter\u002FSKILL.md",[],[84,89,90,91,92,93,75,94,33],"draft","council","voice","but","head","manager",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":111,"publishedAt":34},"01M6K45Z8MYT7FVMV48WE0MACS","social-post-series","Generate a multi-post city social media series with tone control, accessibility, and channel fit.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fsocial-post-series\u002FSKILL.md",[101,106],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[112,113,114,115,116,117,118,74,119,120,121,122,123,124,125,126],"social post","series","post","social","social post series","fit","multi","social media","control","accessibility","generate","Media","channel","campaign","tone",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":136,"publishedAt":34},"01M6K45W3AWHA1GMZV2PRDYJBS","public-comment-summarizer","Synthesize hearing or meeting comments into themes, misconceptions, unanswered questions, and response options.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fpublic-comment-summarizer\u002FSKILL.md",[133],{"categoryNo":134,"categoryName":135,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000034","行政与办公人员",[26,137,138,139,140,141,142,73,143,144],"public comment summarizer","public comment","summarizer","options","synthesize","themes","comments","meeting",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":34},"01M6K45QWBXSDMGQTA1E9NC43M","press-release-writer","Write a city press release that is accurate, readable, and aligned with legal and operational review needs.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fpress-release-writer\u002FSKILL.md",[],[152,153,154,155,156,157,27,74],"press release writer","press release","writer","release","review","write",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":165,"publishedAt":34},"01M6K45JXZRSW4XXH78FTRBB2A","meeting-notice-drafter","Draft a legally sufficient public notice for any city council, board, commission, or committee meeting — covering required content, posting deadlines, and special-meeting or emergency-meeting rules.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fmeeting-notice-drafter\u002FSKILL.md",[164],{"categoryNo":134,"categoryName":135,"taxonomyType":109,"taxonomyTypeDesc":110},[166,144,31,167,80,26,168,89,169,170,33,90],"meeting notice drafter","content","board","posting","type"]