Construction Documentation Automation with Claude Code for Architects

The Documentation Burden in Architectural Practice

Construction documentation is the backbone of every architectural project, yet it remains one of the most time-consuming and error-prone phases of design. For most firms, the CD phase consumes 30 to 40 percent of total project hours. Junior architects spend weeks coordinating drawing sets, cross-referencing keynotes, updating detail libraries, and compiling project manuals. Partners and project architects spend their evenings reviewing redlines rather than designing.

The pain points are well documented across the industry. Keynote databases drift out of sync between projects. Detail libraries grow organically without consistent naming or cataloging. Drawing sheet indices fall behind as sheets get added, removed, or renumbered. RFI responses require digging through specification sections and drawing details to assemble coherent answers. Submittal logs live in spreadsheets that nobody updates in real time. And project closeout becomes a scramble to compile O&M manuals, warranty letters, and as-built documentation that should have been tracked from day one.

These are not design problems. They are information management problems. And information management is exactly where AI-powered tools like Claude Code excel. Rather than replacing the architect’s judgment on building assemblies or code compliance, Claude Code can serve as an intelligent documentation assistant that handles the repetitive, rule-based tasks that consume so much of the CD workflow.

This guide walks through eight specific Claude Code skills that target the most painful documentation tasks in architectural practice. Each skill is practical, buildable today, and designed to integrate with existing BIM and documentation workflows.

Where Claude Code Fits in the CD Workflow

Before diving into specific skills, it helps to understand where Claude Code adds value in the construction documentation pipeline. Claude Code operates on text, structured data, and file systems. It can read, write, search, and transform files on your local machine. This makes it particularly well suited for tasks that involve:

• Structured text databases such as keynote files, general notes, and specification references
• File system organization such as drawing indices, detail libraries, and document transmittals
• Cross-referencing and consistency checking such as verifying that keynotes used on drawings exist in the master database
• Template-based document generation such as RFI responses, submittal reviews, and closeout checklists
• Change tracking and audit trails such as revision logs and drawing issue records

Claude Code does not directly modify Revit models, AutoCAD drawings, or BIM geometry. Instead, it works alongside those tools by processing the text-based outputs they generate (exported schedules, keynote files, sheet lists) and producing text-based inputs they consume (updated keynote databases, drawing indices, specification references).

The practical workflow looks like this: you export structured data from your BIM tool, run a Claude Code skill against it, review the output, and import the results back. For many documentation tasks, this round-trip takes seconds rather than the hours of manual work it replaces.

Skill: Drawing Sheet Index and Set Organization

A well-maintained drawing sheet index is critical for navigating large construction document sets. On projects with 200 or more sheets, keeping the index current as sheets are added, removed, split, or renumbered becomes a project management task in itself.

Claude Code can automate this by reading your exported sheet list and producing a formatted, organized index. Here is an example of the structured input and output.

Input: Exported sheet list (CSV from Revit or similar)

Sheet Number,Sheet Name,Discipline,Phase,Issue Date
A-001,Cover Sheet,Architectural,CD,2026-03-15
A-101,Floor Plan - Level 1,Architectural,CD,2026-03-15
A-102,Floor Plan - Level 2,Architectural,CD,2026-03-15
A-201,Building Sections,Architectural,CD,2026-03-15
A-301,Exterior Elevations,Architectural,CD,2026-03-15
A-501,Wall Sections,Architectural,CD,2026-03-15
A-502,Wall Sections (continued),Architectural,CD,2026-03-15
A-601,Interior Details,Architectural,CD,2026-03-15
A-701,Door Schedule,Architectural,CD,2026-03-15
A-702,Window Schedule,Architectural,CD,2026-03-15
S-101,Foundation Plan,Structural,CD,2026-03-20
S-201,Framing Plan - Level 2,Structural,CD,2026-03-20
M-101,Mechanical Floor Plan - Level 1,Mechanical,CD,2026-03-22
E-101,Electrical Floor Plan - Level 1,Electrical,CD,2026-03-22

