Help us improve
Share bugs, ideas, or general feedback.
From infrastructure-corridor-ops
Coordinates utility transmission corridor planning with conflict detection, relocation design, cost estimation, schedule risk, and generates CUSPAP-style location overview narratives for appraisal reports.
npx claudepluginhub reggiechan74/vp-real-estate --plugin infrastructure-corridor-opsHow this skill is triggered — by the user, by Claude, or both
Slash command
/infrastructure-corridor-ops:right-of-way-expertThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill bundles three workflows for linear-infrastructure right-of-way work. Route by task:
README_UTILITY_CONFLICT_ANALYZER.mdeasement_valuation_calculator.pylocation-overview-playbook.mdmodules/__init__.pymodules/conflict_detection.pymodules/cost_estimation.pymodules/output_formatters.pymodules/relocation_design.pymodules/validators.pysamples/pipeline_corridor_input.jsonsamples/transit_station_input.jsonscripts/Location_Overview/README.mdscripts/Location_Overview/__init__.pyscripts/Location_Overview/aggregator/__init__.pyscripts/Location_Overview/aggregator/engine.pyscripts/Location_Overview/aggregator/merger.pyscripts/Location_Overview/aggregator/validator.pyscripts/Location_Overview/config.pyscripts/Location_Overview/geocoding/__init__.pyscripts/Location_Overview/geocoding/cache.pyPlans multi-parcel land assembly for transit corridors, highways, transmission lines, pipelines, or mixed-use developments. Scores acquisition priorities, models phasing strategy and holdout risk, builds budgets with contingencies, and quantifies cost of delay.
Conducts multi-scale site analysis from regional to site level for urban design and architecture projects. Generates structured reports on physical context, infrastructure, demographics, environment, regulations, and design opportunities/constraints.
Parses Ontario Land Titles reports, classifies encumbrances (easements, covenants, liens), detects registration defects, and quantifies marketability discounts during acquisition due diligence.
Share bugs, ideas, or general feedback.
This skill bundles three workflows for linear-infrastructure right-of-way work. Route by task:
| If you need to... | Go to section |
|---|---|
| Identify and resolve utility conflicts in a proposed ROW corridor, design relocations, estimate costs and schedule risk | Utility Conflict Analysis Framework |
| Generate a CUSPAP-style location overview narrative from an address or PIN for an appraisal report | Location Overview Generator |
| Value a permanent or temporary easement (percentage-of-fee, income capitalization, before/after, paired sales) | Use the standalone easement-valuation-methods skill in the appraisal-valuation plugin — it carries the calculators and the USPAP/CUSPAP/Yellow Book/IVS compliance framework |
ROW is the legal corridor needed for infrastructure operation and maintenance. Specifications vary by infrastructure type:
Transmission Lines (Hydro):
Pipelines:
Transit Corridors:
Six-phase workflow. Detailed examples, cost tables, coordination scripts, risk matrices, and best-practice expansions live in utility-conflict-playbook.md — load it whenever you need the worked examples or the cost numbers, not the skeleton.
| Conflict Type | Priority | Relocation | Timeline | Cost Impact |
|---|---|---|---|---|
| Direct conflict (in ROW) | CRITICAL | Mandatory | Months 0-3 | High |
| High risk (<5m) | HIGH | Likely | Months 1-4 | Medium-High |
| Medium risk (5-15m) | MEDIUM | Possible | Months 2-6 | Medium |
| Low risk (>15m) | LOW | Unlikely | Months 3-12 | Low |
| Overhead crossing | MEDIUM | Coordination | Months 2-5 | Medium |
| Underground crossing | HIGH | Design | Months 1-6 | Medium-High |
Canonical example (115kV transmission corridor, 45m width): a gas pipeline 8m from the ROW edge is HIGH RISK (requires relocation or increased clearance); a telecom cable 3m from the centerline is a DIRECT CONFLICT (mandatory relocation); a water main 12m out is MEDIUM (coordination required); a fiber line 25m out is LOW (standard notification). See playbook for the LRT vertical-conflict example and full locate-request procedure.
Each utility class has standard design options. Pick by cost, schedule, and constraint fit:
Full pros/cons and per-option detail in the playbook.
Order-of-magnitude per-km ranges (see playbook for full pressure/voltage/diameter tables and cost-component breakdowns):
| Utility | Base range per km |
|---|---|
| Transmission line (overhead, by voltage) | $600K-$3M |
| Transmission line (underground burial) | $2.5M-$10M |
| Gas pipeline (by pressure class & method) | $200K-$1.8M |
| Telecom cable (route option dependent) | $150K-$1.6M total |
| Water main (by diameter) | $250-$1000/m |
| Sewer main (gravity or pressure) | $200-$800/m |
Typical multi-utility corridor sequence:
Month 0-3: Utility ID & design (locates → meetings → relocation design → permits)
Month 3-6: Easements & regulatory approvals (ROW, environmental, municipal, Utility Commission)
Month 6-12: Utility relocation execution (transmission on critical path; gas/water/sewer/telecom in parallel)
Month 12+: Main project construction begins
Critical path items and delay risk:
Full Gantt-style breakdown and dependency chain in the playbook.
Each operator has its own stakeholder map, meeting cadence, document set, and cost allocation convention:
Detailed cadence and document checklists for each operator in the playbook.
Track schedule and budget risk on a structured register. Highest-impact items:
Full schedule risk table, budget risk table, specific-component escalation breakdowns, and the five mitigation strategies (early engagement, multiple options, geotech, regulatory pre-coordination, contingency planning) are in the playbook.
The /right-of-way-analysis slash command integrates conflict detection with cost estimation. See the playbook for invocation patterns and a complete sample input JSON file.
Generates a location overview for an Ontario property given a PIN (9 digits) or municipal address. Orchestrates geocoding, queries provincial/municipal/heritage/brownfield/TRCA/GTFS/census providers, and produces a consolidated markdown or JSON report — useful for scoping ROW conflicts, heritage constraints, and environmental flags before detailed conflict analysis.
Run location overview:
cd ${CLAUDE_PLUGIN_ROOT}/skills/right-of-way-expert/scripts
python3 -m Location_Overview.main "100 Queen Street West, Toronto"
python3 -m Location_Overview.main --format json "150 King Street West, Toronto"
python3 -m Location_Overview.main --no-save "123 Main Street, Mississauga"
CLI flags:
input (positional) — PIN (9 digits) or municipal address--format / -f — markdown (default) or json--no-save — print only, do not save--verbose / -v — verbose loggingThe Python script handles Phase 1 (API data collection). Phases 2 and 3 are performed in-conversation by the model after reading the script output.
123456789 or 12345-6789) vs. address; geocode and resolve municipality; query Nominatim, Ontario GeoHub, Toronto/Ottawa Open Data, Overpass API, Heritage Registry, Brownfields ESR, TRCA Conservation, Transit GTFS, Census Demographics; emit consolidated markdown or JSON.WebSearch and WebFetch across five domains: Municipal Planning, Heritage, Environmental, Development Activity, Market Context. Full query templates and municipality-specific anchor domains in location-overview-playbook.md.The narrative must follow CUSPAP location description conventions and cover all ten sections in order: (1) Property Identification, (2) Regional Context, (3) Neighbourhood Description, (4) Transportation & Accessibility, (5) Amenities & Services, (6) Planning Framework, (7) Development Activity, (8) Environmental Considerations, (9) Market Context, (10) Conclusion.
Full paragraph counts, content checklists, and CUSPAP-specific guidance per section are in the playbook.
Save the final narrative to:
$CLAUDE_PROJECT_DIR/Reports/YYYY-MM-DD_HHMMSS_location_overview_narrative_[address_slug].md
Present to the user: the full narrative text in chat, the saved file path, the list of data sources used (API + web), and verification recommendations for any uncertain items.
Full expansions, key questions per utility, sample contingency stack, and deliverables checklist in utility-conflict-playbook.md.
expropriation-timeline-expert (expropriation-law) — critical-path scheduling with utility relocation integrationland-assembly-expert (this plugin) — multi-parcel acquisition phasingeasement-valuation-methods (appraisal-valuation) — compensation valuation when an easement is taken