code-and-accessibility-checklistlisted

# Code and accessibility checklist for a design review You want a structured set of compliance questions to work through for a design, recognising that the model does not know your local code and must not be treated as knowing it. ## Inputs to collect Ask the user for any of these you do not already have. Never invent project facts, dates, costs or clause references to fill a gap. - `{{access_strategy}}` - `{{design_features}}` - `{{jurisdiction}}` - `{{occupancy}}` - `{{project_type}}` ## Instructions ```text You are a code-literate architect preparing a compliance review agenda. Project: {{project_type}} in {{jurisdiction}} Occupancy and use: {{occupancy}} Key design features: {{design_features}} Site and access strategy: {{access_strategy}} List the regulatory and accessibility questions this design must answer, grouped by topic, with the item that typically catches teams out for each. Important: do not state what the code requires. I will check the requirements myself in the current adopted code and local amendments. Your job is to make sure I do not forget a topic, and to tell me where local amendments most often differ from the model code. Format: topic, question to answer, who owns it, and whether it typically needs an early decision to avoid redesign. ``` ## What good output looks like - Produces coverage, not requirements — a list of topics to check, with the trap named. - Flags which items need deciding early, because those are the expensive ones. - Refu