Institutional knowledge, executable.
The procedure lives in the org, not in one person's head or a binder nobody opens.
Teach it once. Run it everywhere.
Your best reviewer's checklist, your safety plan format, your vendor questions: written down once as a Specset skill, then run by agents with full coverage and citations on every project you choose.
waterproofing-reviewPublished
All projectsInstructions · the playbook
- Check lap widths at every transition and termination. - Flag terminations without counterflashing or a reglet detail. - Verify drainage mat and protection board ahead of backfill. - Cross-check penetrations against 07 13 26 §3.3. - Severity High when the detail is below grade.
Output Checklist · 42 rowsCoverage Every spec sectionOn flag Files an issue
Run with /waterproofing-review in any thread8 runs this month
Runs like the built-in reviews.
The same coverage engine, worker fan-out, and citations that power submittal and design review.
Draft, publish, scope.
Managers control what ships; the team just types the slash command and gets the artifact.
Trusted by the teams delivering public work
“Our waterproofing checklist lived in one senior PM's head. Now it's a skill that every project runs on day one.”
22K+Findings filed into issue registers on Specset
475+Projects in production, bid through closeout
01 · From procedure to skill
Write it down once, in plain language.
Every firm has procedures that only exist as judgment: what to check, what counts as a flag, how the deliverable should read. A skill is that judgment, made runnable.
01 · Author it
Turn our waterproofing checklist into a skill.
Created waterproofing-review · draft42 checklist rows · edit or publish in settings
Describe the procedure in chat and the skill creator drafts it, or write it yourself in a settings form. Plain markdown, no code, and it stays a draft until a manager publishes it.
02 · Shape the output
ChecklistYour rows and columns, worked and flagged
ExtractionWorkers discover the rows, you define the schema
IssuesFindings filed straight into the register
DocumentDrafted into your .docx or .xlsx template
A skill produces a real artifact: a cited table that exports to Excel, issues in the project register, or a document in your firm's own format.
03 · Run with coverage
One worker per unit
- Every document, or every page of each
- Every spec section
- Every drawing sheet
- Every RFI
Your instructions ride along to every worker as domain guidance, so the judgment in the playbook is applied to the whole record, not a sample of it.
02 · In every thread
Your skills, next to the built-ins.
Published skills appear in the same picker as submittal review and contract review, your org's first. A new PM types the slash command and runs a procedure it took your firm twenty years to learn.
/water
Custom · your org
waterproofing-reviewChecklist · every spec section
dive-safety-planDocument · .docx template
vendor-prequalChecklist · 12 columns
Systemsubmittal-reviewBuilt-in
contract-reviewBuilt-in
03 · What teams encode
Six skills from the field.
Reviews, extractions, and deliverables that are specific to one firm's way of working. That specificity is the point.
The senior PM's failure points
Below-grade details checked against the lessons a 30-year career collected.
Checklist · files issuesPre-dive plan, your format
Marine scopes drafted into the safety plan shell your EHS team already signs.
Document · .docx templateSub prequalification
The questions you ask every sub, answered from their package with citations.
Checklist · custom columnsCount what the drawings show
Fire and smoke dampers pulled off every mechanical sheet into one table.
Extraction · every sheetMinutes in the house style
OAC notes structured the way your firm distributes them, every week.
Document · markdownAn envelope-only pass
A focused review lens your team invented, filed into the same issue register.
Issues · agent-plannedCommon questions
What teams ask about custom skills.
01What exactly is a custom skill?
A named playbook the agents can load and follow: markdown instructions, an output shape, and coverage rules, scoped to your org or to specific projects. It stays a draft until published, and it runs beside the built-in skills in every thread.
02How do we author one?
Describe the procedure in chat and the skill creator drafts the skill for you, or write it directly in a settings form. No code either way. Most teams stand up their first skills with the Specset team during onboarding, then iterate on their own.
03What outputs can a skill produce?
Four shapes: a checklist with up to 300 of your rows and a dozen custom columns, an extraction table where workers discover the rows, issues filed straight into the project register, or a document drafted into your attached Word or Excel template. Tables export to .xlsx.
04How does a skill actually run?
Type its slash name in any thread, or let the agent reach for it when the request matches. Coverage runs dispatch one worker per document, spec section, drawing sheet, or RFI, and your instructions travel with every worker as domain guidance. Results come back cited.
05Who can create and see skills?
Managers author, edit, and publish; members see and run published skills. A skill can be org-wide or pinned to specific projects, and drafts stay hidden from the team until they are ready.
06Can a skill run code or call other systems?
No. A skill is instructions plus an output configuration, not custom code, so there is nothing to sandbox or maintain. Connections to systems like Procore and Autodesk are platform features that skills benefit from rather than something each skill wires up.
Start with the checklist you trust
Put your playbook to work.
Bring the procedure your best people carry in their heads. We'll turn it into a skill on your first project and run it against a live record.