Permit Navigator Skill
Permits are where good projects hit a wall: people renovate, then get a stop-work
order; open a business, then find they were operating unlicensed; plan an event, then
learn the road-closure permit needed 90 days' notice. The rules are hyper-local
(city, county, sometimes your specific zone) and this skill will not pretend to know
your jurisdiction's code — its job is to tell you which kinds of permits a project
like yours usually needs, the order they go in (some can't start until others are
issued), and exactly which office to call to confirm, so you sequence the paperwork
before the work.
What This Skill Produces
- A permit checklist: the permits a project like this typically needs, each
marked likely required / maybe / probably not — to confirm, not to rely on
- The sequence and dependencies: what must be approved before what (zoning before
building, building before occupancy), so you don't apply out of order
- The who-to-ask map: which office/department owns each permit and the question
to ask them ("does a project like X need Y here?")
- A timeline reality check: which permits have long lead times or public-notice
periods, so the project plan accounts for them instead of being ambushed
Required Inputs
Ask for (if not already provided):
- The project: what, where (city/region — rules are local), and scale
- Type: building/renovation, opening/running a business, an event, signage, a home
business, short-term letting, etc.
- Property context: own or rent, residential/commercial, historic district or HOA
(these add layers), and whether any work has started
- The deadline driving it (an event date, a lease start) so lead times can be flagged
Framework
- Classify the project — it determines the permit family. Renovation vs new
build vs change-of-use vs event vs business-license are different worlds. Nail the
category first; everything else follows from it.
- List the likely permits, honestly hedged. For the category, name the permits
commonly involved (e.g. renovation often: building, electrical, plumbing,
sometimes zoning/planning) — each labeled by likelihood and flagged "confirm with
[office]." Never assert "you need X" as fact about a specific jurisdiction.
- Order by dependency. Many permits gate each other: zoning/planning approval
before a building permit; building sign-offs before an occupancy permit; a food
license needs a passed health inspection. Draw the sequence so nothing is applied
for before its prerequisite exists.
- Flag the long poles. Public-notice periods, historic/heritage review,
variance/exception requests, environmental review, and event road-closures can take
weeks-to-months. Surface these against the deadline early — they're the usual cause
of a blown timeline.
- Route to the authority for the real answer. The permit office / planning
department / licensing authority is the source of truth. The most valuable move is
often a single scoping call: "here's my project — which permits does it need?"
The skill prepares that call and the checklist to bring to it.
Output Format
## The project, classified
[Category · location · scale · anything already started (may need retroactive fixes)]
## Likely permits (confirm each — do not rely on this list)
| Permit | Likelihood | Office that owns it | The question to ask them |
## The order to do them
[Dependency sequence — what gates what]
## Long lead times to plan around
[Notice periods, reviews, inspections — against your deadline]
## Your first call
[The scoping question to the permit office, and what to have ready]
⚠ Local code governs; this orients you and routes you to the authority. It is not a
substitute for the permit office or, for complex projects, an architect/expediter/lawyer.
Quality Checks
Anti-Patterns
Related
[[trade-quote-builder]] and [[stage-payment-shield]] for the tradespeople doing the
work; [[speak-at-the-council]] if the project needs a hearing; [[report-a-hazard]] for
the other side of local government.
Example Trigger Phrases
- "Do I need a permit for this?"
- "What permits for my renovation/business/event?"
- "Help me apply for a permit."
1---2name: permit-navigator3description: "Work out which permits a project actually needs and the order to get them — building/renovation, business licensing, events, signage, home businesses — so you don't build first and discover the permit later. Use when someone says 'do I need a permit for this', 'what permits for my renovation/business/event', 'help me apply for a permit', or 'the council flagged my project'. Produces a permit checklist with the likely permits, their sequence and dependencies, and the official offices to confirm each. Not legal/code advice — it orients and routes to the authority."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/permit-navigator7---89# Permit Navigator Skill1011Permits are where good projects hit a wall: people renovate, then get a stop-work12order; open a business, then find they were operating unlicensed; plan an event, then13learn the road-closure permit needed 90 days' notice. The rules are hyper-local14(city, county, sometimes your specific zone) and this skill will not pretend to know15your jurisdiction's code — its job is to tell you *which kinds of permits a project16like yours usually needs*, the order they go in (some can't start until others are17issued), and exactly which office to call to confirm, so you sequence the paperwork18before the work.1920## What This Skill Produces2122- A **permit checklist**: the permits a project like this typically needs, each23 marked *likely required / maybe / probably not* — to confirm, not to rely on24- The **sequence and dependencies**: what must be approved before what (zoning before25 building, building before occupancy), so you don't apply out of order26- The **who-to-ask map**: which office/department owns each permit and the question27 to ask them ("does a project like X need Y here?")28- A **timeline reality check**: which permits have long lead times or public-notice29 periods, so the project plan accounts for them instead of being ambushed3031## Required Inputs3233Ask for (if not already provided):34- The project: what, where (city/region — rules are local), and scale35- Type: building/renovation, opening/running a business, an event, signage, a home36 business, short-term letting, etc.37- Property context: own or rent, residential/commercial, historic district or HOA38 (these add layers), and whether any work has started39- The deadline driving it (an event date, a lease start) so lead times can be flagged4041## Framework42431. **Classify the project — it determines the permit family.** Renovation vs new44 build vs change-of-use vs event vs business-license are different worlds. Nail the45 category first; everything else follows from it.462. **List the likely permits, honestly hedged.** For the category, name the permits47 commonly involved (e.g. renovation often: building, electrical, plumbing,48 sometimes zoning/planning) — each labeled by likelihood and flagged "confirm with49 [office]." Never assert "you need X" as fact about a specific jurisdiction.503. **Order by dependency.** Many permits gate each other: zoning/planning approval51 before a building permit; building sign-offs before an occupancy permit; a food52 license needs a passed health inspection. Draw the sequence so nothing is applied53 for before its prerequisite exists.544. **Flag the long poles.** Public-notice periods, historic/heritage review,55 variance/exception requests, environmental review, and event road-closures can take56 weeks-to-months. Surface these against the deadline early — they're the usual cause57 of a blown timeline.585. **Route to the authority for the real answer.** The permit office / planning59 department / licensing authority is the source of truth. The most valuable move is60 often a single scoping call: "here's my project — which permits does it need?"61 The skill prepares that call and the checklist to bring to it.6263## Output Format6465```66## The project, classified67[Category · location · scale · anything already started (may need retroactive fixes)]6869## Likely permits (confirm each — do not rely on this list)70| Permit | Likelihood | Office that owns it | The question to ask them |7172## The order to do them73[Dependency sequence — what gates what]7475## Long lead times to plan around76[Notice periods, reviews, inspections — against your deadline]7778## Your first call79[The scoping question to the permit office, and what to have ready]8081⚠ Local code governs; this orients you and routes you to the authority. It is not a82substitute for the permit office or, for complex projects, an architect/expediter/lawyer.83```8485## Quality Checks8687- [ ] Every permit is hedged by likelihood and routed to a named office to confirm —88 nothing asserted as certain for the jurisdiction89- [ ] The dependency sequence is explicit (what must precede what)90- [ ] Long-lead / notice-period permits are flagged against the stated deadline91- [ ] Work-already-started is handled (retroactive permits, stop-work risk) if relevant92- [ ] The output ends with a concrete scoping call to the authority9394## Anti-Patterns9596- [ ] Do not assert a specific jurisdiction's permit requirements or code as fact —97 they're local and change; orient and route to the office98- [ ] Do not give code, structural, or legal advice — flag when an architect,99 engineer, expediter, or lawyer is the right call100- [ ] Do not present the permit list as complete or authoritative — it's a starting101 checklist to confirm102- [ ] Do not skip the sequencing — an out-of-order application is the classic wasted103 month104- [ ] Do not encourage skipping permits or "asking forgiveness" — unpermitted work105 creates real liability and resale problems; say so106107## Related108109[[trade-quote-builder]] and [[stage-payment-shield]] for the tradespeople doing the110work; [[speak-at-the-council]] if the project needs a hearing; [[report-a-hazard]] for111the other side of local government.112113## Example Trigger Phrases114115- "Do I need a permit for this?"116- "What permits for my renovation/business/event?"117- "Help me apply for a permit."