Menu

Individual skill

side-project-launch

0upvotes

Takes a side project from idea to shipped launch with behavior-based validation, a ruthlessly cut MVP, a hard timebox, and explicit kill criteria so nights-and-weekends effort never runs open-loop for months. Use when someone asks "how do I launch my side project", "should I keep building this", "how do I validate before building", "I've been building for months and haven't shipped", or "how do I know when to quit". Do NOT use for the Product Hunt assets and mechanics specifically - use product-hunt-launch instead - for orchestrating a multi-channel company launch calendar - use launch-plan-sequencer instead - or for running a launch day in real time - use launch-day-runbook instead.

skills/side-project-launch/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Side Project Launch

The biggest side-project risk is not failure - it is spending six months of evenings building something nobody wants, with no deadline forcing the question. A side project runs on scarce hours, so the discipline is different from a startup's: validate with behavior before building, cut the MVP to one flow, timebox hard, and write the kill criteria before launch, when judgment is still honest.

## Operating procedure

Validation precedes building, and the timebox precedes scoping - scope must be cut to fit the date, never the reverse.

### Step 1: Gather inputs

1. The idea, as a one-liner: "I help [audience] do [job] better by [approach]." Force the sentence; vagueness here compounds everywhere.
2. Weekly hours honestly available (default assumption: 5-10 for a side project).
3. Skills on hand and preferred tools - boring and familiar wins.
4. The success motive: revenue, portfolio, learning, or fun. The kill criteria in Step 7 depend on it.
Back to top