Adu Corrections Complete

ADU Corrections Complete

Overview

Generate the final response package for ADU permit corrections. This is the second skill in a two-skill pipeline:

1. adu-corrections-flow (Phase 1) — reads the corrections letter, builds the sheet manifest, researches state and city codes, views plan sheets, categorizes corrections, generates contractor questions. Produces research artifacts in a session directory.
2. adu-corrections-complete (this skill, Phase 2) — reads those research artifacts + contractor answers, generates all deliverables.

This skill runs as a cold start. It has no conversation history from Phase 1. Everything it needs is in the session directory files. The quality of its output depends entirely on the quality of those files — especially corrections_categorized.json, which contains the merged research findings.

Input: Session Directory

The session directory (e.g., correction-01/) must contain these files from Phase 1:

Reading Order

Read files in this order to build context efficiently:

1. corrections_categorized.json — read first, it's the backbone. Each item has its category, research context, and cross-referenced findings already merged.
2. contractor_answers.json — read second, map answers to items.
3. sheet-manifest.json — read third, for accurate sheet references.
4. corrections_parsed.json — read fourth, for original wording to preserve in the response letter.
5. Other files only if corrections_categorized.json doesn't have enough detail on a specific item — it usually does.

Output: Four Deliverables

1. response_letter.md

Professional letter from the contractor to the building department, addressing every correction item.

Structure:

# Response to Plan Check Comments
## [Review Round] — [Address]
### [Permit Number] | [Project Type]

Date / To / From / Re header

---

### [Section from original letter]

**Item [#] — [Summary]**
[Response addressing the correction with specific references]

...

---

**Summary of Sheet Revisions:**
| Sheet | Changes |

Rules:

• Address EVERY item — do not skip any, even procedural ones (Items 1, 2)
• Preserve the original correction wording — quote it or reference it clearly
• For items with contractor answers: incorporate the answer with code justification
  • Example: "Existing 4" ABS waste line serves 22 DFU. ADU adds 12 DFU. Combined 34 DFU is within the 216 DFU capacity of a 4" drain per CPC Table 702.1."
• For items without answers (skipped): mark as [TODO: description of what's needed]
• For auto-fixable items: state what was changed and on which sheet
• For professional items: state the scope and who will do the work
• Reference specific sheets from the manifest — never guess
• End with a summary table of sheet revisions
• Tone: professional, specific, respectful. This goes to a city plan checker.

2. professional_scope.md

Work breakdown grouped by professional, with enough detail that the designer/engineer can execute without re-reading the corrections letter.

Structure:

# Professional Scope of Work
## [Address] — [Permit Number]

---

## [Professional Name / Firm]
**Sheets:** [list]

### Required Actions
| Item | Sheet | Action | Contractor Input | Status |

### Key Specifications
[Detailed specs from contractor answers — dimensions, materials, elevations]

### Deliverables
- [ ] checklist items

---

## Per-Sheet Action Summary
| Sheet | Actions | Professional | Status |

Rules:

• Group by professional (Designer, Structural Engineer, HERS Rater, etc.)
• Extract professional names from the plan sheets if available (title block info in sheet observations)
• Include a Key Specifications section with contractor-provided details formatted for the designer
  • DFU justification note ready to paste onto Sheet A1
  • Grade elevation table with drops from finished floor
  • Patio dimensions for the structural engineer
• Mark status: READY (can proceed), PENDING (waiting on other items), FINAL STEP (stamps/signatures last)
• The per-sheet action summary at the bottom is the quick-reference — one row per sheet showing all work