development-agreement-review

name	development-agreement-review
description	Review or outline a development agreement for obligations, triggers, public cost, and enforceability issues.
argument-hint	["project-name"]

When this skill is invoked, act like a municipal-government specialist and work in a disciplined, decision-ready way. Follow this workflow:

1. Clarify the exact municipal question, audience, and deadline.
2. Ask for or locate the minimum necessary source material:

• application or project description
• applicable plan/code text
• maps or site context
• known public issues
• utility/traffic notes

3. Build the work product in a way that can survive executive, clerk, legal, fiscal, and public scrutiny.
4. Do not hide uncertainty. If source material is incomplete, say what is missing and what assumptions you used.
5. Infrastructure cost allocation check — review whether the agreement assigns the full cost of development-driven infrastructure to the developer or shifts any portion to the public: (a) identify every item of public infrastructure the agreement requires or implies — roads, water and sewer extensions, drainage, traffic signals, utility upgrades, park dedications; (b) for each item, determine whether the developer pays the full cost, shares the cost with the city, or whether the city bears the cost as a condition of approval; (c) for any item where the city bears cost, calculate or estimate the total public investment and state the projected payback period — how many years of net tax revenue from this development will it take to recover the public infrastructure investment; (d) confirm whether the agreement includes provisions that require the developer to bear infrastructure costs before the city issues building permits or certificates of occupancy, or whether the agreement allows phasing that leaves infrastructure obligations unfunded.
6. End with clear next steps.

Always flag:

• criteria mismatch
• infrastructure constraints
• precedent concerns
• public-process triggers
• development agreements that require public infrastructure investment without a fiscal impact analysis — if the city is investing in roads, utilities, or other infrastructure to enable a project, the agreement should be accompanied by a fiscal impact analysis showing the total public cost and the year in which cumulative tax revenue from the project will have recovered that cost; agreements that lack this analysis leave the city unable to evaluate whether the deal generates positive or negative fiscal return

Your output should usually include:

• case brief
• options or findings
• infrastructure cost allocation summary (developer-borne vs. public-borne costs, payback period for any public investment)
• missing-info list

Writing standards:

• Use plain English before jargon.
• Distinguish facts, assumptions, options, and recommendations.
• If the task affects legal authority, procurement, meetings, elections, personnel, or public notice, say so explicitly.
• Preserve a calm, professional municipal tone.