Output: Formatted drawing index with gap detection

DRAWING INDEX - Project XYZ
Generated: 2026-04-01
Total Sheets: 14

ARCHITECTURAL (10 sheets)
  A-001  Cover Sheet
  A-101  Floor Plan - Level 1
  A-102  Floor Plan - Level 2
  A-201  Building Sections
  A-301  Exterior Elevations
  A-501  Wall Sections
  A-502  Wall Sections (continued)
  A-601  Interior Details
  A-701  Door Schedule
  A-702  Window Schedule

STRUCTURAL (2 sheets)
  S-101  Foundation Plan
  S-201  Framing Plan - Level 2

MECHANICAL (1 sheet)
  M-101  Mechanical Floor Plan - Level 1

ELECTRICAL (1 sheet)
  E-101  Electrical Floor Plan - Level 1

WARNINGS:
- Gap detected: A-103 through A-200 (no sheets in range)
- Gap detected: A-302 through A-500 (no sheets in range)
- Structural discipline has only 2 sheets (unusually low for CD phase)
- No Plumbing sheets found

The skill can also compare the current index against a previous version to flag additions, deletions, and renumbered sheets. This comparison output becomes the basis for revision documentation and transmittal cover sheets. You can prompt Claude Code to format the output for your firm’s specific transmittal template, saving another round of manual formatting.

Skill: Keynote Database Management and Consistency Checking

Keynote systems are one of the most fragile parts of the documentation workflow. In Revit, keynotes reference an external text file that maps codes to descriptions. When that file gets out of sync with what appears on drawings, or when multiple team members edit it without coordination, the result is inconsistent documentation that creates confusion during construction.

Claude Code can serve as a keynote database manager that validates, deduplicates, and organizes your keynote file. Here is a practical example.

Input: Revit keynote file (tab-delimited)

03 00 00	CONCRETE
03 30 00	Cast-in-Place Concrete
03 30 00.A1	4000 PSI NORMAL WEIGHT CONCRETE
03 30 00.A2	3000 PSI NORMAL WEIGHT CONCRETE, SLAB ON GRADE
03 30 00.A3	GROUT, NON-SHRINK, PER SPEC SECTION 03 30 00
04 00 00	MASONRY
04 20 00	Unit Masonry
04 20 00.A1	CONCRETE MASONRY UNIT, 8" NOMINAL, RUNNING BOND
04 20 00.A2	CONCRETE MASONRY UNIT, 12" NOMINAL, RUNNING BOND
04 20 00.A3	CONCRETE MASONRY UNIT, 8" NOMINAL, STACK BOND
07 00 00	THERMAL AND MOISTURE PROTECTION
07 21 00	Thermal Insulation
07 21 00.A1	BATT INSULATION, R-19, FIBERGLASS
07 21 00.A2	RIGID INSULATION, R-10, XPS, 2" THICK
07 21 00.A3	BATT INSULATION, R-19, FIBERGLASS
07 27 00	Air Barriers
07 27 00.A1	SELF-ADHERED AIR AND VAPOR BARRIER

Claude Code consistency check output:

KEYNOTE DATABASE AUDIT
File: keynotes_project_2026.txt
Total entries: 14 (4 categories, 3 subcategories, 7 keynotes)

ISSUES FOUND:

1. DUPLICATE DESCRIPTION
   07 21 00.A1 and 07 21 00.A3 both read:
   "BATT INSULATION, R-19, FIBERGLASS"
   Action: Remove 07 21 00.A3 or differentiate description

2. INCONSISTENT CASING
   Category headers use Title Case ("Cast-in-Place Concrete")
   Keynote entries use ALL CAPS ("4000 PSI NORMAL WEIGHT CONCRETE")
   Recommendation: Standardize to ALL CAPS for keynotes, Title Case for headers

