科研 Skill

项目文件发布核查

document-release

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.

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

SKILL.md

Document Release

Post-delivery document currency audit for [Your Organisation]. Scans all live project documents after a milestone issue and flags any that have drifted from the actual scope, findings, or programme.

Adapted from the gstack /document-release methodology for the firm engineering practice.

RULE: Every issued report or milestone creates a document debt — the gap between what the project file says and what actually happened. This skill clears that debt before it compounds into a contractual or professional liability.


When to Run

Run after any of these events:

EventWhy Docs Drift
Final report issuedFindings may differ from method statement; scope exclusions may have changed
Interim / preliminary report issuedProgramme, scope, and fee records need to reflect partial delivery
Variation order agreedContract, proposal scope, and programme all need updating
Scope reduced (client decision)Deliverable register, fee schedule, and programme need to reflect reduction
Inspection completed (but report pending)Field data may have revealed conditions not anticipated in the method statement
Project paused or suspendedStatus must be recorded in all documents before file is archived
Project handed over to another engineerEvery document must reflect current state for continuity

Phase 1 — Document Inventory

List all live project documents. For each project, the standard set is:

DocumentRefStatus
ProposalPRJ/PROP/YYYY/NNN[current / stale / superseded]
Contract / LOAPRJ/CON/YYYY/NNN[current / stale / superseded]
Method StatementPRJ/MS/YYYY/NNN[current / stale / not produced]
Programme / Schedule—[current / stale / not produced]
Transmittal RegisterPRJ/LTR/YYYY/NNN[current / stale / not produced]
Deliverable Register—[current / stale / not produced]
Field Data Records—[filed / unfiled / missing]
Final Report(s)PRJ/RPT/YYYY/NNN[issued / draft / pending]
Invoice Record—[current / outstanding items]

Flag any document that is absent and should exist for this project type.


Phase 2 — Drift Detection

For each document in the inventory, check for drift against the current project reality.

2.1 Scope Drift

Compare the scope of work as stated in:

  • The proposal (what the firm offered to do)
  • The contract (what the firm was contracted to do)
  • The issued report (what the firm actually did)

Flag any discrepancy:

SCOPE DRIFT FLAG:
  Document: [name and ref]
  Stated scope: [what the document says]
  Actual delivery: [what was actually done]
  Drift type: [ADDITION / OMISSION / SUBSTITUTION]
  Action required: [update document / issue variation record / note in retro]

2.2 Findings Drift

Compare the findings, recommendations, or conclusions in:

  • The method statement (what the firm expected to find / how results would be reported)
  • The issued report (what the firm actually found)

Flag if:

  • The report contains findings not anticipated in the method statement (new defect types, access restrictions, additional elements inspected)
  • The acceptance criteria applied differ from those stated in the method statement

2.3 Programme Drift

Compare:

  • Proposed programme dates
  • Actual mobilisation, inspection, and report issue dates

Flag if actual dates differ from proposed by more than 14 days, and record the reason (client delay, the firm delay, external).

2.4 Fee Drift

Compare:

  • Contract fee (as executed)
  • Any variations agreed (verbal or written)
  • Invoices issued to date

Flag any uncontracted work performed but not invoiced, or any agreed variation without a formal variation order.


Phase 3 — Update Actions

For each drift flag, assign one of these actions:

ActionWhen to Use
AMEND — update the documentFactual error, administrative correction, minor addition
ISSUE VARIATION RECORD — create a brief variation noteScope addition or change agreed with client but not formally documented
NOTE IN RETRO — log in the project retrospective notes but do not amendInformational drift that doesn't affect contract or liability
ESCALATE — requires client discussion before any document changeDisputed scope, contradictory client instructions, potential claim
NO ACTION — drift is acceptable and documentedDeliberate deviation with client knowledge

Produce an action list:

DOCUMENT UPDATE ACTION LIST:
  Project: [name]
  Date: [date]

  1. [document ref] — [AMEND / VARIATION RECORD / RETRO NOTE / ESCALATE / NO ACTION]
     Reason: [one line]
     Owner: [PM]
     Due: [date]

  2. [document ref] — [action]
     ...

Phase 4 — Transmittal Register Update

After every report or document issue, the transmittal register must reflect:

FieldConfirm
Document title correct[ ]
Document reference correct[ ]
Revision number updated[ ]
Issue date recorded[ ]
Recipient confirmed[ ]
Method of transmission recorded (email / portal / hand)[ ]
Client acknowledgement / receipt recorded (if required)[ ]

If the transmittal register does not exist for this project, create it now using the project's standard document template or an available document-drafting tool.


Phase 5 — Archive Check

Before closing a project file:

  • All field data (photos, raw NDT readings, calibration records) filed in the project folder with legible naming convention
  • All client communications (emails, meeting notes, instructions) filed
  • Final report in PDF/A format for long-term archiving
  • Equipment calibration certificates for the inspection period filed (these support the report's legal validity)
  • Any [National Regulator] or regulatory submission receipts filed
  • Invoice and payment records reconciled

Output — Document Release Note

PM DOCUMENT RELEASE NOTE
Ref: PRJ/DRN/[YYYY]/[NNN]
Date: [date]
Project: [name]
Client: [name]
Trigger event: [what just happened — report issued, variation agreed, etc.]

DOCUMENTS REVIEWED:   [N]
DRIFT FLAGS RAISED:   [N]
ACTIONS ASSIGNED:     [N]

OPEN ACTIONS:
[list from Phase 3]

ARCHIVE STATUS:       [COMPLETE / INCOMPLETE — items outstanding]

Prepared by: [PM]

File this note in the project folder alongside the documents it covers.

示例提示词

报告刚发出去,帮我核查一下所有在用文件是否反映实际交付内容。

所属插件

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

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

同插件的其他科研 Skill

常见问题

项目文件发布核查能做什么?

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。

如何安装项目文件发布核查?

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

项目文件发布核查需要哪些权限?

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

项目文件发布核查经过官方审核吗?

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