Skip to main content

itp-holdpoint-check

Build or check a construction ITP hold-witness-review pack against spec, drawings, and the planned activity including pre-pour and inspection records. Use when the user says ITP, hold point, witness point, inspection test plan, pre-pour, pre-cover, inspection checklist, or what records before we pour.

소스 정보

저장소
dgcruzing/construction-office-skills
최근 소스 활동
2026년 9월 30일 13:49
감지된 SKILL.md 언어
영어
스타
0
포크
0

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
3 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
itp-holdpoint-check
description
Build or check a construction ITP hold-witness-review pack against spec, drawings, and the planned activity including pre-pour and inspection records. Use when the user says ITP, hold point, witness point, inspection test plan, pre-pour, pre-cover, inspection checklist, or what records before we pour.
metadata
{"type":"workflow","version":"1.0","pack":"construction-office-skills","domain":"construction-quality"}
# ITP / hold-point check Quality gate before cover-up. The skill produces a checklist the inspector can stand on, not a quality essay. ## Inputs required - Activity (e.g. ground slab pour, membrane, first-fix hydraulic, fire-stopping) - Spec section + drawing refs - Existing ITP if any - Who holds authority (builder QA / client / certifier / superintendent) - Planned date/time of the activity - Records already available (tickets, test results, photos, set-out) ## Point types (use these words only) - **H — Hold** — do not proceed until signed - **W — Witness** — invite the party; may proceed if they decline *in writing* - **R — Review** — document check, not necessarily on site - **S — Surveillance** — random / ongoing If the project ITP uses different letters, copy the project letters and map them once at the top. ## Refuse list - Do not invent spec clauses or acceptance criteria. Quote or mark UNKNOWN. - Do not waive a hold point. - Do not say "looks fine". Either the record exists or it is OPEN. - Do not mix trades in one ITP unless the user supplied a combined pack. - Do not sign. ## Method 1. Name the activity and the cover-up risk (what becomes inaccessible). 2. Build rows in process order — materials → set-out → prep → inspection → test → cover → as-built. 3. Each row needs — what / criteria / record / point type / who signs / status. 4. Status = `CLOSED` only if the user provided the record. Otherwise `OPEN` or `N/A`. 5. List **blockers** separately (missing ticket, expired cert, no reo inspection booked). 6. If no project ITP exists, draft a starter ITP and label it `DRAFT — not approved`. Load `references/typical-hold-points.md` only when the user has no ITP and needs a starter list. Prefer the project ITP always. ## Output Follow `assets/itp-checklist.md`. ``` HOLD POINT — not approved / not signed ``` ## Optional VET map Only if asked. Quality planning (ITP), assurance (hold points), control (records). No competency claim. ## Done when - Every row has point type + record type + signer role. - OPEN items are listed as blockers. - No invented criteria.
GitHub에서 보기