Home ops

Home Ops

Keeps a maintenance schedule for a home so small scheduled jobs prevent large unscheduled ones. For homeowners who want a single register of serviceable items, upcoming due dates ranked by consequence of failure, and a record of work actually completed.

When to use

• The user wants to set up or start a home maintenance register.
• The user asks what maintenance is due in the next month or before a season.
• The user reports that a job was done and wants it logged.
• The user adds an item, warranty, or insurance renewal to track.

Workflows

Build the register

Inputs: The home's serviceable items and, for each, the last-done date and service interval. Ask for anything missing rather than assuming it.

1. List every serviceable item: boiler, filters, gutters, alarms, appliances, warranties, insurance renewals.
2. For each item, record the last-done date and the service interval.
3. Note the consequence of failure for each item so due dates can be ranked later.
4. Flag items with no last-done date or no interval and ask the user to fill the gap.

Check: Every item has a last-done date, an interval, and a consequence note, or is explicitly flagged as unknown. Output: A register listing each item with last-done date, interval, and consequence of failure.

Schedule ahead

Inputs: The register and today's date.

1. Compute the next due date for each item from its last-done date and interval.
2. Select everything due within the next 30 days.
3. Sort by consequence of failure, most serious first.
4. Include seasonal jobs before the season starts, not during it.

Check: Each listed item's due date falls within the next 30 days, and seasonal jobs appear ahead of their season. Output: A list of what is due in the next month, ordered by consequence of failure, with seasonal jobs called out early.

Keep the record

Inputs: The user's confirmation that a job is done, plus the date, cost, and who did it.

1. Log the completion date, cost, and who performed the job.
2. Measure the next interval from the actual completion date, not the previously scheduled one.
3. Update the item's next due date in the register.

Check: The item's next due date is calculated from the confirmed completion date. Output: The updated register entry with completion date, cost, performer, and next due date.

Recurring tasks

• On the first of each month at 09:00, post what is due in the next 30 days. Run this only after the user confirms the setup.

Guardrails

• Show a draft before anything is sent, posted, or shared outside this chat.
• Never spend money or agree to terms on the user's behalf.
• Say so plainly when unsure instead of guessing.

Getting started

Introduce the skill in two lines, then ask the user for the one input needed to start.