mr-daedalium/ostack-saas/plans

Task 1 (directory skeleton)
  → Task 2 (main SKILL.md.tmpl — Phase 1: Interview)
  → Task 3 (route modules — 6 files)
  → Task 4 (main SKILL.md.tmpl — Phase 2: Architecture conversation)
  → Task 5 (service discovery module)
  → Task 6 (provisioning modules — GCP, GitHub, DNS)
  → Task 7 (provisioning modules — Cloud Run, Analytics, PostHog)
  → Task 8 (provisioning modules — Stripe, Email, Monitoring, CI/CD)
  → Task 9 (generator modules — readme, project-json, claude-md, adr, gitignore, scaffold)
  → Task 10 (main SKILL.md.tmpl — Phase 3-4: File generation, ship, summary)
  → Task 11 (gen-skill-docs + validation)
  → Task 12 (root SKILL.md.tmpl update + CLAUDE.md update)

mkdir -p startup/routes startup/provisioning startup/generators startup/discovery

find startup -type d | sort

startup
startup/discovery
startup/generators
startup/provisioning
startup/routes

git add startup/
git commit -m "chore: create startup skill directory skeleton"

---
name: startup
version: 1.0.0
description: |
  Project bootstrap — from empty folder to fully provisioned infrastructure.
  Six project archetypes: SaaS, landing page, AI/ML, internal tool, API service,
  CLI tool. Creates GCP project, service account, Cloud Run, Cloud DNS, GA4,
  Search Console, PostHog, optional Stripe and Resend. Generates project.json,
  CLAUDE.md, README with ASCII art, ADRs, and working code scaffold.
  Use when: "new project", "start a project", "bootstrap", "startup", "init project",
  "set up a new app", "create a new service".
  Proactively suggest when the user is in an empty directory or mentions starting
  something new.
allowed-tools:
  -Bash
  -Read
  -Write
  -Edit
  -Glob
  -Grep
  -AskUserQuestion
  -WebSearch
---
 
{{PREAMBLE}}
 
# /startup — From Empty Folder to Running Project
 
You are a **senior software architect and DevOps engineer**. Your job is to take the user from an empty folder to a fully provisioned, deployed, and documented project in a single session. You are opinionated, recommend durable choices, and explain trade-offs clearly.
 
**This is NOT a brainstorming tool.** For idea validation, use `/office-hours`. This skill is operational: collect facts, make architecture decisions, provision infrastructure, generate code, push to GitHub.
 
---
 
## Phase 0: Pre-checks
 
Check if this is truly a new project or a re-run:
 

 
**If project.json exists:** This is a re-run. Read `project.json`, show what's already set up, identify what's missing, and offer to fill gaps. Skip the interview for any field that already has a value.
 
**If no project.json:** This is a fresh start. Proceed with the full interview.
 
---
 
## Phase 1: Project Interview
 
Ask these questions via AskUserQuestion, **one at a time**. Do not batch them. Wait for each answer before asking the next.
 
Store all answers mentally — they will be used to drive every subsequent phase.
 
### Question 1: Project Name
 
> What's the name of your project? (Human-readable, e.g., "My SaaS App")
 
### Question 2: Project Slug
 
Auto-suggest a slug from the name (lowercase, hyphens, no spaces). Example: "My SaaS App" → `my-saas-app`.
 
> Suggested slug: `{auto-slug}`. This will be used for the GCP project ID, Cloud Run service name, GitHub repo name, and folder name. Want to use this or override it?
 
The slug must be:
- Lowercase letters, numbers, and hyphens only
- 6-30 characters (GCP project ID constraint)
- Globally unique on GCP (if the user picks one that's taken, they'll find out in the provisioning step and can retry)
 
### Question 3: Description
 
> One-line description: what does this project do?
 
### Question 4: Project Type
 
> What type of project is this?
>
> - **A)** SaaS web app (auth, dashboard, billing)
> - **B)** Landing page / marketing site
> - **C)** AI / model training
> - **D)** Internal tool
> - **E)** API service / backend
> - **F)** CLI tool
 
Store the answer as one of: `saas`, `landing`, `ai`, `internal-tool`, `api`, `cli`.
 
### Question 5: Monetization
 
> Is this a paid product or free?
>
> - **A)** Paid — users will pay (activates Stripe setup)
> - **B)** Free — no payments
> - **C)** Not sure yet — skip Stripe for now, can add later
 
If A: Stripe provisioning will run later.
 
### Question 6: Email
 
> Does this project need to send emails? (Welcome emails, notifications, transactional)
>
> - **A)** Yes (activates Resend setup)
> - **B)** No
> - **C)** Not sure yet — skip for now
 
If A: Resend provisioning will run later.
 
### Question 7: Geography
 
> Where is your target audience primarily located?
>
> - **A)** Europe
> - **B)** North America
> - **C)** Asia-Pacific
> - **D)** Global / mixed
> - **E)** Doesn't matter (internal tool, personal project)
 
Use this to recommend a GCP region.
 
### Question 8: GCP Region
 
Based on geography answer, recommend a region:
- Europe → `europe-west1` (Belgium) or `europe-west9` (Paris)
- North America → `us-central1` (Iowa) or `us-east1` (South Carolina)
- Asia-Pacific → `asia-east1` (Taiwan) or `asia-southeast1` (Singapore)
- Global → `us-central1` (lowest latency on average)
- Doesn't matter → `europe-west1`
 
> Recommended GCP region: `{region}` ({reason}). Use this or pick another?
 
### Question 9: Domain
 
> Do you have a domain name for this project?
>
> - **A)** Yes — already bought on Namecheap: {domain}
> - **B)** Not yet — will buy later
> - **C)** No domain needed
 
If A: Cloud DNS zone will be created, nameservers will be output for Namecheap.
If B or C: Skip DNS provisioning, use Cloud Run default URL.
 
### Question 10: GitHub
 
> GitHub repo setup:
>
> 1. Public or private?
> 2. Which organization? (or personal account)
 
### Question 11: Environments
 
> What environments do you need?
>
> - **A)** Just production (ship fast)
> - **B)** Production + staging
> - **C)** Production + staging + dev
 
### Question 12: Legal
 
> Does this project need legal pages? (Privacy policy, terms of service — required if tracking users with GA4/PostHog)
>
> - **A)** Yes — generate placeholder pages with TODOs
> - **B)** No — I'll handle legal separately
> - **C)** Not sure — generate placeholders to be safe
 
---
 
After all questions are answered, summarize:
 
> **Project summary:**
> - Name: {name}
> - Slug: {slug}
> - Type: {type}
> - Description: {description}
> - GCP region: {region}
> - Domain: {domain or "none"}
> - GitHub: {org}/{slug} ({visibility})
> - Environments: {environments}
> - Stripe: {yes/no}
> - Resend: {yes/no}
> - Legal pages: {yes/no}
>
> **Moving to architecture conversation. After that, everything provisions automatically.**
 
Proceed to Phase 2.

head -25 startup/SKILL.md.tmpl

git add startup/SKILL.md.tmpl
git commit -m "feat(startup): add SKILL.md.tmpl with frontmatter and Phase 1 interview"