agent-rolloutlisted

# Agent Rollout Most agent builds fail at rollout, not at quality. This skill exists because a working thing nobody uses scores zero. ## When to use - An agent works and needs to reach other people - Adoption is low on something already shipped - Packaging for distribution - Versioning and update strategy ## Inputs - Reads: `workspace/agents/<name>/brief.md`, `guardrails.md` - Needs from user: who the intended users are, what tools they already have open all day, and who their manager is ## Workflow ### 1. Understand the three reasons adoption fails In order of frequency, and none of them is quality. **It lives somewhere they do not already work.** Adoption of a tool requiring a new window, a new login, or a new habit is a fraction of adoption of one inside an existing workflow. Ship into the surface they already have open. **The first run failed.** An API key they do not have, a file that does not exist, a permission prompt they do not understand. Most people do not attempt a second time. **Nobody asked whether they used it.** With no accountable person and no weekly check, usage decays to zero inside a month regardless of value. ### 2. Engineer the first run to under fifteen minutes Time to first useful output is the adoption metric. Over roughly fifteen minutes and most users never return. ``` [ ] Zero setup steps in the first run, or one at most [ ] Works with no config file present, using sensible defaults [ ] Every missing file degrades gracefully, never err