conversion-systemlisted

# Conversion System Turn repeated manual work into automation you can actually trust — and refuse to automate what shouldn't be. The registry is the single source of truth: `~/.claude/automations/registry.md`. ## Step 1 — CAPTURE Any task done manually twice gets a one-line entry in the registry backlog. No judgment at capture time. Format: `- [ ] <task, one line> — seen <n>x, ~<minutes> each` ## Step 2 — QUALIFY (3-question filter) Ask all three. **3 yeses = automate. Any no = leave manual, note why.** 1. **Repeats same shape?** Same steps each time, not bespoke judgment each run. 2. **Inputs digital?** Everything needed is reachable by tooling (API, file, MCP). ⚠️ claude.ai-connector MCPs (Linear, Granola, Slack…) are session-auth only — they do NOT work headless. If inputs need them, the automation is in-session, never a LaunchAgent. 3. **"Done" definable in one sentence?** Objective end-state a checker can verify. Then apply the **build bar** (from `manager` skill): name the hours/week saved (with a number) OR the outward output shipped. Neither → don't build, even with 3 yeses. ## Step 3 — SPEC (template, mandatory before build) ``` TASK: <one sentence> TRIGGER: <manual /command | /loop in-session | LaunchAgent clock-based> INPUT: <exact sources; flag session-auth'd ones> RULES: <constraints, incl. voice/verify rules from memory> STEPS: <numbered, each verifiable> OUTPUT: <artifact produced — a DRAFT/file/report, never a sent thing