3. MISSING SPEC REFERENCES
   04 20 00.A1 through A3: No specification section reference in description
   Recommendation: Add "PER SPEC SECTION 04 20 00" to each

4. NUMBERING GAP
   No entries between 04 20 00 and 07 00 00
   Missing divisions: 05 (Metals), 06 (Wood/Plastics/Composites)
   Note: May be intentional if project scope excludes these

SUGGESTED ADDITIONS (based on common practice):
- 07 92 00.A1  JOINT SEALANT, PER SPEC SECTION 07 92 00
- 03 30 00.A4  CONCRETE TOPPING, LIGHTWEIGHT, PER SPEC SECTION 03 30 00

This kind of automated audit catches errors that are nearly invisible during manual review. Running it before each document issue ensures your keynote database stays clean throughout the project.

Skill: Detail Library Cataloging and Search

Every architectural firm accumulates a library of standard details over years of practice. These details live in various formats: Revit detail families, AutoCAD blocks, PDF references, and hand-drawn sketches that someone scanned years ago. Finding the right detail when you need it often means scrolling through folders or asking the most senior person in the office.

Claude Code can build and maintain a searchable catalog of your detail library by indexing file names, metadata, and descriptions you provide. The skill works by scanning a directory structure and building a structured index.

Example directory scan prompt:

Scan the directory at /project/details/ and build a catalog.
For each file, extract: filename, file type, parent folder
(as category), and file size. Output as a searchable markdown table.

Generated catalog:

| ID | Category | Detail Name | File Type | Size | Tags |
|----|----------|-------------|-----------|------|------|
| D-001 | Foundations | Spread Footing at Grade Beam | .dwg | 245 KB | foundation, footing, grade beam |
| D-002 | Foundations | Pier and Grade Beam Connection | .dwg | 189 KB | foundation, pier, connection |
| D-003 | Wall Sections | CMU Cavity Wall at Foundation | .rvt | 1.2 MB | masonry, cavity wall, foundation |
| D-004 | Wall Sections | Metal Stud Exterior Wall | .rvt | 890 KB | metal stud, exterior, sheathing |
| D-005 | Roof | TPO Membrane at Parapet | .dwg | 312 KB | roofing, TPO, parapet, flashing |
| D-006 | Roof | Standing Seam Metal Roof Ridge | .dwg | 278 KB | metal roof, ridge, standing seam |
| D-007 | Waterproofing | Below Grade Waterproofing | .dwg | 198 KB | waterproofing, below grade, drainage |
| D-008 | Stairs | Steel Stair Stringer at Landing | .rvt | 1.5 MB | stairs, steel, landing, stringer |

Once this catalog exists as a local file, you can ask Claude Code natural language questions like “find all details related to waterproofing at foundations” or “which details show parapet conditions” and get instant results. You can also ask it to flag details that have not been updated in over two years, or identify categories where your library is thin compared to typical project needs.

The real power comes from maintaining this catalog as a living document. Each time your firm creates a new standard detail, a quick Claude Code prompt adds it to the index with appropriate tags and metadata.

Skill: General Notes and Code Compliance Boilerplate Generator

General notes sheets are among the most tedious pages in a construction document set. They compile building code requirements, accessibility standards, fire rating information, and project-specific conditions into dense text blocks that must be accurate and jurisdiction-specific.

Claude Code can generate and maintain general notes based on project parameters you provide. Instead of copying notes from the last similar project and hoping nothing changed, you define the project conditions and let the skill assemble the appropriate notes.

Example prompt structure:

Generate architectural general notes for the following project:
- Building type: Type IIA construction, Business (B) occupancy
- Code: 2021 IBC with local amendments (City of Austin)
- Stories: 3 above grade, 0 below
- Sprinklered: Yes, NFPA 13
- Accessibility: 2010 ADA Standards + TAS (Texas)
- Seismic Design Category: A
- Wind Speed: 120 mph (Ultimate)
- Climate Zone: 2A

