startup-launch-kitlisted

Opt-in umbrella orchestrator that sequences the full five-step startup pipeline (`brand-workshop` → `validation-canvas` → `riskiest-assumption-test` → `pitch-deck` → `startup-grill`) with shared state via `kit-manifest.json`. Every pipeline skill stays independently invocable; this is convenience, not replacement: it calls each in turn, never bypasses their gates, surfaces every prompt to the founder, and records gate overrides. Use when the user asks to "build my whole startup kit", "do the full pipeline", "launch kit", "full validation pipeline", or asks Claude to coordinate the five startup skills together. Also triggers for already-built projects ("run the whole pipeline on my existing repo", "infer the kit from the code"), reusing `startup-audit`'s inference to pre-fill what code reveals. (For a fast verdict rather than the full kit, that's `startup-audit`.) Also via `/startup-launch-kit`. Does NOT trigger for single-step requests ("just the canvas", "build my deck").
sorawit-w/agent-skills · ★ 1 · AI & Automation · score 75

Install: claude install-skill sorawit-w/agent-skills

# Startup Launch Kit Opt-in orchestrator that sequences the five-step startup pipeline with state tracking via `kit-manifest.json`. The orchestrator is convenience for founders who want end-to-end coordination without manual step-chaining; it is **not** a replacement for any individual skill, and it never bypasses the gates each skill enforces. The orchestrator's job is **sequencing + state**, not content. Each pipeline skill runs as itself — same prompts, same outputs, same gates the founder would see if they invoked the skill directly. The orchestrator just remembers where the founder is, surfaces the next step, and records overrides for audit. It runs in one of two **source modes** (detected in Phase 0.3): **greenfield** (no built product — the step-by-step pipeline, as always) or **existing-project** (a codebase is present — the orchestrator reads it via `startup-audit` and pre-fills what code reveals, asking the founder only for what it can't infer). Existing-project mode is **opt-in**: offered when a codebase is detected, never forced. --- ## STOP gate — When NOT to use this skill Hand off to a different skill — do not run the orchestrator — if any of these apply: - **The user wants only one step**, named explicitly (e.g., "just build my validation canvas", "rework my pitch deck slide 5", "grill my idea") → route to the named skill directly. The orchestrator's value is end-to-end sequencing; running it for one step is overhead with no benefit. - **The user