stack-auditlisted

# Stack Audit The failure this exists to prevent: **paying every month for a decision made once, on a tool nobody has opened since, because nobody put a date on revisiting it.** Subscriptions are the easiest spend in a business or a personal budget to lose track of, because the bill is the only thing that recurs. The decision to keep paying does not recur unless something forces it to. This skill forces it. --- ## What this needs **Minimum: a list of tool names from memory.** Nothing else required. The audit runs, and it says plainly that anything not on the list was not covered. **Better with** a card or bank statement export, or an app-store subscription list, pasted in. This turns the inventory from what the user remembers paying for into what they are actually being billed for, which are reliably different lists. **Best with** a one-phrase answer for what each tool was actually hired to do. That is what makes overlap detection possible. Two tools in the same vendor category are not necessarily doing the same job, and two tools in different categories sometimes are. Where the user gives only a list of names, run anyway. Ask for the job each tool does as part of Step 3, inline, rather than blocking on it upfront. --- ## When this runs Runs when the user wants to review, clean up or account for the tools already in use, individually or across a team. **Does not run for:** - A single new tool not yet adopted. That is a before-purchase question, and `before-you-in