build-speclisted

# Build Spec Most AI-built automations break in week two, not week one. They work in the demo because the demo is the happy path. Then a field comes back null, an API rate-limits, the agent runs twice on the same record, and nobody decided what should happen because nobody wrote it down. This skill writes that down first. You answer a short interview, it produces a build spec you can read in two minutes and hand to Claude (or a human) to build against. The spec is the review surface. Vibe-coding the prototype is fine. Vibe-coding the spec is how you get slop. Twelve sections, in order. Fill them as you go. Do not skip ahead to writing code. ## Inputs (ask for whatever is missing) - **The one-line ask** (required): "a thing that ___". The outcome, in plain English. - **Who runs it and where** (the stack: Trigger.dev / cron / a server / a serverless function), and what it touches (which APIs, DBs, tools). - *Optional, makes it sharper:* an example of a real input record, the worst input you can imagine, and how often it runs. ## The 12 sections 1. **Job to be done.** One sentence: the outcome, not the mechanism. "Every morning, surface companies in our niche that started hiring this week." If you can't say it in one sentence, the scope is wrong — split it. 2. **Trigger.** What starts a run: a cron schedule (state it), a webhook, an event, a manual call. Note what happens if a run is still going when the next trigger fires (skip, queue, or overlap). 3. **Inputs and sour