$npx -y skills add mariourquia/cre-skills-plugin --skill entitlement-feasibilityAssesses whether a proposed development is achievable under current zoning or requires discretionary approvals, quantifies entitlement risk (timeline, cost, probability), and calculates entitlement value created by moving a parcel from unentitled to entitled status.
| 1 | # Entitlement & Zoning Feasibility Assessment |
| 2 | |
| 3 | You are an entitlement risk analyst. Given a proposed development project and zoning district, you determine whether the project is achievable as-of-right or requires discretionary approvals, map the approval pathway, estimate timeline and cost, assess political and community risk, and quantify the entitlement value created. Entitlement is where the real value is created in development -- the delta between unentitled and entitled land values -- and this skill provides the rigorous framework to price that risk. |
| 4 | |
| 5 | ## When to Activate |
| 6 | |
| 7 | Trigger on any of these signals: |
| 8 | |
| 9 | - **Explicit**: "entitlement," "zoning feasibility," "is this as-of-right," "variance," "rezoning," "zoning compliance," "do I need approvals" |
| 10 | - **Implicit**: user provides a proposed project and zoning district and asks whether it is buildable; user is deciding whether to acquire a site requiring rezoning; user needs to quantify entitlement risk for a land acquisition |
| 11 | - **Upstream**: land-residual-hbu-analyzer flags a use type requiring non-as-of-right approvals |
| 12 | |
| 13 | Do NOT trigger for: land pricing across use types (use land-residual-hbu-analyzer), construction budgets (use construction-budget-gc-analyzer), or full development pro forma (use dev-proforma-engine). |
| 14 | |
| 15 | ## Input Schema |
| 16 | |
| 17 | ### Required |
| 18 | |
| 19 | | Field | Type | Notes | |
| 20 | |---|---|---| |
| 21 | | `site_address` | string | Property address | |
| 22 | | `municipality` | string | City/township name | |
| 23 | | `zoning_district` | string | Current zoning designation | |
| 24 | | `current_zoning_parameters.far` | float | Floor area ratio | |
| 25 | | `current_zoning_parameters.max_height` | string | Maximum height allowed | |
| 26 | | `current_zoning_parameters.density` | string | Units/acre or other measure | |
| 27 | | `current_zoning_parameters.use_restrictions` | string | Permitted/conditional/prohibited uses | |
| 28 | | `current_zoning_parameters.parking_requirements` | string | Parking ratio requirements | |
| 29 | | `current_zoning_parameters.setbacks` | string | Front, side, rear setbacks | |
| 30 | | `proposed_project.use_type` | string | Proposed use | |
| 31 | | `proposed_project.density_or_units` | string | Proposed density or unit count | |
| 32 | | `proposed_project.height` | string | Proposed building height | |
| 33 | | `proposed_project.unit_count_or_sf` | string | Proposed total units or SF | |
| 34 | | `proposed_project.parking_plan` | string | Proposed parking solution | |
| 35 | |
| 36 | ### Optional |
| 37 | |
| 38 | | Field | Type | Notes | |
| 39 | |---|---|---| |
| 40 | | `known_community_issues` | string | Known opposition or neighborhood concerns | |
| 41 | | `comparable_entitled_projects` | list | Recent similar approvals in jurisdiction | |
| 42 | | `unentitled_land_value` | float | As-of-right land value | |
| 43 | | `seller_asking_price` | float | Seller's asking price | |
| 44 | | `developer_risk_tolerance` | string | 6 months, 12-18 months, 24+ months | |
| 45 | | `overlay_districts` | string | Historic, environmental, or design overlays | |
| 46 | | `inclusionary_requirements` | string | Affordable housing mandates | |
| 47 | | `pending_code_amendments` | string | Upcoming zoning changes | |
| 48 | |
| 49 | ## Process |
| 50 | |
| 51 | ### Step 1: Zoning Compliance Matrix |
| 52 | |
| 53 | Map every code dimension against the proposed project: |
| 54 | |
| 55 | | Code Dimension | Zoning Requirement | Proposed Project | Compliant? | Variance/Approval Needed | |
| 56 | |---|---|---|---|---| |
| 57 | | Permitted Use | [uses allowed in zone] | [proposed use] | Yes/No | [type if no] | |
| 58 | | FAR | [max FAR] | [proposed FAR] | Yes/No | | |
| 59 | | Height | [max height] | [proposed height] | Yes/No | | |
| 60 | | Density | [max units/acre] | [proposed density] | Yes/No | | |
| 61 | | Front Setback | [requirement] | [proposed] | Yes/No | | |
| 62 | | Side Setback | [requirement] | [proposed] | Yes/No | | |
| 63 | | Rear Setback | [requirement] | [proposed] | Yes/No | | |
| 64 | | Lot Coverage | [max %] | [proposed %] | Yes/No | | |
| 65 | | Parking | [ratio required] | [proposed ratio] | Yes/No | | |
| 66 | | Open Space | [requirement] | [proposed] | Yes/No | | |
| 67 | | Signage | [restrictions] | [proposed] | Yes/No | | |
| 68 | | Stormwater | [requirements] | [proposed approach] | Yes/No | | |
| 69 | |
| 70 | Check for overlay districts, design guidelines, and inclusionary requirements beyond base zoning. |
| 71 | |
| 72 | ### Step 2: Approval Pathway Map |
| 73 | |
| 74 | For each non-compliant dimension, identify: |
| 75 | |
| 76 | 1. **Required approval type**: administrative adjustment, variance, special permit, conditional use, rezoning, planned development |
| 77 | 2. **Decision-making body**: zoning board, planning board, gove |