Home Renovation

Setup

On first use, read setup.md for integration guidelines. Create ~/home-renovation/ if it doesn't exist.

When to Use

User plans a home renovation or remodel. Agent tracks budgets, timelines, and contractor coordination. User needs help evaluating quotes, planning phases, or managing multiple trades.

Architecture

Memory lives in ~/home-renovation/. See memory-template.md for structure.

~/home-renovation/
├── memory.md          # Status + active projects overview
├── projects/          # Per-project details and tracking
│   └── {project}.md   # Budget, timeline, contractors, notes
└── archive/           # Completed projects

Quick Reference

Core Rules

1. Project-Centric Memory

Each renovation gets its own file in projects/. Track:

• Budget: original estimate vs actual spend
• Timeline: planned vs actual dates
• Contractors: who, contact, status, notes
• Decisions: what was decided and why

2. Budget Reality Check

When user shares a quote or estimate:

• Ask square footage and scope details
• Compare to typical ranges (see projects.md)
• Flag if significantly above/below normal
• Never guarantee prices — always "typically ranges from..."

3. Phase-Based Planning

Renovations follow a sequence. See phases.md for details:

1. Planning & permits
2. Demolition
3. Structural/rough-in (electrical, plumbing, HVAC)
4. Insulation & drywall
5. Finishes (paint, flooring, fixtures)
6. Final inspection & punch list

Wrong order = costly rework. Always verify sequence before starting.

4. Contractor Coordination

When multiple trades involved:

• Confirm who handles permits
• Establish communication expectations
• Document verbal agreements immediately
• Track payment schedule vs work completed

5. Scope Creep Defense

Every change request:

• Get written quote before approving
• Update budget tracker
• Recalculate remaining contingency after each approved change order
• Assess timeline impact
• Document decision and rationale

6. Decision Documentation

For every major decision, record:

• What options were considered
• Why this option was chosen
• Cost and timeline impact
• Date decided

This prevents revisiting decisions and provides context for future projects.

7. Progress Updates

When user mentions progress:

• Update project timeline
• Check if on budget
• Note any issues or delays
• Celebrate completed milestones

Common Traps