科研 Skill

土木项目管理总调度

orchestrator

Classifies incoming civil-engineering PM events and routes each to the matching cost, programme, risk, quality, HSE, RFI, or report skill. Use as the entry point for project management requests.

发布者 Codar安全审核通过v0.1.0更新于 2026-11-18

SKILL.md

PM Orchestrator

Conductor for civil engineering project management. One entry point. Every request classified, routed, and tracked. No situation handled ad-hoc.

RULE: Every project session begins here. Describe what just happened or ask what needs to happen next. The orchestrator routes everything.


Phase 0 — Project State Snapshot

On first invocation for any project, establish the state snapshot. On subsequent invocations, read and update it.

PROJECT STATE SNAPSHOT
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Project:          [name]
Client:           [name]
Contract ref:     [PRJ/CON/YYYY/NNN or client ref]
Contract type:    [Lump sum / Admeasurement / Cost-reimbursable / BOO]
Contract value:   [₦ / $]
PM:               [PM] / [assigned PM]
Current phase:    [INITIATION / PLANNING / EXECUTION / MONITORING / CLOSEOUT]
Programme status: [ON TRACK / AT RISK / DELAYED — N days]
Budget status:    [WITHIN / AT RISK / OVERSPEND — amount]
Last updated:     [date]

OPEN ITEMS (auto-surfaced):
  Overdue RFIs:         [N]
  Open NCRs:            [N]
  Unmitigated HIGH risks: [N]
  Pending sign-offs:    [N]
  Overdue invoices:     [N]
  Actions from last meeting: [N open]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Store this snapshot. Update it at the end of every session.


Phase 1 — Request Classification

When any input arrives, classify it before routing. Every input falls into one of these types:

CodeTypeDescription
SITE-ANOMALYSite defect or anomalyUnexpected ground conditions, structural finding, material failure
SITE-PROGRESSProgress updateWork completed, milestone achieved, activity started
SCOPE-CHANGEScope eventClient instruction, design change, unforeseen work
COST-EVENTCost eventVariation claim, dayworks, price adjustment, invoice
SCHEDULE-EVENTSchedule eventDelay, acceleration, programme revision request
RISK-EVENTRisk materialisingA risk on the register is happening or has happened
QUALITY-EVENTQuality failureNCR raised, inspection failed, material rejected
HSE-EVENTSafety or environmentIncident, near-miss, unsafe condition, environmental release
DESIGN-EVENTDesign issueDrawing error, RFI needed, design clarification required
CLIENT-COMMSClient instruction or queryLetter, email, meeting outcome needing response or action
CONTRACTOR-COMMSContractor query or noticeClaim notice, programme submission, approval request
SIGN-OFFProfessional certificationReport, certificate, adequacy letter requiring issue
REPORTINGReporting dueWeekly/monthly report, board update, regulatory submission
PLANNINGPlanning requestNew task, WBS item, resource plan, baseline update
CLOSEOUTProject closeHandover, punch list, as-builts, DLP management
GENERALUnclassifiedRoute to report for logging and triage

Classification output:

CLASSIFICATION:
  Type:     [code]
  Priority: [IMMEDIATE / THIS SESSION / THIS WEEK / LOG AND MONITOR]
  Trigger:  [what the user said / what happened]

Phase 2 — Routing Table

Once classified, route to the correct skill or chain.

Single-skill routes

CodePrimary SkillNotes
SITE-ANOMALYinvestigateIron law: root cause before any instruction
SITE-PROGRESSprogrammeUpdate schedule, check critical path impact
COST-EVENTcostLog variation, update forecast, flag if threshold breached
SCHEDULE-EVENTprogrammeDelay analysis, recovery options, notify if contractual
RISK-EVENTriskUpdate register, escalate if HIGH/CRITICAL
QUALITY-EVENTqualityOpen NCR, assign corrective action, track to close
HSE-EVENThseClassify incident, initiate reporting chain
DESIGN-EVENTrfiOpen RFI, route to designer, track response
CLIENT-COMMSreportLog, draft response, assign action
CONTRACTOR-COMMSreportLog, classify (routine / contractual notice), action
REPORTINGreportGenerate report from current project state
PLANNINGprogrammeWBS update, resource plan, baseline
CLOSEOUTretrospective notes + document-releaseRun in sequence

Chained routes (multi-skill sequences)

These situations require more than one skill in sequence:

SCOPE-CHANGE chain:

scope → cost (price the change) → programme (schedule impact)
→ obtain [PM] sign-off if the variation order requires it → report (notify client)

SITE-ANOMALY with structural implication:

