科研 Skill
项目范围核查
scope
Interrogates assumed project scope before a civil-engineering proposal is drafted, surfacing the real problem and scope options. Use before quoting, proposing, or committing to a scope of work.
SKILL.md
Scope Check
Pre-proposal interrogation protocol for [Your Organisation]. Forces the real problem to the surface before scope, fee, or methodology is committed.
Adapted from the gstack /office-hours methodology for the firm engineering and
inspection practice.
RULE: No proposal draft, no fee estimate, no methodology selection — until this interrogation is complete. Scoping before framing is how the firm ends up underpaid for overdelivery.
Phase 1 — Receive and Restate
When the user describes a potential project or client request:
- Restate what you heard in one sentence — not what was said, but what was meant: the problem the client has, not the service they asked for.
- Flag the gap between what the client asked for and what they actually need (if one exists).
Example:
Client asked for: "Tank calibration for two tanks" What they actually need: "A defensible volumetric baseline for fiscal custody transfer compliance — calibration is the method, not the goal"
This reframe may change the scope, the deliverable, and the fee.
Phase 2 — Six Forcing Questions
Work through these in order. Ask only the ones that are unanswered from the context already provided. Do not ask questions the user has already answered.
Q1 — What is the actual consequence if this is not done?
Not the project rationale — the real downstream consequence for the client.
- Is this regulatory / compliance-driven?
- Is it insurance / underwriting-driven?
- Is it a precondition for another project?
- Is the client under pressure from a principal (operator, JV partner, bank)?
This determines urgency, leverage, and whether the firm is solving a pain or a preference.
Q2 — What does "success" look like to the client — in their words?
Not what the deliverable is, but what the client will say when the job is done well.
- A signed-off report? A passed inspection? An insurer satisfied? A claim dismissed? A plant back online?
- If you don't know this, you cannot scope the right deliverable.
Q3 — What has already been tried or done?
- Prior inspections, assessments, repairs?
- Other firms engaged previously?
- What did they miss, or why was the client unsatisfied?
- Are there existing drawings, reports, or data available?
This prevents the firm from re-doing work and charging for it, and may reveal why the client is coming to the firm specifically.
Q4 — What is the actual constraint — time, access, or budget?
Pick the binding one.
- If time is the constraint: methodology must be fast; deliverable may be preliminary.
- If access is the constraint: methodology must fit the access window; mobilisation timing matters more than fee.
- If budget is the constraint: scope must be reduced to fit, or client must be educated on minimum viable scope for defensible output.
Do not guess. Ask directly if not already known.
Q5 — Who else is quoting, and on what basis?
- Is this a competitive tender or a direct award?
- Are competitors quoting the same scope, or a different interpretation?
- Is there a BOQ / scope document, or is each firm defining its own scope?
This determines whether to price to win, price for margin, or decline.
Q6 — What is the riskiest assumption in the current scope framing?
The thing that — if wrong — would make the proposal embarrassing or loss-making.
- Assumed access that may not exist?
- Assumed data that the client may not have?
- Assumed structural condition that may require additional investigation?
- Assumed regulatory pathway that may not apply?
Name it explicitly before scoping.
Phase 3 — Reframe and Alternatives
After the six questions, generate:
3.1 Reframed Problem Statement
One paragraph: what is the firm actually being asked to solve, in engineering terms, not in service-catalogue terms.
3.2 Three Scope Options
Present three interpretations of what the firm could deliver:
| Option | Scope | Fee Signal | Risk |
|---|---|---|---|
| Narrow | Minimum defensible deliverable that answers the client's core question | Lowest | Scope creep risk if client expects more |
| Standard | Full scope as originally framed | Mid | Current baseline |
| Expanded | Broader scope that solves the underlying problem, not just the stated request | Higher | Client may not have budget; but this is the right answer |
Recommend one. Justify it in one sentence.
3.3 Scope Exclusions (Draft)
List 3–5 items that are explicitly out of scope under the recommended option. These go into the proposal to prevent scope creep.
3.4 Key Assumption Register (Draft)
List 3–5 assumptions the firm is relying on. Each becomes a caveat in the proposal.
Phase 4 — Methodology Check
Once scope is agreed, challenge the methodology:
- Is the proposed method the most defensible for the client's purpose (fiscal, regulatory, insurance, litigation)?
- Is it the most efficient given the access and timeline constraints?
- Is there a better method the firm could offer that competitors may not (SHM, digital twin, integrated NDT + structural analysis)?
- Does the method produce output in the client's required format (API standard, [National Regulator] format, operator template)?
Flag any mismatch between method and purpose before the proposal is drafted.
Output — Scope Brief
At the end of this interrogation, produce a one-page scope brief:
PM SCOPE BRIEF
Ref: PRJ/SB/[YYYY]/[NNN]
Date: [date]
Client: [name]
Project: [working title]
REAL PROBLEM:
[one paragraph reframe]
RECOMMENDED SCOPE OPTION: [Narrow / Standard / Expanded]
RATIONALE: [one sentence]
KEY SCOPE EXCLUSIONS:
1.
2.
3.
KEY ASSUMPTIONS:
1.
2.
3.
RISKIEST ASSUMPTION: [from Q6]
BINDING CONSTRAINT: [time / access / budget]
RECOMMENDED NEXT STEP: [draft proposal / request more info / decline / site visit first]
Prepared by: [PM]
This brief feeds directly into proposal drafting (via the project's document-drafting tool or template). Do not begin the proposal until this brief is reviewed and confirmed.
示例提示词
客户想加一项检测服务,帮我先核查清楚这算不算在范围内。
所属插件
安装该插件会一并获得同领域的 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.
常见问题
项目范围核查能做什么?
Interrogates assumed project scope before a civil-engineering proposal is drafted, surfacing the real problem and scope options. Use before quoting, proposing, or committing to a scope of work。
如何安装项目范围核查?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「项目范围核查」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
项目范围核查需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
项目范围核查经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。