Drawing Standards Audit
Sweep a set for the conventions that make it readable, not for what it shows
Once installed, Claude loads it on its own when your conversation matches. You can also call it directly with /drawing-standards-audit.
Install just this one
npx archtmpl@latest --skill drawing-standards-audit --globalFirst time? The whole install, step by step
- Open Claude Code — the terminal version or the desktop app, either one.
- In a terminal, paste the line above and press Enter. In the app, paste it into the chat and ask Claude to run it.
- Restart Claude Code. That's the whole install.
Set up plugins for me: run `claude plugin marketplace add https://archaiflow.com/plugins/marketplace.json` and then `claude plugin install drawing-standards-audit@archaiflow`Paste into the Code tab (not Chat or Cowork) and approve when Claude asks. The third-party marketplace it mentions is this site. Windows may ask to install Git once.
What this skill does
Drawing Standards Audit
This is not a review of what the drawings show. It is a sweep for the things that make a set usable: that a reference lands somewhere, that the index matches the set, that a symbol means one thing. A set can be technically right and still generate a correction letter and forty RFIs because nobody could find anything.
Workflow
Step 1. Establish what the standard is
Ask, in one message:
- Is there an office or project standard? Paste or point at it.
- What is the set, and how is it supplied?
- What phase, and is this a pre-issue check or a general audit?
- Have consultants' sheets been included, and are they held to the same standard?
- Is there a previous revision to compare against?
Where no standard exists, say plainly that the audit will check internal consistency and nothing else. That is still worth doing and it is a different claim.
Step 2. Index and sheet integrity
- Every sheet in the index exists in the set.
- Every sheet in the set appears in the index.
- Sheet numbering follows a sequence, with gaps reported.
- Sheet titles in the index match the titles on the sheets.
- Consultants' sheets are present and in the sequence the index claims.
This is first because everything after depends on knowing what the set is.
Step 3. References, in both directions
The most valuable pass, and the most tedious.
| Reference | On sheet | Points to | Exists? | Kind |
|---|
Check:
- Every detail, section, elevation and enlarged plan callout lands on a drawing that exists, on the sheet it names, with the number it names.
- Every drawing on a sheet is referenced from somewhere. An unreferenced detail is either an orphan or a missing callout.
- Every schedule reference resolves.
- Every reference to a specification section names a section that exists in the book.
Report broken references by kind and by frequency. Thirty broken references all pointing at one sheet is one problem.
Step 4. Title block and issue data
Across every sheet: project name, number, address, north point, scale, date, revision, drawn and checked, seal block, and whatever else your standard names. Report by field rather than by sheet, so a field missing on forty sheets reads as one finding.
Check the revision data against the revision history and against any cloud on the sheet. A clouded change with no revision entry, or the reverse, is a finding.
Step 5. Symbols, abbreviations, and one-word-one-meaning
- Every symbol used appears in the legend.
- Every symbol in the legend is used.
- Every abbreviation used appears in the abbreviation list.
- The same term is used for the same thing throughout. Two words for one thing, or one word for two, both get reported.
- Wall types, door marks, room numbers and finish codes follow one convention.
Step 6. Information appearing twice
Find anything stated in two places and check the two agree: a dimension on a plan and on a detail, an area on a plan and on a schedule, a rating in a legend and in a schedule, a note on a sheet and in the specification.
Where the two disagree, report both values and neither as correct. Where the two agree, report the duplication anyway, because duplicated information will eventually disagree.
Step 7. Report by frequency
| Finding | Count | Systematic or isolated | Where |
|---|
Order by count. Then:
- Systematic findings first, with the likely cause if one is visible: a template problem, a missing standard, a sheet set up by a different hand.
- Isolated findings as a list.
- What could not be audited, and why: a set supplied as images, a standard not supplied, consultants' sheets missing.
Step 8. Save, if asked
Ask whether to write the audit to a file and where. CSV where it becomes a task list.
Rules
- Never supply a standard. Yours, the project's, or internal consistency only.
- Check references in both directions.
- Report by field and by frequency, never sheet by sheet.
- Where two sources disagree, report both and rule on neither.
- Report duplicated information even when it agrees.
- Say plainly what could not be audited.
- Never fix anything.
Anti-patterns
- Reviewing what the drawings show. Different skill, different question.
- Listing four hundred findings sheet by sheet, which nobody acts on.
- Checking that callouts resolve without checking for unreferenced drawings.
- Auditing against a remembered office standard.
- Treating a missing title block field on every sheet as forty findings.
- Deciding which of two disagreeing dimensions is right.
- Skipping consultants' sheets because they are somebody else's.
Resources
None. This skill is one file. Output is written directly at the path you choose.
What it does not check
What this does. Audits a set against its own conventions and against your office standard where you supply one. Reports findings by frequency, because one broken reference is a typo and thirty is a process problem, and they need different answers.
What this does not do.
- It carries no standard. No layer naming, no line weights, no text heights, no sheet numbering convention, no title block content. Yours or the project's, supplied. Where none is supplied, the audit checks internal consistency only and says so.
- It does not review content. Whether the detail is right, whether the design
works, whether the phase is complete:
drawing-checklistcovers phase content,constructability-reviewreads it as a builder,senior-plan-examinerpredicts the review. - It does not audit the model.
model-health-auditdoes. - It does not audit the specification.
spec-reviewdoes, and the coordination between the two is that skill's. - It does not fix anything. It reports, with counts.
- It does not replace the Architect of Record.
What you need before starting. The set, ideally as a single PDF or a directory. Your office standard, if there is one. The sheet index. The phase and whether this is an issue or a check.
Files it puts on your disk
.claude/skills/drawing-standards-audit/1 file · 7.1 KBSKILL.md7.1 KB