Distribute: Scale & Automate

This skill is the capstone of the Distribute phase. It reads the Growth Experiments Tracker, takes only the experiments that proved they work, and turns each into a plan to double down (do more, do better) and automate (make the winning process run without more of the founder's hours). The output is a sequenced Scale & Automation Roadmap.

The two principles are the whole skill. Double down: a proven win is a license to do more of it (scale the volume, spend, or reach) and better (the next experiment that lifts it further). Automate: a manual process that works is a process worth systematizing — clip-and-schedule pipelines, enrichment-and-sequence loops, scheduled tasks, templates, and eventually delegation — so output grows without the founder's time growing with it. Scale is what happens when both run at once: you amplify the result and remove yourself from the loop.

The evidence gate is non-negotiable: you only scale and automate what the tracker has proven. The most expensive mistakes here are scaling a hunch, automating a process before it works, and automating away the human touch that made it work in the first place (the founder's voice, real community presence, a personal first line). This skill exists to amplify proven wins, systematize them safely, and keep a guardrail metric on every automation so throughput never quietly costs conversion.

Session length: 30–45 minutes. Claude reads the tracker and maps each winning process to its automation using the bundled tool/plugin recipes; the user supplies their time budget, their tooling/automation budget, and whether they're open to delegation. The skill plans the top few winners, not every line in the tracker — depth over breadth.

Inputs

This skill needs the proven winners, product context (so automations are specific), an output target, and the automation playbook. Winners come one of two ways depending on where the skill runs — the rest is identical.

Winners — Path A (standard): ProductOS in the repo — productos/ at the app repo root, or the current folder in a standalone ProductOS checkout

1. The Growth Experiments Tracker — usually productos/distribute/3-Growth-Experiments-Tracker.md. The primary input. Read the log for rows marked Pass with a "double down" decision, and the Cumulative Learnings. These are the only candidates for scaling and automation. If the tracker is empty or has no winners yet, stop and point the user back to studio-distribute-growth-experiments — there's nothing proven to scale.
2. Context: productos/distribute/2-Growth-Experiments.md (the rhythm and up-next queue) and productos/distribute/1-Go-To-Market-Strategy.md (the channels). Plus docs/PRODUCT.md or the Define docs for the customer, the magic moment, and the north star.