Output as numbered notes organized by CSI division.

The skill produces organized notes grouped by topic: structural requirements, fire resistance ratings, accessibility provisions, energy code compliance, and material standards. Each note includes the code reference so the architect can verify it against the specific edition in use.

This is not about blindly trusting AI-generated code references. The architect still reviews every note. But starting from a well-organized, code-referenced draft saves hours compared to building the notes sheet from scratch or hunting through a previous project’s notes to find relevant items.

You can extend this skill by maintaining a firm-wide notes library as a structured text file. Claude Code can then pull from your firm’s vetted notes and supplement with project-specific items, giving you the best of both standardization and customization.

Skill: Drawing Revision Tracking and Change Documentation

Revision tracking across a large drawing set is one of those tasks that seems simple in theory but becomes unwieldy in practice. Every time a drawing set is reissued, the revision schedule on each sheet needs to be updated, the transmittal needs to list what changed, and the project record needs to capture why.

Claude Code can maintain a revision database as a structured text file and generate the various outputs you need from it.

Revision database format:

{
  "project": "City Center Office Building",
  "revisions": [
    {
      "rev": "1",
      "date": "2026-03-15",
      "description": "Issued for Permit",
      "sheets_affected": ["A-001", "A-101", "A-102", "A-201", "A-301", "A-501", "A-502", "A-601", "A-701", "A-702", "S-101", "S-201"],
      "reason": "Initial permit submission"
    },
    {
      "rev": "2",
      "date": "2026-04-01",
      "description": "Plan Check Comments",
      "sheets_affected": ["A-101", "A-201", "A-501", "A-601"],
      "reason": "Address plan check comments from Building Department dated 2026-03-28",
      "changes": [
        {"sheet": "A-101", "delta": "Added exit signage and revised corridor width at Grid C"},
        {"sheet": "A-201", "delta": "Updated fire rating annotation at Level 2 floor assembly"},
        {"sheet": "A-501", "delta": "Revised exterior wall section at window head condition"},
        {"sheet": "A-601", "delta": "Added accessible toilet room grab bar detail"}
      ]
    }
  ]
}

From this single database, Claude Code can generate multiple outputs on demand: a transmittal cover sheet listing affected sheets, a revision narrative for project records, individual sheet revision schedules formatted for import back into Revit, and a cumulative revision log for the project file. When the contractor asks “what changed in Rev 2?”, the answer is already compiled and ready to send.

Skill: RFI Response Drafting from Project Documentation

Requests for Information (RFIs) during construction consume significant architect time. Each RFI requires reading the question, searching through drawings and specifications for the relevant information, composing a clear response, and often sketching a clarification detail. The searching and composing steps are where Claude Code adds the most value.

The skill works by maintaining a searchable index of your project documentation. You feed it your specification table of contents, your drawing index, and optionally your keynote database. When an RFI comes in, you provide the question text and Claude Code drafts a response referencing the relevant documents.

Example RFI input:

RFI #047
From: General Contractor
Subject: Waterproofing membrane extent at below-grade retaining wall

Question: Drawing A-501 shows waterproofing membrane at the foundation
wall, but does not indicate how far the membrane extends above
finished grade. Please clarify the termination height and
detailing at the transition from below-grade to above-grade
wall assembly.

Claude Code drafted response:

RFI #047 RESPONSE - DRAFT

Reference Documents:
- A-501: Wall Sections (Rev 2, 2026-04-01)
- A-601: Interior Details, Detail 4/A-601
- Specification Section 07 10 00: Dampproofing and Waterproofing
- Specification Section 07 62 00: Sheet Metal Flashing and Trim

Response:
Waterproofing membrane shall extend from the top of the footing
to 8 inches above finished grade, minimum. At the above-grade
transition, terminate the membrane with a stainless steel
termination bar and sealant, per Detail 4/A-601. Refer to
Specification Section 07 10 00, Article 3.3 for membrane
termination requirements.

