specification-writing
Skill0 starsChanged 3 months agoMITView on GitHub
Authors and reviews CSI MasterFormat construction specifications — sections, divisions, submittals, and coordination with drawings. Use when writing spec sections, organizing a project manual, structuring Division 00-33 content, or reviewing specification accuracy and completeness.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- epicenter-md/epicentertheir own version, first seen Oct 8, 2026
- EpicenterHQ/epicentertheir own version, first seen Oct 8, 2026
- jahfaliabdulrahman-dev/hermes-skillstheir own version, first seen Oct 3, 2026
- talhaMah56/claude_skillstheir own version, first seen Sep 12, 2026
- wanshuiyin/Auto-claude-code-research-in-sleeptheir own version, first seen Jul 15, 2026
- raja21068/AutoResearchtheir own version, first seen May 5, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- wanshuiyin/Auto-claude-code-research-in-sleep★ 19ksame name
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
- raja21068/AutoResearch★ 2same name
- jahfaliabdulrahman-dev/hermes-skills★ 1same name
- talhaMah56/claude_skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- bim-interoperabilitySkill
- building-code-reviewSkill
- dxf-drawing-inspectionSkill
- egress-life-safetySkill
- ifc-model-analysisSkill
- mep-coordinationSkill
- sustainable-designSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Write, structure, and review construction specifications in the CSI MasterFormat organization (and Note: AIA/APEP content practices).
- Distinctive: line 50
Write requirements, not descriptions: Use directive language: "Provide...", "Submit...", "Comply with...".
- Distinctive: line 52
Review pass: check section numbers are current MasterFormat, materials match drawings, quantities/units consistent (US customary vs …
- Distinctive: line 62
Proprietary vs. performance specs: use "equal to & approved" language or sole-source per project rules.
- Distinctive: line 64
Don't invent manufacturer model numbers: If you can't verify a product exists, make the citation generic and flag for confirmation.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Specification Writing
Write, structure, and review construction specifications in the CSI MasterFormat organization (and Note: AIA/APEP content practices). Produces coordinated, accurate spec content that matches the drawings.
When to use
- Drafting a new spec section (e.g. Division 09 finishes, Division 08 openings)
- Setting up the project manual / spec book structure
- Editing or checking a spec for accuracy and coordination gaps
- Answering "what should the spec say for X?"
MasterFormat quick structure
Five-digit section numbers: Division (00–49) + 3 digits.
| Division | Content |
| 00 | Procurement & contracting requirements |
| 01 | General requirements (admin, submittals, quality control) |
| 02-19 | Facility construction — each discipline block |
| 22/23 | Plumbing / HVAC (naming differs by AIA master) |
| 26/27/28 | Electrical / communications / electronic safety & security |
| 31-33 | Sitework / utilities |
| 32 | Exterior improvements |
| 34-35 | Transportation / waterway & marine |
| 40-49 | Process integration |
A standard section skeleton (e.g. 09 90 00 — Paints & Coatings)
- Part 1 – General: Summary, References, Submittals, Quality Assurance, Delivery/Storage
- Part 2 – Products: Materials, Manufactured units, Finishes, Performance requirements
- Part 3 – Execution: Examination, Preparation, Application, Installation, Field quality control, Protection
Each paragraph uses "AUI" (Article/Uniform/Item) hierarchy: Article → Part; Paragraph → Uniform; Sub-paragraph → Item.
Writing workflow
- Clarify project scope — divisions needed, whether using a master (AIA, BSD, etc.), level of detail.
- Map to drawings — a spec must match what's drawn. For each spec section confirm: it's referenced by a drawing detail/callout, and the drawing's materials/performance match the spec.
- Draft sections in the skeleton: fill products first (materials/manufacturers/performance), then execution.
- Write requirements, not descriptions. Use directive language: "Provide...", "Submit...", "Comply with...". Avoid appealing adjectives ("high-quality", "durable") without measurable criteria.
- Cross-reference submittals (Division 01 §01 33 00) and related sections.
- Review pass: check section numbers are current MasterFormat, materials match drawings, quantities/units consistent (US customary vs metric), and that certification/inspection requirements are realistic.
Output format
Deliver spec section(s) as clean markup with the CSI three-part structure, headings numbered per section, and a brief notes column for coordination items (e.g. "verify with structural details").
Edge cases & cautions
- Section number collisions — verify the number is unused by another discipline in the project manual.
- Owner-provided vs. contractor-provided materials — state responsibilities explicitly.
- Proprietary vs. performance specs: use "equal to & approved" language or sole-source per project rules; never silently convert.
- Green building specs (LEED/v2, Title 24, red-list): include VOC/emissions + recycled content where the section applies.
- Don't invent manufacturer model numbers. If you can't verify a product exists, make the citation generic and flag for confirmation.
- Reference standards are best as named norms with year (e.g. "ASTM C1036-19"), not vague "per manufacturer".
Files
references/masterformat-2020-divisions.md— full Division 00-49 index with common sections per division.references/spec-guidelines.md— writing rules, AUI hierarchy, submittal/QA guidance, and editing checklist.assets/section-skeleton.md— blank section template.
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
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.