Update to Argovance Skill OS

{
  "description": "Build a jurisdiction- and project-specific checklist of potential property permissions, consultations, submissions, inspections, certificates, dependencies, and evidence to verify. Use for permit and compliance planning. Do not determine that approval is or is not required, interpret law conclusively, submit applications, or certify compliance.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 257
    }
  ],
  "name": "build-property-permit-checklists",
  "skill_md_contents": "---\nname: build-property-permit-checklists\ndescription: Build a jurisdiction- and project-specific checklist of potential property permissions, consultations, submissions, inspections, certificates, dependencies, and evidence to verify. Use for permit and compliance planning. Do not determine that approval is or is not required, interpret law conclusively, submit applications, or certify compliance.\n---\n\n# Property Permit and Compliance Checklist Builder\n\n## Workflow\n\n1. Define exact jurisdiction, authority, property, current and proposed use, works, occupancy, tenure, protected status, site constraints, and project stage.\n2. Research current official authority and statutory sources; record access date, effective date, scope, and unresolved interpretation.\n3. Build a verification matrix for planning or zoning, building control or code, fire, accessibility, heritage, environmental or habitat, demolition, trees, highways, parking, utilities, drainage, signage, licensing, occupancy, energy, and inspections as applicable.\n4. Identify prerequisite surveys, drawings, calculations, ownership consents, notices, consultations, fees, lead times, conditions, expiry, inspections, and completion evidence.\n5. Separate confirmed requirement, likely applicability requiring confirmation, not applicable with evidence, and unknown.\n6. Route legal interpretation and design compliance to qualified local professionals or authorities; do not treat the checklist as permission to proceed.\n\n## Required output\n\n- Project and jurisdiction scope\n- Permission and evidence matrix\n- Authority and professional contacts to verify\n- Dependency and submission sequence\n- Decision deadlines and expiry risks\n- Unknowns and no-work gates\n\n"
}