---
name: revit-documentation-qa
description: Check a Revit drawing set through a connected Revit MCP server (read-only) before an issue or submission - sheets, sheet numbers and names, views placed or not, title block parameters, revisions, schedules exported as CSV and drawing-compliance style rules the user defines. Use when the user prepares a drawing issue, transmittal, permit set or tender package from Revit and asks to "review the sheets", "revisar la documentación", "QA de planos", or "is the set ready to issue".
---

# Revit documentation QA (read-only)

Autodesk is adding AI drawing-compliance checks to Revit (announced at AU 2026); this skill gives any MCP-connected agent a transparent, rule-by-rule version the user controls.

## Requires
A Revit MCP server connected (Autodesk Revit MCP Server read tools, or a community server with equivalent queries). Read-only tools only. If no server is connected, ask the user to export the Sheet List and View List schedules to CSV and work from those files.

## Rules to check (confirm the list with the user first)
1. Sheet numbers: unique, follow the project pattern (ask for it, e.g. `A-101`).
2. Sheet names: no placeholders ("Unnamed", "Sheet", "Copy of").
3. Title block parameters filled: drawn by, checked by, approved by, date, scale, revision.
4. Every sheet has at least one view; views meant for issue are placed on a sheet.
5. Revisions: the current revision exists on the sheets listed in the transmittal; no sheet carries a revision that is not in the transmittal.
6. Scale consistency: the scale on the title block matches the main view's scale.
7. Dimensions and tags: views of the user's chosen categories (e.g. floor plans) have dimension and room tag annotations (count via queries; flag zero).
8. Project-specific rules the user adds (e.g. "every floor plan shows the north arrow legend").

## Procedure
1. Query sheets, views and title block parameters; export the sheet list schedule to CSV if the server supports export.
2. Evaluate each rule; record evidence (tool call, count, ids).
3. Produce the findings table and a "ready to issue: yes / no / yes after N fixes" verdict for the user to confirm.
4. Offer to draft the transmittal list (sheet, title, revision, date) from the verified data.

## Output
- Findings table: rule · status · affected sheets · evidence.
- Fix list ordered by effort.
- Draft transmittal (only verified rows).

## Never
- Never change sheets, views or parameters from this skill; for changes use `revit-mcp-write-safely`.
- Never mark a rule as passed when the query returned nothing; say the data was not available.