Finishes Schedule Spec Check — Testing skill for Claude Code
Cross-check a Room Finishes Schedule against the Architectural Specification.
How to install Finishes Schedule Spec Check
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open hamzaabduljabbar/finishes-schedule-spec-check and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Finishes Schedule Spec Check does
Cross-check a Room Finishes Schedule against the Architectural Specification. Auto-detects BSB (per-code appendix) or US CSI (Div-XX sections) spec formats. Colour-coded Excel out, every finding traceable to a spec PDF page. A Claude skill.
Alternatives in Testing
- Deslop Reborn — One iteration of the IronClaw Reborn de-slop loop — take ONE Reborn crate, fan out parallel review sub-agents 12.6k ★
- L Debug Trace — Analytically debug issues by tracing data flow through code - no logs, no test-and-see 3k ★
- Factory — Dark Factory Mode - Spec-in, software-out autonomous pipeline 2.8k ★
README
Finishes Schedule ↔ Specification Cross-Check (a Claude skill)
Turn a **Room Finishes Schedule** and an **Architectural Specification** into a colour-coded Excel cross-check that flags every finish code as **Match / Mismatch (desc) / Code not in specs**. Two PDFs in, one workbook out.
A finishes coordinator normally does this by hand: for every room, look up each floor/wall/ceiling code, open the spec book to that code's page, and verify that the spec's intended room-type actually matches the room. On a 500-room tower with a 1,800-page spec, that's a week of billable time and a common source of last-minute RFIs. This tool does the first pass automatically.
What it does
- Reads two PDFs — the finishes schedule sheet(s) and the architectural specification. Text-only, no image recognition, no BIM required.
- Auto-detects the spec family — supports per-code appendix specs (each finish code has its own spec page — common on Middle East / UK / Aus-NZ projects) and US CSI-format Div-XX section specs. Picks the right pipeline automatically.
- Cross-checks every finish code — for each code in the schedule, finds its spec-side definition and checks that it agrees with how the drawing is using it. Same four flags in both modes, meaning adapts to the spec structure.
- Cites every finding — spec PDF page number and schedule sheet + room, so a reviewer can open the exact page and verify.
- Accounts for every room — rooms whose finishes are all N/A / BY TENANT / BY ID are listed on a separate "Deferred Rooms" tab, so nothing is silently dropped from the audit.
- Flags confidence implicitly by refusing to guess: when spec-anchor or column-layout detection is uncertain, the tool errors with an override hint instead of writing wrong data.
Quick start
py -m pip install -r requirements.txt
py scripts/engine.py \
--spec "path/to/Architectural Specification.pdf" \
--schedule-dir "path/to/schedule-folder" \
--proj
Related Skills
Autoconst Spec Compliance Claude
Cross-check a Revit model against its written CSI construction spec. Auto-indexes the spec into SQLite, auto-e
Halflife
Spaced-repetition study tracking where your coding agent runs the test and a script owns the schedule.
Axiom — Development Changelog
Purpose: Historical record of Axiom development milestones, TDD testing results, and architectural decisions.
Test Report
Generate test execution report in various formats
Std Builder
Generate STD (YAML + test stubs with PSE docstrings) from an existing STP file or a scenario list, then auto-r
Stp Builder
Generate a Software Test Plan (STP) from a Jira ticket, then auto-run review and refinement so the command fin
Related Agents
Tax Auditor
Reviews tax engine code and data like an auditor - money math, hard-coded numbers, rounding sites, trace compl
Bd Spec
Fills in the S3 system specification (spec.yaml). Queries knowledge to populate parameters, attaches provenanc
Osf Clean Room
Reads a feature inside a temp folder, extracts its behavior and test coverage as a source-free specification,