investigate → [if IMMEDIATE urgency] obtain [PM] sign-off before any instruction to contractor
→ rfi (if design input needed) → cost (flag potential variation)
→ report (log for weekly report) → risk (update risk register)

QUALITY-EVENT with design cause:

quality (open NCR) → rfi (raise design query if design-caused)
→ investigate (if root cause unclear) → cost (variation if contractor not at fault)

SIGN-OFF request:

document-release (check all supporting docs current)
→ obtain [PM] sign-off as a confirmation gate before issue

PROJECT START:

scope → programme (build baseline) → risk (populate initial register)
→ cost (set budget baseline) → hse (prepare safety plan)
→ report (set up reporting template) → orchestrator (initialise state snapshot)

REPORTING cycle (weekly/monthly):

programme (progress % this period) → cost (spend vs. budget)
→ risk (top risks this period) → quality (open NCRs)
→ hse (incidents / observations) → report (compile and issue)

Phase 3 — Proactive Surfacing

At the start of every session, before processing any new input, scan the project state and surface anything overdue or at risk:

PROACTIVE ALERTS:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[🔴 IMMEDIATE]  RFI-007 — response overdue by 5 days, contractor claiming extension of time
[🟡 THIS WEEK]  Monthly progress report due in 2 days
[🟡 THIS WEEK]  Risk R-04 (foundation bearing capacity) — mitigation action overdue
[🔵 LOG]        Invoice PRJ/INV/2026/003 — 14 days since issue, no payment received
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Severity thresholds:

  • 🔴 IMMEDIATE — contractual deadline today or passed; safety event; HIGH risk materialising
  • 🟡 THIS WEEK — deadline within 7 days; at-risk milestone; open NCR >14 days
  • 🔵 LOG — informational; no immediate consequence but needs attention

Phase 4 — Session Close

At the end of every session, update the project state snapshot:

  1. Mark completed items closed
  2. Log new items opened
  3. Update programme and budget status
  4. Set next proactive alert triggers
  5. Capture any new pattern or lesson from this session in the project's own notes for future reference
SESSION CLOSE LOG:
  Date: [date]
  Items resolved this session: [N]
  New items opened: [N]
  State changes: [phase change / programme status change / budget status change]
  Skills invoked: [list]
  Lessons captured to skillify: [yes / no]
  Next session priority: [top item from proactive alerts]

Escalation Protocol

Some situations require escalation outside the skill system to [PM]'s direct judgment. Flag these immediately:

SituationEscalation
Potential contractual claim by contractor[PM] + legal review before any response
HSE incident with injury or fatality[PM] + client notification within 24 hours + regulatory
Discovered latent defect with structural implication[PM] sign-off required before any communication
Budget overrun exceeding 10% of contract value[PM] + client notification
Scope dispute with no agreed variation order[PM] + written record of all positions
Suspected fraud, corruption, or bid manipulation[PM] + legal + client
ESCALATION FLAG:
  Situation: [description]
  Reason for escalation: [why this cannot be handled by skill routing alone]
  Immediate action required: [what [PM] must do before anything else]
  Deadline: [if any]

Inter-skill Communication Protocol

When the orchestrator chains skills, it passes a context baton — a brief handoff note so each skill knows what came before:

CONTEXT BATON:
  From skill:       [sending skill]
  To skill:         [receiving skill]
  Project:          [name]
  Trigger event:    [what happened]
  Prior output:     [key finding or decision from sending skill]
  What is needed:   [specific question or action for receiving skill]
  Constraints:      [time / cost / contractual limits that apply]

The receiving skill reads the baton before acting. Nothing is repeated. Nothing is lost between skills.

示例提示词

现场又出了个问题,帮我判断这应该归到哪个管理流程处理。

所属插件

建筑学与土木工程面向建筑与土木研究和设计:场地分析与方案设计、Revit/AutoCAD/Rhino-Grasshopper 与 OpenBIM-IFC、机电与结构协调、消防与无障碍、围护结构与日照能耗、造价与工程量,以及土木工程项目的进度、质量、安全、风险与 RFI 管理。

安装该插件会一并获得同领域的 44 个 Skill / MCP。

同插件的其他科研 Skill

常见问题

土木项目管理总调度能做什么?

Classifies incoming civil-engineering PM events and routes each to the matching cost, programme, risk, quality, HSE, RFI, or report skill. Use as the entry point for project management requests。

如何安装土木项目管理总调度?

在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「土木项目管理总调度」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。

土木项目管理总调度需要哪些权限?

该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。

土木项目管理总调度经过官方审核吗?

是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。