suggest-discards

Suggest discards

When to invoke

The user wants to know what to get rid of, asks "what should I throw out", or wants to start a decluttering pass.

Preconditions

Workspace exists and inventory/master.json has items. Otherwise prompt for setup-workspace / import-inventory.

Heuristics for "throw away" candidacy

Score each item against these signals (higher score = stronger discard candidate):

• Condition broken → strong candidate. poor → moderate.
• Obsolescence: technology more than ~10 years old with no current use (CRT monitors, mini-DV tapes, dead phones with no resale value), expired consumables, old cosmetics, expired food, expired medicines.
• Low value + low utility: est_value near zero AND no sentimental tag AND not actively used.
• Redundancy: more units than the household plausibly needs (e.g. 12 phone chargers, 5 frying pans).
• Damaged irreparably: notes mention "missing parts", "doesn't work", "leaks", "torn".
• Hazardous to keep: leaking batteries, mouldy items, anything flagged in notes as a safety issue.

Negative signals — do NOT recommend discarding if

• Tagged sentimental, heirloom, gift, keepsake.
• est_value is high (instead, route to identify-resale-targets).
• Likely donatable in good condition (route to identify-donation-targets).
• User has previously rejected it (track in analysis/.discard-rejections.json).

Output

Write <workspace>/analysis/discards.md with sections:

1. Strong candidates — score ≥ 0.8, with one-line reason each.
2. Worth considering — score 0.5–0.8.
3. Edge cases — items the agent wasn't sure about, with the question to resolve.

Each entry: - [item name] (id) — reason — location/box.

Also print the strong-candidates list to chat. Offer to:

• Pipe the list into generate-action-list for a printable CSV/PDF.
• Re-route specific items to identify-resale-targets or identify-donation-targets.