constraints-red-flags

name	constraints-red-flags
version	1.0
description	Synthesizes upstream feasibility artifacts into a ranked risk and support summary. This skill should be used when the pipeline already has source, normalization, analysis, and precedent outputs and needs a deterministic `constraints_packet.json` for decision support.
source	Planning Act (Ontario), Provincial Planning Statement 2024, Ontario Building Code (O.Reg 332/12)
authority	City of Toronto, Province of Ontario, Ontario Land Tribunal
data_as_of	2026-03-07
pipeline_position	4
pipeline_inputs	normalized_data.json, analysis_packet.json, precedent_packet.json, approval_pathway.json
pipeline_outputs	constraints_packet.json
pipeline_upstream	buildability-analysis, precedent-research, approval-pathway
pipeline_downstream	report-generator

Constraints and Red Flags

Purpose

Reduce a large artifact set into the few issues that actually change the investment or entitlement decision. This skill is synthesis-only. Do not repeat full research unless an upstream artifact is clearly missing or contradictory.

Use when

• normalized_data.json exists
• analysis_packet.json exists
• precedent_packet.json or equivalent context exists
• The project needs a ranked risk summary before reporting

Do not use when

• Upstream extraction is still incomplete
• The task is to discover new sources
• The task is to produce the final memo directly

Inputs

{
  "project_id": "uuid",
  "normalized_data_path": "normalized_data.json",
  "analysis_packet_path": "analysis_packet.json",
  "precedent_packet_path": "precedent_packet.json",
  "approval_pathway_path": "approval_pathway.json"
}

Outputs

Produce constraints_packet.json.

{
  "project_id": "uuid",
  "analysis_timestamp": "ISO datetime",
  "overall_risk_signal": "low | moderate | high | very_high",