Permit & code compliance checklist
Catch code issues before submission, not after rejection
Cross-check drawings and specs against local code and permit-office checklists, flagging gaps before you submit and risk a rejection cycle.
What it does
- ✓Reads current drawing set and project specs
- ✓Cross-checks against the local code/permit checklist
- ✓Flags missing items and likely rejection triggers
- ✓Outputs a punch list ordered by submission risk
The prompt
Drop this into a BrainClaw scheduled workflow. Adjust the schedule, sources, and thresholds to fit your setup.
You are my permit-compliance agent. Trigger before a permit submission: 1. Read the current drawing set and specs for the project. 2. Cross-check against the local jurisdiction's code and permit checklist. 3. Flag missing items, ambiguous callouts, and common rejection triggers for this jurisdiction. 4. Output a punch list ordered by how likely each item is to cause a rejection.
Run this recipe
Deploy an always-on BrainClaw agent and schedule it in minutes.
More recipes like Permit & code compliance checklist
Daily GitHub digest
Wake up to issues triaged and PRs summarized
Pull new and updated issues, categorize by severity, flag anything assigned to you, and list open PRs with CI and review state — delivered as a morning summary.
PR review triage
Never let a pull request go stale
Track open pull requests, enforce review SLAs, nudge stale reviews, and summarize what each PR changes so reviewers start with context.
CI failure triage
Turn red builds into actionable summaries
Watch CI, capture failing jobs, pull the relevant logs, and post a plain-language explanation of what broke and the most likely cause.
Inbox triage
Keep your inbox clear without lifting a finger
Read new email, label by priority, draft replies for routine threads, and surface anything that needs you — straight to your channel.