See attached sketch [ARCHITECT TO PROVIDE] for clarification
at the grade transition condition.

Status: DRAFT - Requires architect review and supplemental sketch

The draft saves time by assembling the relevant references and composing a professional response. The architect reviews it, adds or corrects the technical content, attaches any needed sketches, and sends the final version. Even if the draft needs significant revision, it provides a starting framework that eliminates the blank-page problem.

To make this skill effective, invest time upfront in building the searchable project index. Export your specification table of contents as a text file, maintain your drawing index (using the skill described earlier), and keep your keynote database current. The better your index, the more accurate the RFI drafts become.

Skill: Submittal Review and Tracking Automation

Submittal management during construction involves tracking hundreds of individual submissions from contractors and subcontractors. Each submittal needs to be logged, routed to the correct reviewer, reviewed against the specifications, and returned with one of several action codes. The tracking spreadsheet alone can become a full-time job on large projects.

Claude Code can automate several parts of this workflow. First, it can generate and maintain the submittal log from a specification-based template.

Generating a submittal register from specifications:

Specification sections requiring submittals:
03 30 00 - Cast-in-Place Concrete (mix designs, test reports)
04 20 00 - Unit Masonry (CMU samples, mortar mix)
05 12 00 - Structural Steel Framing (shop drawings, mill certs)
07 21 00 - Thermal Insulation (product data)
07 27 00 - Air Barriers (product data, installer qualifications)
07 42 13 - Metal Wall Panels (shop drawings, color samples)
08 11 13 - Hollow Metal Doors and Frames (shop drawings)
08 14 16 - Flush Wood Doors (product data, finish samples)
08 71 00 - Door Hardware (hardware schedule, templates)
09 29 00 - Gypsum Board (product data)
09 65 00 - Resilient Flooring (product data, color samples)
09 91 00 - Painting (product data, color schedule)

Generated submittal register:

| Sub # | Spec Section | Description | Type | Reviewer | Status | Due Date |
|-------|-------------|-------------|------|----------|--------|----------|
| 03-001 | 03 30 00 | Concrete Mix Design - 4000 PSI | Mix Design | Structural | Pending | -- |
| 03-002 | 03 30 00 | Concrete Mix Design - 3000 PSI | Mix Design | Structural | Pending | -- |
| 04-001 | 04 20 00 | CMU Samples - 8" and 12" | Sample | Architect | Pending | -- |
| 04-002 | 04 20 00 | Mortar Mix Design | Mix Design | Structural | Pending | -- |
| 05-001 | 05 12 00 | Structural Steel Shop Drawings | Shop Drawing | Structural | Pending | -- |
| 05-002 | 05 12 00 | Steel Mill Certificates | Test Report | Structural | Pending | -- |
| 07-001 | 07 21 00 | Thermal Insulation Product Data | Product Data | Architect | Pending | -- |
| 07-002 | 07 27 00 | Air Barrier Product Data | Product Data | Architect | Pending | -- |
| 07-003 | 07 27 00 | Air Barrier Installer Quals | Qualification | Architect | Pending | -- |
| 07-004 | 07 42 13 | Metal Wall Panel Shop Drawings | Shop Drawing | Architect | Pending | -- |
| 07-005 | 07 42 13 | Metal Wall Panel Color Samples | Sample | Architect | Pending | -- |
| 08-001 | 08 11 13 | HM Door and Frame Shop Drawings | Shop Drawing | Architect | Pending | -- |
| 08-002 | 08 14 16 | Wood Door Product Data | Product Data | Architect | Pending | -- |
| 08-003 | 08 14 16 | Wood Door Finish Samples | Sample | Architect | Pending | -- |
| 08-004 | 08 71 00 | Door Hardware Schedule | Schedule | Architect | Pending | -- |
| 09-001 | 09 29 00 | Gypsum Board Product Data | Product Data | Architect | Pending | -- |
| 09-002 | 09 65 00 | Resilient Flooring Product Data | Product Data | Architect | Pending | -- |
| 09-003 | 09 65 00 | Resilient Flooring Color Samples | Sample | Architect | Pending | -- |
| 09-004 | 09 91 00 | Paint Product Data | Product Data | Architect | Pending | -- |
| 09-005 | 09 91 00 | Paint Color Schedule | Schedule | Architect | Pending | -- |

