DavidCho1999/archaiflow-skills / bundles/construction-admin/skills/drawing-checklist
drawing-checklist
VerifiedThis skill should be used when the user needs a phase-specific drawing-set checklist for an architectural project — SD, DD, CD, or IFC. Trigger on 'make a checklist', 'drawing set review', 'CD checklist', 'DD set review', or pasted phase + project-type context. Generates a structured checklist markdown in `docs/checklists/` and updates the project checklist index.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.4 KB |
| assets/checklist-template.md | markdown | 5.7 KB |
| references/_provenance.md | markdown | 7.0 KB |
| references/coordination_flags.md | markdown | 4.6 KB |
| references/phase_deliverables.md | markdown | 7.5 KB |
| references/sheet_types.md | markdown | 7.9 KB |
| scripts/append_to_index.py | script | 1.6 KB |
| scripts/init_checklist_workspace.py | script | 773 B |
references/coordination_flags.md
View on GitHub# Coordination Flags
Common architectural-to-structural and architectural-to-MEP coordination items. Use as a checklist of interfaces to verify before issuing a set.
> **Provenance note.** This 100-item coordination list is a synthesis of common AEC coordination touchpoints — sourced from architectural / structural / MEP coordination practice (AIA Best Practices, AISC 303 Code of Standard Practice for Steel Buildings and Bridges, ASHRAE HVAC Design Guides, MEP coordination guides, NCS v6). It is **not** a published checklist from a single authority. Use as a starting point; supplement with the project-specific coordination matrix from the BIM execution plan and any firm QA/QC checklists. See `_provenance.md` for source authorities and verification status.
---
## Architectural ↔ Structural
### Grid alignment
- Architectural column locations match structural grid on every plan
- Grid letters/numbers identical across A and S sheets
- Grid extends to plan edges on architectural sheets
- Column sizes shown on architectural plans match structural sizing (DD onward)
### Floor-to-floor and structural depth
- Floor-to-floor dimensions match between A sections and S framing plans
- Structural depth zone (joist + slab + topping) accommodates ceiling plenum + MEP
- Slab depressions for wet areas, terraces, and equipment shown on both A and S
- Slab edge conditions at perimeter walls coordinated (overhang, recess, flush)
### Openings in structure
- Slab openings for stairs, elevators, shafts, and skylights match between A and S
- Beam penetrations for ducts/pipes flagged on A and confirmed structurally feasible
- Wall openings in shear walls and load-bearing walls reviewed by structural
### Roof and parapet
- Parapet height and structural backup coordinated (especially at tall parapets)
- Roof equipment loads transferred to structural
- Expansion joints aligned between A and S
### Foundations and below-grade
- Building footprint matches foundation extents
- Basement wall thickness coordinated with site retaining strategy
- Elevator pit and sump locations coordinated
---
## Architectural ↔ MEP
### Ceiling plenum
- Plenum depth in A sections accommodates the deepest MEP run
- Soffit/bulkhead locations on RCP align with mechanical duct routing
- Ceiling height tags consistent between A RCP and M layout
### Shafts and chases
- Vertical shafts (mechanical, electrical, plumbing, exhaust) sized for routing on every floor
- Chase locations consistent floor-to-floor on architectural plans
- Wall thickness around chases accommodates rated construction where required
### Equipment locations
- Mechanical room sizes confirmed against equipment list and service clearances
- Electrical room locations and sizes confirmed against gear list
- Roof equipment (RTUs, condensers, exhaust fans) located on A roof plan and M plan, with screening if required
- Floor drains coordinated with plumbing layout and slab slope
### Penetrations
- Roof penetrations (vents, exhausts, plumbing stacks, conduit) shown on A roof plan
- Wall penetrations through rated assemblies flagged for firestopping
- Slab penetrations coordinated with structural
### RCP fixtures
- Diffusers, returns, sprinklers, lights, speakers, sensors, smoke detectors all located on RCP
- Fixture-to-fixture clearances respected
- Access panels located for equipment requiring service
### Plumbing fixtures
- Fixture counts on A schedules match P schedules
- Fixture locations on enlarged plans align with P rough-in
- Accessibility clearances at fixtures verified
### Electrical
- Switch locations on A plans match E plans
- Receptacle locations match E plans (or "by E" noted clearly)
- Panel locations and clearances coordinated with A
---
## Common conflicts to flag explicitly
- Ceiling height too low for MEP plenum at corridors and back-of-house
- Beam depth at exterior bay conflicts with window head height
- Mechanical shaft moves between floors and breaks vertical alignment
- RTU on roof lands over a column-free interior space (no support)
- Plumbing wall thickness insufficient for stacks at residential bathrooms
- Electrical panel located in a finished public area
- Sprinkler heads conflict with linear lighting in RCP
- Floor drain locations don't align with slab slope direction
---
## When to raise
- **SD:** strategy-level only — major shaft locations, structural grid, mechanical room footprint
- **DD:** every interface above should be reviewed and documented in coordination meetings
- **CD:** every conflict resolved or formally accepted; clash detection complete if BIM
- **IFC:** zero outstanding conflicts; any remaining items become RFIs after issue
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |