egress-life-safety
Skill0 starsChanged 3 months agoMITView on GitHub
Computes means-of-egress requirements — occupant loads, exit capacity, travel distance, stairs and ramps — for floor plans and buildings. Use when checking egress on a plan, sizing exits and corridors, reviewing exit signage/lit stairs, or preparing a life-safety plan sheet.
In this repository7 other files it gives its agents.
- bim-interoperabilitySkill
- building-code-reviewSkill
- dxf-drawing-inspectionSkill
- ifc-model-analysisSkill
- mep-coordinationSkill
- specification-writingSkill
- sustainable-designSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 52
Do not rely on memory for exact tables: Always give the Table/Section reference and the exact number read from the current adopted edition.
- Distinctive: line 55
Elevators are not exits: If the design relies on them for egress, flag it.
- Distinctive: line 57
Dead-end corridors: must not exceed the code dead-end max (commonly 20 ft unsprinklered / 50 ft sprinklered) — verify.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Egress & Life Safety
Compute and check the means-of-egress for a building or space: occupant load, number of exits, corridor/stair widths, travel distance, and exit layout. Eg egress design is governed by IBC Ch. 10 and NFPA 101 (adopted editions vary).
When to use
- Sizing the number and width of exits for a given program
- Checking that a floor plan's corridor, door, and stair dimensions comply
- Computing occupant load for a room or an assembly space
- Reviewing exit signs, egress lighting, and discharge path
Workflow
- Confirm edition & sprinkler status — they change nearly every limit below.
- Occupancy classification → occupant load factor (IBC Table 1004.5). For mixed programs, compute per space and use the governing (largest) load.
- Occupant load per space:
area (ft²) ÷ load factor. Round up. Sum for the floor; the code's smaller-scale rules don't reduce the sum. - Number of exits (IBC §1006): 1 exit allowed only under strict low-occupant + low-travel cases listed in Table 1006.3.2; otherwise 2, then 3/4 by occupant ranges. Provide the minimum required, not necessarily the design intent.
- Exit/exit access width: corridor min 44" (some occupancies/loads require 72" when >50 occupants — verify). Exit door clear width min 32". Stairs min 44" clear.
- Travel distance: max from any occupied point to the exit (Table 1017.2). Sprinklered business: 300 ft; unsprinklered: 200 ft. Verify per occupancy.
- Common path of egress travel (Table 1006.3.2) — the distance to a point where two means of egress become available.
- Egress capacity check: width-based capacity = width (in inches) ÷ the per-occupant inches factor (e.g. 0.2"/person stairs, 0.3"/person doors/ramps — IBC §1005).
capacity ≥ occupant loadmust hold at each exit component. - Assembly spaces (Ch. 10 additional): fixed seating occupant load by seat, aisle widths, exit capacity factoring 1:2, 2:3, etc.
- Discharge: exits must discharge to a public way or an open space with safe passage; check the discharge path total capacity.
Output
Present a short table:
| Item | Requirement | Design | Verdict |
| Occupant load L1 | 120 | 132 | OK (computed) |
| No. of exits | 2 | 2 | OK |
| Corridor width | ≥44" | 66" | OK |
| Corridor capacity | 66/0.3=220 ≥ 132 | — | OK |
| Exit door clear | ≥32" | 34" | OK |
| Travel distance | ≤300' (sprinklered B) | 185' | OK |
| Common path | ≤100' | 48' | OK |
List any FAIL/verify items with the code section and a proposed fix.
Edge cases & cautions
- Do not rely on memory for exact tables. Always give the Table/Section reference and the exact number read from the current adopted edition; note the edition. If you cannot verify a number, say so.
- Assembly without fixed seats: occupant load uses the concentrated load factor and exit capacity is stricter (assembly flow).
- Unusual occupancy spans: a corridor serving assembly + business has the assembly rules apply.
- Elevators are not exits. If the design relies on them for egress, flag it.
- Revolving doors, security gates: restricted in path of egress; check that swinging doors open in direction of egress travel for >50 occupants.
- Dead-end corridors must not exceed the code dead-end max (commonly 20 ft unsprinklered / 50 ft sprinklered) — verify.
- High-rise: exit stairs need to be pressurized, exit enclosures, and possibly exit discharge through a protected path — treat as its own review.
Files
references/egress-cheatsheet.md— the constants and tables (occupant load factors, widths, travel distances, capacity factors) with IBC/NFPA references.scripts/egress_calc.py— computes occupant load, required exit count, and corridor/stair capacity from basic inputs.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