When a submittal comes in, you can ask Claude Code to compare the submitted product data against the specification requirements and draft review comments. It will not catch everything a trained architect would notice, but it can flag obvious discrepancies like wrong fire ratings, missing test reports, or products that do not match the basis of design. The architect then focuses their review time on the items that require professional judgment rather than specification cross-referencing.

Skill: Project Closeout Document Compiler

Project closeout is notoriously chaotic. The list of required closeout documents is long, the deadlines are tight (often tied to final payment), and the documents come from dozens of different subcontractors and suppliers. Missing a single warranty letter or O&M manual can delay project completion.

Claude Code can manage the closeout checklist by tracking what has been received, what is outstanding, and who is responsible for each item.

Closeout tracking database:

{
  "project": "City Center Office Building",
  "substantial_completion": "2026-09-15",
  "final_completion": "2026-10-15",
  "closeout_items": [
    {
      "category": "Warranties",
      "items": [
        {"item": "Roofing System - 20 Year", "responsible": "ABC Roofing", "spec": "07 52 00", "status": "received", "date_received": "2026-09-10"},
        {"item": "Waterproofing - 10 Year", "responsible": "XYZ Waterproofing", "spec": "07 10 00", "status": "outstanding", "follow_up_date": "2026-09-20"},
        {"item": "Storefront System - 10 Year", "responsible": "Glass Co", "spec": "08 44 13", "status": "outstanding", "follow_up_date": "2026-09-18"},
        {"item": "HVAC Equipment - 1 Year", "responsible": "Mechanical Sub", "spec": "23 00 00", "status": "received", "date_received": "2026-09-12"}
      ]
    },
    {
      "category": "O&M Manuals",
      "items": [
        {"item": "HVAC Systems O&M", "responsible": "Mechanical Sub", "spec": "23 00 00", "status": "under_review", "date_received": "2026-09-08"},
        {"item": "Electrical Systems O&M", "responsible": "Electrical Sub", "spec": "26 00 00", "status": "outstanding", "follow_up_date": "2026-09-22"},
        {"item": "Fire Alarm O&M", "responsible": "Fire Alarm Sub", "spec": "28 31 00", "status": "outstanding", "follow_up_date": "2026-09-22"}
      ]
    },
    {
      "category": "As-Built Documentation",
      "items": [
        {"item": "Architectural As-Builts", "responsible": "General Contractor", "status": "in_progress"},
        {"item": "MEP As-Builts", "responsible": "General Contractor", "status": "outstanding"},
        {"item": "Site As-Builts", "responsible": "Civil Engineer", "status": "received", "date_received": "2026-09-05"}
      ]
    }
  ]
}

From this database, Claude Code generates status reports, follow-up emails, and completion checklists. You can ask it to draft a follow-up email to the waterproofing subcontractor requesting the outstanding warranty, complete with the specification reference and the contractual deadline. You can generate a summary report for the owner showing closeout progress as a percentage. And when everything is finally received, you can have it compile a transmittal letter and document index for the final closeout package.

The key insight is that the tracking database is simple structured text. You do not need specialized project management software to maintain it. A JSON or markdown file on your local machine, managed through Claude Code prompts, gives you a flexible and powerful closeout tracking system.

Integrating Documentation Skills with BIM Workflows

These skills become significantly more powerful when connected to your BIM workflow. The integration points are straightforward because most BIM tools export the text-based data that Claude Code works with.

Revit integration points:

