Skip to content

dleerdefi/claude-code-construction / skills/rfi-drafter

rfi-drafter

Verified

Draft RFIs and manage the ambient issue registry. Reviews issues surfaced by other skills, escalates to formal RFIs. Triggers: 'draft RFI', 'write RFI', 'drawing conflict', 'review issues', 'issue queue'.

references/research-checklist.md

View on GitHub
# Research Checklist — Pre-Draft Investigation

## Purpose

Every RFI must be backed by research. An RFI that asks a question
already answered by the documents wastes the design team's time and
damages the GC's credibility. This checklist ensures systematic
investigation before any draft is written.

## Mandatory Checks (every RFI)

### 1. Primary Source Review
- Read the specific area on the source sheet at the identified location

- Rasterize the sheet and crop to the conflict zone with the two commands in
  SKILL.md Step 2 (they carry the plugin path; this file does not), then read
  the crop with vision
- Read title block for revision date and project info

**With AgentCM** (`.construction/project.yaml` exists), also read the sheet's
text in `.construction/sheets/<sheet>.tsv` (each line with its box, view and
zone) and its accepted callouts and tags in `.construction/sheets/<sheet>.groups.tsv`.

### 2. Related Views
- Check all details, sections, and elevations that reference or are
  referenced from the conflict area
- Large-scale drawings govern small-scale — if a detail shows
  different info than the plan, note which governs

**With AgentCM**: search `.construction/xrefs.tsv` for the sheet: lines starting
with `{sheet}` are references from it, lines with a tab, `{sheet}` and a tab
elsewhere are references to it.

**Without AgentCM**:
- Search the source sheet visually for detail callouts, section marks, and elevation markers
- Rasterize each referenced sheet and read the referenced view

### 3. Specification Review
- Identify the relevant spec section(s) for the scope in question
- Check Part 1 (General), Part 2 (Products), and Part 3 (Execution)
  for any language addressing the condition
- Check Division 01 general requirements for any overriding provisions

**With AgentCM**: Find the section in `.construction/INDEX.md` and read its text in `.construction/specs/<section>.txt` (`08 71 00` is `08-71-00.txt`; each line starts with its page). Only for a manual INDEX.md lists under "Spec manuals not read", read spec-splitter's `.construction/skills/spec_text/` instead.

**Without AgentCM**: Search the project directory for spec PDFs. Use pdfplumber to extract text from relevant sections.

### 4. Addenda and ASI Check
- Review all addenda issued after the original drawing date
- Check if any ASI (Architect's Supplemental Instruction) addresses
  this condition
- If an addendum supersedes the drawing/spec in question, the issue
  may already be resolved — inform the user, no RFI needed

**With AgentCM**: Search `.construction/index/file_manifest.yaml` for `type: addendum` or `type: asi` files.

**Without AgentCM**: Search the project directory for addenda/ASI documents. Read title pages for affected sheets/sections.

### 5. General Notes Review
- Check the general notes sheet(s) for the relevant discipline
- Many apparent conflicts are addressed by general notes that
  establish default conditions or clarify conventions

**With AgentCM**: find the sheets titled GENERAL NOTES in `.construction/INDEX.md`'s
Drawing sheets table and read their `.construction/sheets/<sheet>.txt`.

**Without AgentCM**: Check `.01` sheets for each discipline (e.g., A-0.01, S-0.01, M-0.01) — these typically contain general notes.

### 6. Existing RFI Check
- If an RFI log is available, search for existing RFIs addressing
  the same condition, area, or spec section
- If a prior RFI response resolves this issue, inform the user
  and reference the prior RFI number
- If a prior RFI is related but doesn't fully resolve, reference
  it in the new RFI

Also check the issue registry with the `issue_manager.py list --table` command
in SKILL.md (Reviewing the Issue Queue).

**With AgentCM**: Search `.construction/index/file_manifest.yaml` for `type: rfi` files.

**Without AgentCM**: Search the project directory for RFI logs (Excel/PDF). Ask the user if an RFI log exists.

## Conditional Checks (when applicable)

### 7. Cross-Discipline Check
When the issue spans multiple disciplines:
- Pull the same area on each discipline's drawings
- Note discrepancies in dimensions, element locations, or clearances
- Identify which discipline's drawing likely governs

### 8. Code Check
When the issue may involve building code compliance:
- Identify the applicable code section (IBC, ADA, NFPA, local)
- State the code requirement alongside the drawing condition
- Do NOT assert a code violation — frame as "appears to conflict
  with [code section], please clarify"

### 9. Manufacturer Data Check
When the issue involves product compatibility or installation:
- Check submitted/approved product data if available
- Reference manufacturer's published installation requirements
- Note if the specified product can physically accommodate the
  shown condition

### 10. Schedule Cross-Reference
When the issue relates to quantities or locations:
- Check the relevant schedule (door, fixture, finish, equipment)
- Note any discrepancies between schedule data and drawing
- Schedules often contain notes that clarify apparent conflicts

## Research Outcome Decision

After completing research, one of three outcomes:

**Issue confirmed** → Proceed to draft. Document all research
findings as evidence in the RFI description.

**Issue resolved by existing document** → Inform the user which
document resolves it (addendum #, RFI response #, general note).
No RFI needed. Optionally log as resolved issue in registry.

**Issue unclear** → Present findings to user. The user may still
want to draft an RFI for clarification even if the evidence is
ambiguous — that's their judgment call.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall