agentleFS
Sign inStart free
MakeItEzzz555MakeItEzzz555/Gridline/skills/construction-documentation/SKILL.md

construction-documentation

Skill39 starsChanged 23 days agoMITView on GitHub

Develop and coordinate architectural construction-document sets: sheet registers, plans, sections, elevations, details, schedules, notes, legends, drawing references, revisions, issue packages and documentation QA. Use for technical design/CD production, permit/tender/issue-set preparation, and drawing-set organization.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep verified facts, project assumptions, design options, and unresolved questions visibly separate.

    line 15
  2. Distinctive:

    Run cross-sheet, revision, annotation, dimension and consultant-interface QA before issue.

    line 22
  3. Very specific:

    Every callout resolves; room/door/window/detail identifiers reconcile across views and schedules.

    line 33
  4. Distinctive:

    Do not invent missing construction assemblies or engineering details.

    line 40
  5. Distinctive:

    If the native application is unavailable, produce a reproducible plan, script, structured data, SVG/DXF artifact, or exact in-application …

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Construction Documentation

Turn coordinated design information into a traceable drawing/document package without inventing technical details.

Preflight

  • Project stage, issue purpose, sheet/document numbering standard, units, scales, revision system and consultant deliverables.
  • Current architectural model/drawings, room/door/window/finish data, outline specifications and known coordination decisions.

Keep verified facts, project assumptions, design options, and unresolved questions visibly separate. If a required input is absent, record it as UNKNOWN rather than inventing it.

Workflow

  1. Build a deliverable/sheet register and responsibility matrix before producing sheets.
  2. Develop general arrangements first, then sections/elevations, enlarged plans and details; keep tags/references bidirectional.
  3. Generate schedules from authoritative model/data where possible; reconcile IDs and counts against plans.
  4. Run cross-sheet, revision, annotation, dimension and consultant-interface QA before issue; freeze the issue snapshot and record transmittal metadata.

Deliverables

  • Sheet/document register
  • Coordinated drawing package plan
  • Schedules and detail register
  • Issue checklist and transmittal metadata

Verification

  • Every callout resolves; room/door/window/detail identifiers reconcile across views and schedules.
  • Revision/date/status are consistent and the issue package opens/plots at intended scales.

For file/model changes, compare the result against a pre-change baseline and report changed items, skipped items, failures, and checks actually run.

Professional boundaries

  • Do not invent missing construction assemblies or engineering details.
  • Issue status does not equal code compliance or professional approval.

If a live CAD/BIM/GIS/analysis tool or MCP integration is available, inspect the current document/model and tool version before write operations. Prefer read-only inspection, dry runs, bounded samples, new output paths, and native undo/transaction mechanisms. Never claim a model or drawing was changed unless the tool confirms it.

If the native application is unavailable, produce a reproducible plan, script, structured data, SVG/DXF artifact, or exact in-application procedure instead of pretending to have operated the software.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free