product-launch-tracking

Installation
SKILL.md

The Launch Watch

New products live or die on early signal, and watching each one by hand is exactly the chore that gets skipped in a launch week. This loop runs for a fixed window - typically 14 days - then stops itself. The bounded window is the point: an unbounded launch watch becomes a second daily report nobody reads.

Loop discipline. Read references/loop-cadence-guide.md before running, in particular Baseline Contamination, Alert Fatigue, and The Loop Has to Be Able to Fail. Its early-signal thresholds are fixed for a bounded window, so the fatigue budget and the failability rule matter more here than baseline drift: confirm the gate can actually fail and stop the spend.

Before you write

Run the input list below before you write anything. If one of those inputs is missing, ask for it and stop. Do not return a draft with a warning on it. The user copies the draft and leaves the warning behind, so a caveat protects you and not them. Ask at most THREE questions. Hard cap. Before anything becomes a question, get it yourself: read .agents/product-context.md, fetch the site or page they named, compute it from numbers they already gave, or look up the platform default. Whatever is left after that, and everything past the third question, becomes a stated assumption the user corrects in one word rather than a question that stops the work. Number them, and say what you will assume if one goes unanswered. Check .agents/product-context.md first so you never ask for something already recorded there.

Installs
13
GitHub Stars
9
First Seen
Aug 25, 2026