• Keynotes: Revit reads keynote files from a configurable path. Claude Code edits the same file. After running the keynote audit skill, the updated file is immediately available in your Revit model.
• Sheet lists: Export the sheet list schedule from Revit as a CSV. Run the drawing index skill. The formatted output can serve as the basis for your cover sheet drawing index.
• Schedules: Any Revit schedule (door, window, room, finish) can be exported as a CSV and processed by Claude Code for consistency checking, gap detection, or cross-referencing against specifications.
• Shared parameters: Export shared parameter definitions and use Claude Code to audit for duplicates, inconsistent naming, or missing parameters needed for your documentation standards.

File-based workflow example:

1. Revit → Export sheet list as CSV
2. Claude Code → Run drawing index skill
3. Claude Code → Output formatted index as TXT
4. Architect → Review and copy into Revit title block family
5. Revit → Updated drawing index on cover sheet

Time: ~5 minutes (vs. 30-60 minutes manual formatting)

For firms using Dynamo or pyRevit, you can take this further by writing scripts that automatically export the data Claude Code needs and import the results. The Claude Code skill handles the intelligence (auditing, formatting, cross-referencing), while Dynamo handles the BIM tool integration (reading from and writing to the model).

The same principle applies to ArchiCAD, Vectorworks, or any BIM tool that supports structured data export. The documentation skills described in this guide are tool-agnostic; they operate on text files that any BIM platform can produce.

Building a Documentation Skill Library for Your Firm

The skills described in this guide are starting points. The real value comes from building a library of skills tailored to your firm’s specific documentation standards, project types, and workflows. Here is a practical approach to getting started.

Step 1: Identify your highest-pain documentation tasks. Survey your project teams. Which tasks take the most time? Which ones generate the most errors? Which ones do junior staff dread? Those are your first automation candidates.

Step 2: Standardize your inputs. Claude Code skills work best when they consume consistent, structured input. If your keynote files use different formats on every project, standardize on one format first. If your detail library naming is inconsistent, establish a naming convention. The skill development process itself forces beneficial standardization.

Step 3: Start with one skill and iterate. Pick the task with the clearest input/output definition, build the skill, and test it on a real project. Gather feedback from the team. Refine the prompts and output formats. Then move on to the next skill.

Step 4: Document your skills as reusable prompts. Store your refined prompts in a shared location (a firm knowledge base, a Git repository, or even a shared drive folder). Include example inputs and expected outputs so any team member can use the skill without needing to understand how to write prompts from scratch.

Step 5: Create skill chains for common workflows. Once you have individual skills working, combine them into sequences. For example, a “pre-issue QC” chain might run the keynote audit, drawing index update, and revision tracker in sequence, producing a single QC report before each document issue.

Practical folder structure for a firm skill library:

firm-skills/
  keynotes/
    audit-keynotes.md          (prompt + instructions)
    sample-input.txt           (example keynote file)
    sample-output.txt          (expected audit results)
  drawing-index/
    generate-index.md
    sample-sheet-list.csv
    sample-index-output.txt
  rfi-response/
    draft-rfi.md
    project-index-template.txt
    sample-rfi-input.txt
    sample-response-output.txt
  closeout/
    track-closeout.md
    closeout-template.json
    sample-status-report.txt
  general-notes/
    generate-notes.md
    code-reference-library.txt
    sample-project-params.txt

Each skill folder contains the prompt definition, sample inputs, and expected outputs. New team members can learn the system by reviewing the samples. Senior staff can refine skills based on project experience. Over time, this library becomes a significant firm asset that captures institutional knowledge about documentation best practices.

The documentation burden in architecture is not going away. Projects are getting more complex, codes are getting more detailed, and client expectations for thorough documentation continue to rise. But the nature of that burden is shifting. With tools like Claude Code handling the repetitive, rule-based aspects of documentation, architects can focus their expertise on the decisions that actually require professional judgment: selecting the right building assembly, resolving complex detailing conditions, and ensuring the built result matches the design intent. The documentation still gets done. It just takes less of your evening to do it.