as-built-tracker
Track as-built documentation and record drawings. Monitor submission status, manage revisions, and ensure completeness for handover.
What this skill does
# As-Built Documentation Tracker
## Business Case
### Problem Statement
As-built documentation challenges:
- Tracking hundreds of drawings
- Managing revisions
- Ensuring completeness
- Meeting handover deadlines
### Solution
Systematic tracking of as-built documentation submissions, revisions, and approval status.
## Technical Implementation
```python
import pandas as pd
from typing import Dict, Any, List, Optional
from dataclasses import dataclass, field
from datetime import date, timedelta
from enum import Enum
class DocumentStatus(Enum):
NOT_STARTED = "not_started"
IN_PROGRESS = "in_progress"
SUBMITTED = "submitted"
UNDER_REVIEW = "under_review"
APPROVED = "approved"
REJECTED = "rejected"
RESUBMIT = "resubmit"
class DocumentType(Enum):
ARCHITECTURAL = "architectural"
STRUCTURAL = "structural"
MECHANICAL = "mechanical"
ELECTRICAL = "electrical"
PLUMBING = "plumbing"
FIRE_PROTECTION = "fire_protection"
CIVIL = "civil"
LANDSCAPE = "landscape"
SPECIFICATIONS = "specifications"
O_AND_M = "o_and_m"
@dataclass
class AsBuiltDocument:
document_id: str
document_number: str
title: str
doc_type: DocumentType
discipline: str
contractor: str
status: DocumentStatus
current_revision: str
required_date: date
submitted_date: Optional[date] = None
approved_date: Optional[date] = None
reviewer: str = ""
comments: str = ""
file_path: str = ""
@dataclass
class DocumentSubmission:
submission_id: str
document_id: str
revision: str
submission_date: date
submitted_by: str
file_path: str
status: DocumentStatus
review_comments: str = ""
class AsBuiltTracker:
"""Track as-built documentation."""
def __init__(self, project_name: str, handover_date: date):
self.project_name = project_name
self.handover_date = handover_date
self.documents: Dict[str, AsBuiltDocument] = {}
self.submissions: List[DocumentSubmission] = []
self._next_id = 1
def add_document(self,
document_number: str,
title: str,
doc_type: DocumentType,
discipline: str,
contractor: str,
required_date: date = None) -> AsBuiltDocument:
"""Add document to tracking."""
doc_id = f"DOC-{self._next_id:04d}"
self._next_id += 1
if required_date is None:
required_date = self.handover_date - timedelta(days=14)
doc = AsBuiltDocument(
document_id=doc_id,
document_number=document_number,
title=title,
doc_type=doc_type,
discipline=discipline,
contractor=contractor,
status=DocumentStatus.NOT_STARTED,
current_revision="0",
required_date=required_date
)
self.documents[doc_id] = doc
return doc
def import_document_list(self, df: pd.DataFrame):
"""Import document list from DataFrame."""
for _, row in df.iterrows():
doc_type = DocumentType(row.get('type', 'architectural').lower())
req_date = pd.to_datetime(row.get('required_date', self.handover_date)).date() if 'required_date' in row else None
self.add_document(
document_number=str(row['document_number']),
title=row['title'],
doc_type=doc_type,
discipline=row.get('discipline', ''),
contractor=row.get('contractor', ''),
required_date=req_date
)
def record_submission(self,
document_id: str,
revision: str,
submitted_by: str,
file_path: str = "") -> Optional[DocumentSubmission]:
"""Record document submission."""
if document_id not in self.documents:
return None
doc = self.documents[document_id]
submission = DocumentSubmission(
submission_id=f"SUB-{len(self.submissions)+1:04d}",
document_id=document_id,
revision=revision,
submission_date=date.today(),
submitted_by=submitted_by,
file_path=file_path,
status=DocumentStatus.SUBMITTED
)
self.submissions.append(submission)
# Update document
doc.status = DocumentStatus.SUBMITTED
doc.current_revision = revision
doc.submitted_date = date.today()
return submission
def review_submission(self,
document_id: str,
approved: bool,
reviewer: str,
comments: str = ""):
"""Review submitted document."""
if document_id not in self.documents:
return
doc = self.documents[document_id]
if approved:
doc.status = DocumentStatus.APPROVED
doc.approved_date = date.today()
else:
doc.status = DocumentStatus.REJECTED
doc.reviewer = reviewer
doc.comments = comments
# Update latest submission
for sub in reversed(self.submissions):
if sub.document_id == document_id:
sub.status = DocumentStatus.APPROVED if approved else DocumentStatus.REJECTED
sub.review_comments = comments
break
def get_summary(self) -> Dict[str, Any]:
"""Get documentation status summary."""
docs = list(self.documents.values())
today = date.today()
# Status counts
status_counts = {}
for status in DocumentStatus:
status_counts[status.value] = sum(1 for d in docs if d.status == status)
# By type
by_type = {}
for doc_type in DocumentType:
pending = sum(1 for d in docs if d.doc_type == doc_type and d.status != DocumentStatus.APPROVED)
if pending > 0:
by_type[doc_type.value] = pending
# Overdue
overdue = sum(
1 for d in docs
if d.required_date < today and d.status != DocumentStatus.APPROVED
)
# Completion rate
approved = sum(1 for d in docs if d.status == DocumentStatus.APPROVED)
completion = (approved / len(docs) * 100) if docs else 0
return {
'total_documents': len(docs),
'approved': approved,
'completion_rate': round(completion, 1),
'by_status': status_counts,
'by_type': by_type,
'overdue': overdue,
'days_to_handover': (self.handover_date - today).days
}
def get_contractor_status(self, contractor: str) -> Dict[str, Any]:
"""Get status for specific contractor."""
docs = [d for d in self.documents.values() if d.contractor == contractor]
approved = sum(1 for d in docs if d.status == DocumentStatus.APPROVED)
pending = len(docs) - approved
return {
'contractor': contractor,
'total': len(docs),
'approved': approved,
'pending': pending,
'completion_rate': round(approved / len(docs) * 100, 1) if docs else 0
}
def get_overdue_documents(self) -> List[Dict[str, Any]]:
"""Get overdue documents."""
today = date.today()
overdue = []
for doc in self.documents.values():
if doc.required_date < today and doc.status != DocumentStatus.APPROVED:
overdue.append({
'document_id': doc.document_id,
'document_number': doc.document_number,
'title': doc.title,
'contractor': doc.contractor,
'required_date': doc.required_date,
'days_overdue': (today - doc.required_date).dRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.