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 |
assets/checklist-template.md
View on GitHub# Drawing Checklist — {{PHASE}} / {{DISCIPLINE}} / {{PROJECT_TYPE}}
**Project:** {{PROJECT_NAME}}
**Phase:** {{PHASE}} ({{PERCENT_COMPLETE}})
**Discipline:** {{DISCIPLINE}} (primary)
**Project type:** {{PROJECT_TYPE}}
**Date:** {{DATE}}
**Reviewed by:** {{REVIEWER}}
---
> **Disclaimer.** Items below are practice-guide-level expectations, **not contract requirements** unless explicitly tied to a B101 / NCS / firm-standard citation. Annotate each row with a `Source authority` (AIA B101-2017 §X.X, NCS v6 Module 2, firm CAD/BIM standard, project BIM execution plan, or "office convention") so the team knows which items are negotiable and which are contractual. Phase percent-complete values are office convention, not AIA-mandated. Project contract language (B101, B102, custom owner-architect agreement) overrides this checklist.
---
## Phase intent
{{PHASE_INTENT}}
_Source authority: AIA B101-2017 §3.X — confirm exact section against project contract._
---
## Required sheets at this phase
_Source authority: sheet-series naming per NCS v6 Module 2 (Uniform Drawing System). Per-phase content expectations are common practice — verify against firm CAD/BIM standard and project BIM execution plan. Annotate each row with the governing source (`NCS v6`, `firm standard`, `BIM execution plan`, or `office convention`)._
### G-series — General
- [ ] G-000 Cover — {{G000_REQS}} _(Source: ____)_
- [ ] G-001 Code summary / Life safety — {{G001_REQS}} _(Source: IBC §___ + ____)_
- [ ] G-002 Sheet index, symbols, abbreviations — {{G002_REQS}} _(Source: NCS v6 Module 2)_
### A-0xx — Site
- [ ] A-001 Site plan — {{A001_REQS}} _(Source: ____)_
### A-1xx — Floor plans
- [ ] {{A100_REQS}} _(Source: ____)_
### A-2xx — Reflected ceiling plans
- [ ] {{A200_REQS}} _(Source: ____)_
### A-3xx — Exterior elevations
- [ ] {{A300_REQS}} _(Source: ____)_
### A-4xx — Building sections
- [ ] {{A400_REQS}} _(Source: ____)_
### A-5xx — Wall sections
- [ ] {{A500_REQS}} _(Source: ____)_
### A-6xx — Enlarged plans
- [ ] {{A600_REQS}} _(Source: ____)_
### A-7xx — Schedules
- [ ] {{A700_REQS}} _(Source: ____)_
### A-8xx — Details
- [ ] {{A800_REQS}} _(Source: ____)_
### A-9xx — Interior elevations
- [ ] {{A900_REQS}} _(Source: ____)_
---
## Level-of-detail checks
_Source authority: common-practice synthesis aligned with AIA B101-2017 §3.2 / §3.3 / §3.4 phase scopes. Specific LOD thresholds (single-line vs double-line walls, dimension granularity) are office convention; verify against firm standard or project BIM execution plan (LOD 100/200/300/350/400 per BIMForum)._
- [ ] Wall depiction matches phase ({{WALL_DEPICTION}}) _(Source: office convention / firm standard)_
- [ ] Dimensions present at required level ({{DIMENSION_LEVEL}}) _(Source: office convention / firm standard)_
- [ ] Schedules at required completeness ({{SCHEDULE_LEVEL}}) _(Source: office convention / firm standard)_
- [ ] Details at required completeness ({{DETAIL_LEVEL}}) _(Source: office convention / firm standard)_
---
## Common missing items
_Source authority: common-practice QA/QC items synthesized from AIA Best Practices and firm QA standards. Not a single published checklist._
- [ ] North arrow present and consistent on every plan _(Source: NCS v6 / firm QA)_
- [ ] Key plan on multi-sheet floor plans _(Source: NCS v6 Module 2)_
- [ ] Match lines align between adjacent sheets _(Source: NCS v6 Module 2)_
- [ ] Column grid extends to plan edges _(Source: firm QA / office convention)_
- [ ] All callouts (detail bubbles, section cuts, elevation tags) reference an existing sheet _(Source: NCS v6 Module 2)_
- [ ] All tags (door, window, partition, room) match the schedule _(Source: firm QA)_
- [ ] Section cut directions on plan match the drawn section view _(Source: firm QA)_
- [ ] {{ADDITIONAL_MISSING_ITEMS}} _(Source: ____)_
---
## Cross-discipline coordination flags
_Source authority: synthesis of common AEC coordination touchpoints — AIA Best Practices, AISC 303, ASHRAE HVAC design guides, MEP coordination guides. **Not a published checklist from a single authority.** Annotate each row with the governing source and supplement with project-specific coordination matrix from the BIM execution plan._
### Architectural ↔ Structural
- [ ] {{ARCH_STRUCT_1}} _(Source: ____)_
- [ ] {{ARCH_STRUCT_2}} _(Source: ____)_
- [ ] {{ARCH_STRUCT_3}} _(Source: ____)_
### Architectural ↔ MEP
- [ ] {{ARCH_MEP_1}} _(Source: ____)_
- [ ] {{ARCH_MEP_2}} _(Source: ____)_
- [ ] {{ARCH_MEP_3}} _(Source: ____)_
---
## Title block / sheet hygiene
_Source authority: NCS v6 Module 2 (sheet identification, title-block organization) + AIA G-series administrative documents (G701 Change Order, G710 ASI) for revision conventions. Specific items are common-practice synthesis._
- [ ] Title block fields populated on every sheet (project, address, sheet name, number, scale, date) _(Source: NCS v6 Module 2)_
- [ ] Sheet numbering complete — no gaps, no duplicates _(Source: NCS v6 Module 2)_
- [ ] Revision block updated with current revision date and description _(Source: NCS v6 Module 2 / AIA G-series)_
- [ ] Revision clouds + delta tags on every changed item (DD onward) _(Source: office convention / firm QA)_
- [ ] Phase stamp matches the issue ({{PHASE_STAMP}}) _(Source: office convention)_
- [ ] Seal/signature block ready (CD/IFC) _(Source: state licensing board / AHJ requirement)_
---
## Phase-specific deliverable expectations
{{DELIVERABLE_EXPECTATIONS}}
_Source authority: AIA B101-2017 §3.X (project contract phase scope). Specific deliverable lists are common-practice synthesis — verify against project owner-architect agreement._
---
## Highest-risk items for this set
1. {{RISK_1}}
2. {{RISK_2}}
3. {{RISK_3}}
---
## Notes
{{NOTES}}
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 |