[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K44DVVDPGW75PR5EAETD2H":3,"skill-same:01M6K44DVVDPGW75PR5EAETD2H":60},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M6K44DVVDPGW75PR5EAETD2H","subdivision-case-brief",null,"Prepare a concise decision brief for platting or subdivision cases with conditions, utility issues, and hearing notes.","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\u002Fplanning-and-growth\u002Fsubdivision-case-brief\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31],"brief","case brief","case","subdivision case brief","prepare","notes","issues","decision","decision brief","name","utility","with","concise","for","2026-11-10 10:12:30",false,"---\nname: subdivision-case-brief\ndescription: Prepare a concise decision brief for platting or subdivision cases with conditions, utility issues, and hearing notes.\nargument-hint: [case-name]\n---\n\n## Purpose\nSummarize a preliminary or final plat, minor subdivision, or lot-line action against the subdivision ordinance, zoning, utilities, and plan so the commission or council can act within the statutory timeline. Most subdivision approvals are ministerial or tightly standard-based: the question is conformance, not preference.\n\n## Required inputs\n- Application, plat sheets, legal description, and checklists; zoning and overlay designation.\n- Subdivision ordinance and engineering standards; adopted plan and street network plan.\n- Reviews: public works\u002Fengineering, utilities, fire (access, hydrants, water flow), stormwater, floodplain, school or park district, county, and utility franchise comments.\n- Infrastructure plans, cost estimates, and security (bond or letter of credit) proposals.\n- Title\u002Fownership evidence, easements, and any development agreement.\n\n## Workflow\n1. Identify the stage and decision type (preliminary, final, minor, replat, vacation) and the statutory shot clock for action; many states deem a plat approved if not acted on in time. Note the date.\n2. Standards check: lot dimensions and area, frontage, block length, street width and connectivity, access spacing, sidewalks, utility easements, drainage, floodplain, and tree\u002Fopen-space requirements. List each as conforms, conforms with condition, or deviates.\n3. Utilities and facilities: water and sewer capacity (not just availability), fire flow, stormwater detention and downstream effects, road adequacy, and school or park dedications.\n4. Public improvements: who builds, to what standard, with what security, inspection, and warranty. Compare security amount to engineer's estimate plus contingency.\n5. Exactions: required dedications or fees must tie to the project's impacts (see exaction-nexus-review). Cite ordinance authority for each.\n6. Conditions of approval: write enforceable, specific conditions with timing (before recording, before building permits, before certificate of occupancy). Avoid vague \"to staff satisfaction\" terms.\n7. Hearing notes: notice requirements met, public comments by theme, legal standard the board must apply, and options (approve, approve with conditions, deny with findings, table when allowed).\n8. Recording: signatures, tax certification, recording deadline, and what makes the approval void.\n\n## Output structure\n| Standard | Requirement | Plat shows | Status | Condition |\nAdd: recommendation, proposed findings, list of conditions with timing, public-improvement and security table, and hearing script cues.\n\n## Red flags \u002F escalate\n- Shot clock about to expire.\n- Insufficient utility capacity or fire flow, or flood-prone lots.\n- Inadequate legal access or disputed easements.\n- Exactions without ordinance authority or nexus.\n- Plat conflicts with an adopted street plan, zoning, or a pending annexation.\n- Quasi-judicial ex parte contact or conflicts: city attorney review.\n\n## Common mistakes\n- Denying on grounds outside the ordinance standards.\n- Approving without security for public improvements.\n- Imposing conditions no one can verify.\n- Overlooking that final plat must substantially conform to preliminary.\n\n## State-law variance\nPlat approval authority, deemed-approval rules, and vested rights vary by state.\n","## Purpose\nSummarize a preliminary or final plat, minor subdivision, or lot-line action against the subdivision ordinance, zoning, utilities, and plan so the commission or council can act within the statutory timeline. Most subdivision approvals are ministerial or tightly standard-based: the question is conformance, not preference.\n\n## Required inputs\n- Application, plat sheets, legal description, and checklists; zoning and overlay designation.\n- Subdivision ordinance and engineering standards; adopted plan and street network plan.\n- Reviews: public works\u002Fengineering, utilities, fire (access, hydrants, water flow), stormwater, floodplain, school or park district, county, and utility franchise comments.\n- Infrastructure plans, cost estimates, and security (bond or letter of credit) proposals.\n- Title\u002Fownership evidence, easements, and any development agreement.\n\n## Workflow\n1. Identify the stage and decision type (preliminary, final, minor, replat, vacation) and the statutory shot clock for action; many states deem a plat approved if not acted on in time. Note the date.\n2. Standards check: lot dimensions and area, frontage, block length, street width and connectivity, access spacing, sidewalks, utility easements, drainage, floodplain, and tree\u002Fopen-space requirements. List each as conforms, conforms with condition, or deviates.\n3. Utilities and facilities: water and sewer capacity (not just availability), fire flow, stormwater detention and downstream effects, road adequacy, and school or park dedications.\n4. Public improvements: who builds, to what standard, with what security, inspection, and warranty. Compare security amount to engineer's estimate plus contingency.\n5. Exactions: required dedications or fees must tie to the project's impacts (see exaction-nexus-review). Cite ordinance authority for each.\n6. Conditions of approval: write enforceable, specific conditions with timing (before recording, before building permits, before certificate of occupancy). Avoid vague \"to staff satisfaction\" terms.\n7. Hearing notes: notice requirements met, public comments by theme, legal standard the board must apply, and options (approve, approve with conditions, deny with findings, table when allowed).\n8. Recording: signatures, tax certification, recording deadline, and what makes the approval void.\n\n## Output structure\n| Standard | Requirement | Plat shows | Status | Condition |\nAdd: recommendation, proposed findings, list of conditions with timing, public-improvement and security table, and hearing script cues.\n\n## Red flags \u002F escalate\n- Shot clock about to expire.\n- Insufficient utility capacity or fire flow, or flood-prone lots.\n- Inadequate legal access or disputed easements.\n- Exactions without ordinance authority or nexus.\n- Plat conflicts with an adopted street plan, zoning, or a pending annexation.\n- Quasi-judicial ex parte contact or conflicts: city attorney review.\n\n## Common mistakes\n- Denying on grounds outside the ordinance standards.\n- Approving without security for public improvements.\n- Imposing conditions no one can verify.\n- Overlooking that final plat must substantially conform to preliminary.\n\n## State-law variance\nPlat approval authority, deemed-approval rules, and vested rights vary by state.\n",{"name":5,"description":7,"argument-hint":37},[38],"case-name","master","edf1fceb08dc8ba63f1ad9159df28c1e0ef449fb","skills\u002Fplanning-and-growth\u002Fsubdivision-case-brief",0,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT","https:\u002F\u002Fgithub.com\u002FBrianPillmore","2026-11-02 04:58:40",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add BrianPillmore\u002FMayorGPT --skill subdivision-case-brief",{"tool":52,"command":53},"bunx","bunx skills add BrianPillmore\u002FMayorGPT --skill subdivision-case-brief",{"tool":55,"command":56},"pnpm","pnpm dlx skills add BrianPillmore\u002FMayorGPT --skill subdivision-case-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fplanning-and-growth\u002Fsubdivision-case-brief\u002FSKILL.md",true,[],[61,78,91,123,142,156],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":32},"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",[],[68,69,70,71,29,72,73,22,74,75,76,77],"town hall kit","kit","follow-up","questions","event","agenda","priorities","message","Rules","up",{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":32},"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",[],[80,85,86,87,88,89,72,90,31],"draft","council","voice","but","head","manager",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":107,"publishedAt":32},"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",[97,102],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[108,109,110,111,112,113,114,29,115,116,117,118,119,120,121,122],"social post","series","post","social","social post series","fit","multi","social media","control","accessibility","generate","Media","channel","campaign","tone",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":132,"publishedAt":32},"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",[129],{"categoryNo":130,"categoryName":131,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000034","行政与办公人员",[133,134,135,136,137,138,139,71,140,141],"public","public comment summarizer","public comment","summarizer","options","synthesize","themes","comments","meeting",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":32},"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",[],[149,150,151,152,153,154,155,29],"press release writer","press release","writer","release","review","write","legal",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":163,"publishedAt":32},"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",[162],{"categoryNo":130,"categoryName":131,"taxonomyType":105,"taxonomyTypeDesc":106},[164,141,165,166,76,133,167,85,168,169,31,86],"meeting notice drafter","notice","content","board","posting","type"]