Trades Operations Skill

What This Skill Does

• Create estimates based on measured scope items (square footage, linear feet, units)
• Schedule and assign field work to crews or subtrades
• Track progress by scope item and location
• Pay subtrades based on completed measured work
• Invoice customers and collect payment

When to Use This Skill

• Product configuration with dependencies → use cpq-builder
• Inventory and stock management → use erp-builder (future)
• Generic CRM or contact management → use crm-builder (future)

Section Definitions

Section 1: Estimate

• Project name — inline editable text (click to edit, save on blur)
• Customer name — inline editable text
• Address — inline editable text
• Estimate number — auto-generated, read-only
• Lead source —

  Select

  dropdown if DOMAIN.md defines sources, otherwise free text
• Estimator notes —

  Textarea

  , always editable

Select

Select

• "Add row" button below the table to add more scope items
• Multiple rows per scope type — e.g., two drywall rows for different locations with different types
• Auto-calculated footer: Subtotal, Tax (GST 5%), Total — updates on every cell change
• All cells are directly editable — click a cell, type, blur to save. See frontend-design skill for inline editing pattern.

• Entity Registry → Job Specification sub-items become the Scope dropdown options
• Business Rules → unit of measure (sqft, lft), tax type and rate, payment terms
• Terminology Glossary → exact scope names (not generic labels)

Section 2: Schedule

• Assigned roles/people —

  Select

  dropdowns from DOMAIN.md Stakeholder Map, NOT free text
• Scope sequence — reorderable list showing which scope items happen in what order
• Start date — date picker, editable
• Target completion date — date picker, editable
• Field crew notes —

  Textarea

  , editable

Section 3: In Progress

• Table populated from Estimate's scope items — same rows, now being tracked for completion

Select

• Status changes save immediately to localStorage
• "Mark all completed" button for bulk update
• Progress indicator: "3 of 5 scope items completed"

Section 4: Close Out

• Subtrade payment amount — auto-calculated from completed scope items (sqft × rate)
• Status:

  Select

  dropdown — Ready to pay / Paid
• Payment date — date picker, editable when status is Paid
• Reference to Bold if mentioned in DOMAIN.md

• Invoice amount — subtotal + tax from Estimate
• Status:

  Select

  dropdown — Ready to send / Sent / Paid
• Invoice date — date picker, editable
• Reference to Arvest if mentioned in DOMAIN.md
• "Close out job" action button that marks the project as Completed
• Both invoice statuses must be saved to localStorage

Section 5: Job Summary

1. Company header — brand logo from domain.md Brand Logos section (use the logo URL or path provided) + company name + placeholder address ("123 Main St, City, Province, Postal Code — update in settings")
2. Project metadata — project name, customer, address, estimate number, dates, assigned to. Two-column grid of label/value pairs.
3. Scope summary table — all scope items with scope type, location, spec/type, sqft, rate, line total. Clean

   Table

   with right-aligned numeric columns.
4. Totals block — subtotal, tax (GST 5%), total. Total is large and bold.
5. Payment status — trade invoice status badge + customer invoice status badge, side by side.
6. Terms — payment terms (Net 30), currency (CAD).

Layout Pattern

Left sidebar (always visible, collapsible)

MainLayout.tsx

estimated, scheduled, in progress, completed

Main content (center — changes per section)

currentStep

currentStep

// ALL FIVE panels, conditional rendering
{currentStep === 0 && <EstimatePanel />}
{currentStep === 1 && <SchedulePanel />}
{currentStep === 2 && <InProgressPanel />}
{currentStep === 3 && <CloseOutPanel />}
{currentStep === 4 && <JobSummaryPanel />}

Right sidebar (always visible)

RBAC behavior

• Seed localStorage with roles from DOMAIN.md User Roles or Stakeholder Map.
• Role switcher is a single

  DropdownMenu

  dropdown in the header bar — not separate buttons. Shows active role name and badge.
• Approval gating: If DOMAIN.md says only certain roles can close out or approve, disable those buttons for other roles.
• Role-specific views: If roles handle specific stages (e.g., estimator handles Estimate, project manager handles Schedule), show relevant context when that role is active.

Price visibility

• Show prices on the Estimate panel — unit rates, line totals, subtotal, tax, total.
• Show running totals in the right sidebar Project Summary.
• Use the currency, tax type, and tax rate from DOMAIN.md.
• Format prices with the currency code (e.g., "$3,900.40 CAD" or "$3,900.40" with "CAD" shown in the summary).

shadcn/ui component mapping

Input

Label

Select

Table

TableHeader

TableRow

TableCell

Badge

Badge

Badge

Select

SelectContent

SelectItem

Card

CardHeader

CardContent

Button

cn()

DropdownMenu

Card

Card

text-sm text-muted-foreground

Input

type="date"

Textarea

AlertDialog

Sonner

toast()

Deterministic Mapping Rules

Entity → Scope Item Mapping

Business Rule → Validation Mapping

Integration → Reference Mapping

Reference Files

DOMAIN.md

.tasks/domain.md

frontend-design/SKILL.md