| name | buildability-analysis |
| version | 1.0 |
| description | Evaluates a proposed project concept against normalized Ontario parcel, zoning, Official Plan, and overlay data. This skill should be used when `normalized_data.json` and a project concept are available and the pipeline needs an `analysis_packet.json` with verdict, pathway signal, planning-context summary, and explicit facts, inferences, assumptions, and unknowns. |
| source | Toronto Zoning By-law 569-2013, Toronto Official Plan, O.Reg 462/24, Ontario Building Code |
| authority | City of Toronto, Province of Ontario |
| data_as_of | 2026-03-07 |
| pipeline_position | 3 |
| pipeline_inputs | normalized_data.json |
| pipeline_outputs | analysis_packet.json |
| pipeline_upstream | parcel-zoning-research |
| pipeline_downstream | constraints-red-flags, approval-pathway, report-generator |
Buildability Analysis
Purpose
Turn normalized policy facts into a conservative feasibility assessment. Use only the fields already extracted into normalized_data.json plus narrowly scoped planning-context research where required. Do not restate the entire source record.
Use when
normalized_data.json exists- The project concept is defined well enough to compare against policy controls
- The next step needs an
analysis_packet.json
Do not use when
- Parcel or zoning facts are still unresolved
- The task is to discover sources or extract raw by-law text
- The task is to write the final human-facing report
Inputs
{
"project_id": "uuid",
"normalized_data_path": "normalized_data.json",
"project_concept": {
"project_type": "multiplex",
"proposed_units": 4,
"proposed_height_m": 10,
"proposed_gfa_m2": 320,
"proposed_lot_coverage_pct": 45
}
}
Outputs
Produce analysis_packet.json.
{
"project_id":
