科研 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.
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:
| Code | Type | Description |
|---|---|---|
| SITE-ANOMALY | Site defect or anomaly | Unexpected ground conditions, structural finding, material failure |
| SITE-PROGRESS | Progress update | Work completed, milestone achieved, activity started |
| SCOPE-CHANGE | Scope event | Client instruction, design change, unforeseen work |
| COST-EVENT | Cost event | Variation claim, dayworks, price adjustment, invoice |
| SCHEDULE-EVENT | Schedule event | Delay, acceleration, programme revision request |
| RISK-EVENT | Risk materialising | A risk on the register is happening or has happened |
| QUALITY-EVENT | Quality failure | NCR raised, inspection failed, material rejected |
| HSE-EVENT | Safety or environment | Incident, near-miss, unsafe condition, environmental release |
| DESIGN-EVENT | Design issue | Drawing error, RFI needed, design clarification required |
| CLIENT-COMMS | Client instruction or query | Letter, email, meeting outcome needing response or action |
| CONTRACTOR-COMMS | Contractor query or notice | Claim notice, programme submission, approval request |
| SIGN-OFF | Professional certification | Report, certificate, adequacy letter requiring issue |
| REPORTING | Reporting due | Weekly/monthly report, board update, regulatory submission |
| PLANNING | Planning request | New task, WBS item, resource plan, baseline update |
| CLOSEOUT | Project close | Handover, punch list, as-builts, DLP management |
| GENERAL | Unclassified | Route 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
| Code | Primary Skill | Notes |
|---|---|---|
| SITE-ANOMALY | investigate | Iron law: root cause before any instruction |
| SITE-PROGRESS | programme | Update schedule, check critical path impact |
| COST-EVENT | cost | Log variation, update forecast, flag if threshold breached |
| SCHEDULE-EVENT | programme | Delay analysis, recovery options, notify if contractual |
| RISK-EVENT | risk | Update register, escalate if HIGH/CRITICAL |
| QUALITY-EVENT | quality | Open NCR, assign corrective action, track to close |
| HSE-EVENT | hse | Classify incident, initiate reporting chain |
| DESIGN-EVENT | rfi | Open RFI, route to designer, track response |
| CLIENT-COMMS | report | Log, draft response, assign action |
| CONTRACTOR-COMMS | report | Log, classify (routine / contractual notice), action |
| REPORTING | report | Generate report from current project state |
| PLANNING | programme | WBS update, resource plan, baseline |
| CLOSEOUT | retrospective notes + document-release | Run 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:
- Mark completed items closed
- Log new items opened
- Update programme and budget status
- Set next proactive alert triggers
- 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:
| Situation | Escalation |
|---|---|
| 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.
示例提示词
现场又出了个问题,帮我判断这应该归到哪个管理流程处理。
所属插件
安装该插件会一并获得同领域的 44 个 Skill / MCP。
同插件的其他科研 Skill
- 建筑图纸矢量生成Produces coordinated architectural drawings (plans, sections, elevations, SVG/DXF) from structured specs with layer and standard checks. Use when drafting or generating drawing sets.
- 建筑项目全流程协调Coordinates end-to-end AEC work across briefing, design, BIM/CAD production, and handover by routing to specialist skills. Use for ambiguous or multi-discipline AEC tasks.
- 建筑任务书空间排布Converts briefs into traceable room programs, area schedules, adjacency logic, and requirement matrices. Use for space planning, briefing, or program validation.
- 建筑成果红队复核Independently challenges an architecture deliverable for hidden assumptions, coordination gaps, and unsupported claims before submission. Use for final adversarial review before issue.
- 建筑面积工程量核算Calculates and audits architectural areas, room schedules, quantities, and takeoffs with explicit units and measurement basis. Use for quantity reconciliation and takeoff sanity checks.
- AutoCAD DWG制图工作流Plans and reviews safe AutoCAD DWG workflows: layers, blocks, xrefs, layouts, plotting, and AutoLISP/.NET automation. Use for AutoCAD-specific drafting and DWG package preparation.
- BIM执行计划编制Drafts and reviews ISO 19650 BIM Execution Plans and Exchange Information Requirements: roles, CDE workflow, LOIN, and federation strategy. Use before modeling starts on a BIM-delivered project.
- 建筑围护结构性能设计Develops and reviews facade, roof, and foundation envelope strategies for thermal, water, air, and acoustic performance. Use for assembly design, condensation risk, and envelope QA.
- CAD/BIM自动化工作流Plans safe, least-destructive automation of CAD/BIM workflows such as batch edits and model-data extraction across Revit, IFC, DWG, and DXF. Use for repetitive model or document tasks.
- 建筑场地土木协调Coordinates architecture with civil/site engineering: grading, earthworks, access, drainage, utilities, and Civil 3D workflows. Use for site grading concepts and civil-architectural handoff.
- 建筑概念方案评审Critiques architectural concepts and compares design options against stated project goals across program, site, climate, and constructability. Use for design critique or option comparison.
- 建筑概念与方案设计Generates and develops concept and schematic design options (parti, massing, blocking, circulation, floor plans) from a validated brief. Use for early design option generation and comparison.
- 施工阶段行政管理支持Supports construction-phase administration: RFIs, submittals, site observations, change tracking, and punch lists. Use during tender clarification, construction, and closeout.
- 施工图文件集编制Develops and coordinates construction-document sets including sheet registers, schedules, details, and issue packages. Use for technical design production and permit or tender drawing sets.
- 土木项目成本管理Manages civil-engineering project budgets: contract sum, variation log, forecast final account, cashflow, and invoice register. Use for cost events such as variations, invoices, or budget review.
- 建筑造价与价值工程Supports architectural cost planning, option comparison, and value engineering using traceable quantities and cost sources. Use for early cost plans, budget reconciliation, and VE workshops.
- 项目文件发布核查Audits live civil-engineering project documents after a milestone to flag drift between proposed, contracted, and delivered work. Use after report issue or scope change to update project records.
- 建筑图纸质量检查QA checks architectural drawing sets for cross-sheet coordination, annotation, dimension, and revision issues. Use for reviewing PDFs, exported drawings, or issue sets before release.
- 岩土勘察与地基评估Plans and interprets geotechnical site investigations for foundation design: desk study, borehole/CPT interpretation, and bearing capacity checks. Use before foundation or earthworks design.
- 竣工移交与运维协调Coordinates architectural handover, O&M manuals, asset data, defects, and post-occupancy evaluation. Use from practical completion through building operation and facilities handoff.
- 历史建筑保护评估Researches heritage significance, listing status, and conservation constraints for existing buildings, and structures conservation-led options. Use for listed or historic buildings.
- 土木项目安全环保管理Manages civil-engineering health, safety, and environment: safety plans, incident register, method statement review, and statutory reporting. Use for any HSE incident, near-miss, or safety review.
- 室内装修布局设计Develops interior and fit-out layouts, furniture zoning, RCP concepts, finish strategies, and fit-out documentation. Use for workplace, residential, retail, or hospitality interior projects.
- 结构与无损检测根因调查Runs a systematic root-cause investigation protocol for structural and NDT findings before any remediation is proposed. Use when a defect, anomaly, or unexplained inspection finding is reported.
常见问题
土木项目管理总调度能做什么?
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 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。