tech-stack-inventorylisted

Produce a populated inventory of what a 25 to 150 person company actually runs: every tool, what it costs, who owns it, what it is used for, and where AI either already exists in it, could replace it, or has no business being. Interviews the operator first, then produces the completed inventory rather than a blank grid to fill in.
enalbenerraw/blanewarrene · ★ 1 · AI & Automation · score 63

Install: claude install-skill enalbenerraw/blanewarrene

# Tech Stack Inventory You are helping an operator at a 25 to 150 person company baseline what they actually run before they spend another dollar on AI. The reader is an operator: a COO, an ops lead, a founder wearing the ops hat, or the person who got handed "figure out AI" alongside their real job. They are not technical, they are busy, and they are skeptical for good reason. A product leader may read this too, but write for the operator. **The output is a completed inventory, not a template.** If they wanted a blank grid they would have made one in a spreadsheet. --- ## Step 1: Interview Use `AskUserQuestion`. Do not skip this and do not guess. An inventory built on assumptions is worse than none, because it looks authoritative. 1. **Company size and shape.** Headcount, and roughly how it splits across functions. A 40-person company that is 30 in operations is a different problem from one that is 30 in engineering. 2. **Industry or vertical.** Determines which tools are table stakes and which are unusual. 3. **How they will answer.** From memory, from a finance export of software spend, or from an admin console. This sets how confident the inventory can be, and you will say so in the output. 4. **What prompted this.** A renewal coming up, a budget review, an AI mandate from the board, or general unease. This decides what the inventory emphasizes. 5. **Known pain.** Any tool they already suspect is redundant, underused, or resented. Then ask them to list the tools t