Evaluate tabulated subcontractor bids against specs and drawings — scope gap analysis, exclusion risk scoring, award recommendation. Triggers: 'evaluate bids', 'bid evaluation', 'lowest responsible bidder'.
日本語の概要は準備中です。原文の説明を表示しています。
Split a bound drawing set PDF into individual sheet PDFs. Extracts sheet numbers from title blocks via vision, renames files. Triggers: 'split drawings', 'break up the drawing set', 'separate sheets'. Run after /project-setup.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Splits a bound drawing set PDF into individual page PDFs. Mirrors what spec-splitter does for specifications.
Run after /project-setup identifies bound drawing sets. Produces split PDFs and sheet_index.yaml consumed by /schedule-extractor and all drawing analysis skills.
This is valuable for:
Sheet Split Progress:
- [ ] Step 1: Check if drawings are already split
- [ ] Step 2: Locate the bound drawing set
- [ ] Step 3: Split into individual page PDFs
- [ ] Step 4: Extract sheet numbers from title blocks
- [ ] Step 5: Rename files with sheet number + title
- [ ] Step 6: Update project context
- [ ] Step 7: Write graph entry (AgentCM only)
Look for individual sheet PDFs. Drawings are already split if:
.construction/index/sheet_index.yaml exists with individual sheet entries and file paths point to split PDFsA-1.1 - FLOOR PLAN.pdf)sheet_index.yaml exists in the drawings directoryIf already split, report the count and skip. If AgentCM has the sheet index but files haven't been physically split on disk, offer to split using the existing metadata for naming.
Search the project directory for ALL PDFs that are drawings. Many projects have multiple drawing PDFs:
Search in:
drawings/, plans/, 01 - Drawings/, or similar (case-insensitive)Process EACH PDF found. All split pages go to the same sheets/ output directory.
If the user specifies a single file (/sheet-splitter path/to/specific.pdf), process only that file.
Run the split script on each drawing PDF found:
"${CLAUDE_PLUGIN_ROOT}/bin/construction-python" "${CLAUDE_SKILL_DIR}/scripts/split_drawing_set.py" \
"{drawing_set.pdf}" \
--output-dir "{drawings_directory}/sheets"
The script splits each page into its own PDF: page_001.pdf, page_002.pdf, etc. It does NOT attempt to read sheet numbers — that's unreliable across different title block formats.
After splitting, read each page to identify sheet numbers and titles:
Use PDF bookmarks and the title-block text layer only as candidates — they are often abbreviated or stale (e.g. a bookmark "Site Grading Plan" on a sheet printed "Proposed Site Plan"). The printed title block wins. Read the title block by vision whenever there is no candidate, the candidate disagrees with the title-block text, or the sheet number carries a suffix (e.g. C9.04H, K-1.1).
"${CLAUDE_PLUGIN_ROOT}/bin/construction-python" "${CLAUDE_PLUGIN_ROOT}/scripts/pdf/rasterize_page.py" "page_NNN.pdf" 1 --dpi 200 --output tb.png
Use vision on the rasterized title block: "Read the title block on this construction drawing. What is the sheet number and sheet title?"
Rename the file: page_001.pdf → A-1.1 - FLOOR PLAN.pdf
Update sheet_index.yaml with the identified sheet number, title, and discipline. When a bookmark title differs from the printed title, keep it as bookmark_title.
Title blocks vary significantly across firms — they can be on the east side, south side, or bottom-center. Some use VA standard forms, some use firm-specific formats. Vision handles all these variations.
After identifying all sheets, write {drawings_directory}/sheets/sheet_index.yaml (shown below). Never write .construction/index/ — that folder belongs to AgentCM; only read it.
sheets/
A-1.1 - FLOOR PLAN.pdf ← renamed by Claude via vision
A-2.1 - ELEVATIONS.pdf
S-1.1 - FOUNDATION PLAN.pdf
page_006.pdf ← could not read title block
...
sheet_index.yaml
After splitting and identifying, update .construction/skills/project_context.yaml with:
documents.drawing_count: number of sheetsdocuments.disciplines: list of unique discipline prefixes foundIf AgentCM is present (.construction/project.yaml exists), write a graph entry:
"${CLAUDE_PLUGIN_ROOT}/bin/construction-python" "${CLAUDE_PLUGIN_ROOT}/scripts/graph/write_finding.py" \
--type "drawings_split" \
--title "Drawing set split: {N} sheets from {source_pdf}" \
--data '{"sheet_count": N, "source_pdf": "...", "identified_count": M, "unidentified_count": K, "disciplines": ["A","S","M","E"]}'
Without AgentCM, skip — the sheet_index.yaml serves as the local record.
When a project has multiple drawing set PDFs (e.g., Architectural, MEP, Civil as separate files), use the source PDF name as a subdirectory to avoid filename collisions:
sheets/
Architectural_Bid_Set/
page_001.pdf ... page_050.pdf
MEP_Bid_Set/
page_001.pdf ... page_030.pdf
sheet_index.yaml ← merged from all sets
Pass --output-dir "{drawings_directory}/sheets/{source_pdf_stem}" to the split script for each set. The sheet_index.yaml merge logic combines entries from all subdirectories into a single index.
Report to user: number of pages split, how many identified via vision, output location.
Never overwrite existing split sheet PDFs. If sheets/ directory already contains files, check for conflicts before writing. The sheet_index.yaml merge uses additive logic — existing entries are preserved.
Allowed scripts — exhaustive list. Only execute these scripts during this skill:
scripts/split_drawing_set.py — split bound PDF into per-page PDFs${CLAUDE_PLUGIN_ROOT}/scripts/pdf/rasterize_page.py — rasterize PDF pages for vision identification${CLAUDE_PLUGIN_ROOT}/scripts/graph/write_finding.py — graph entry (Step 7)まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Evaluate tabulated subcontractor bids against specs and drawings — scope gap analysis, exclusion risk scoring, award recommendation. Triggers: 'evaluate bids', 'bid evaluation', 'lowest responsible bidder'.
日本語の概要は準備中です。原文の説明を表示しています。
Extract data from subcontractor bid PDFs and produce a comparison spreadsheet. Feeds into /bid-evaluator. Triggers: 'tabulate bids', 'bid comparison', 'compare bids', 'buyout analysis', 'bid tab'.
日本語の概要は準備中です。原文の説明を表示しています。
Scope-specific code gap analysis — extracts referenced codes from project docs, researches what should apply, surfaces the delta. Triggers: 'code research', 'what codes apply', 'code check', 'ADA requirements', 'egress'.
日本語の概要は準備中です。原文の説明を表示しています。
Operating guide for construction project documents — load before reading drawings, specs, schedules, RFIs, submittals or bids. Data-access rules (never read PDFs directly; rasterize first), AgentCM graph-guided vision, drawing and cross-reference conventions, document precedence. Triggers: 'construction project', 'drawings', 'specs', 'sheet', 'RFI', 'submittal'.
日本語の概要は準備中です。原文の説明を表示しています。
Construction document review with PE judgment — RFI research, submittal analysis, coordination checking, scope gap detection. Use when reviewing drawings, specs, submittals, or RFIs. Triggers: 'review', 'coordination', 'what's missing'.
日本語の概要は準備中です。原文の説明を表示しています。
Set up a construction project — inventories files, classifies drawings/specs/schedules/registers, detects AgentCM mode, appends construction context to CLAUDE.md. Triggers: 'set up project', 'construction setup', 'classify documents'.
日本語の概要は準備中です。原文の説明を表示しています。