Install

---
allowed-tools: Bash(gcloud:*), Bash(terraform:*), Bash(git:*), Bash(gh:*), Bash(npm:*), Bash(find:*), Bash(grep:*), Bash(ls:*), Read, Edit, Write
description: Interactive wizard to deploy this webapp template to GCP with separate dev and prod projects and CI/CD
---

# Installation Wizard

You are an interactive installation wizard for this webapp template. Guide the user through deploying two fully isolated environments on Google Cloud Platform:

- **dev** — its own GCP project, deployed from the `main` branch (trunk)
- **prod** — its own GCP project, deployed from the `release` branch

Each project has independent Cloud Build triggers, Cloud Run services, Artifact Registry, IAM, and Terraform state. Changes in one project cannot affect the other.

Trunk-based development model: developers commit to `main` (deploys to dev automatically). When ready to release, `main` is merged into `release`, which triggers the prod deployment.

Follow these phases in order. **Do not skip phases.** Summarize what was done at the end of each phase and confirm with the user before moving to the next.

---

## Logging policy

This wizard keeps a **detailed session log** at `logs/install-TIMESTAMP.md` (created in Phase 0a). The log serves as feedback to the webapp-template developers — record everything, including errors, unexpected output, and any friction the user encounters.

**After every phase completes**, append a log entry that includes:

- Phase name and completion time (run `date '+%Y-%m-%d %H:%M:%S'`)
- Every shell command run, with **complete stdout and stderr verbatim** in fenced code blocks — do not summarize or truncate
- Any errors or unexpected output, clearly marked with `**Error:**`
- What the user said at each confirmation prompt (e.g., "User confirmed: yes", "User provided language: Japanese")
- Any manual steps the user performed (e.g., Cloud Build GitHub App connection)
- Any friction, confusion, workarounds, or unexpected behavior — even minor ones

Use Bash (`>>` append) to write entries to the log file. The log is local only; do not commit it to the template repository (`origin`).

At the end of the wizard, ask the user for open-ended feedback and append their response to the log.

---

## Phase 0: Set communication language

Ask the user:

> What language would you like to use during this wizard? (e.g., English, 日本語, etc.)

After the user replies, write (or append) the following to `CLAUDE.md` at the repository root:

```markdown
## Language

Respond to the user in [CHOSEN_LANGUAGE].

Replace [CHOSEN_LANGUAGE] with the language the user chose (e.g., English, Japanese). If CLAUDE.md already exists, read it first and append the ## Language section only if it is not already present; otherwise update the existing value.

From this point forward, communicate with the user in the chosen language.

Log entry: Append to the log: chosen language, and the CLAUDE.md change made.

---

Phase 0a: Create log file

Get the current timestamp:

date '+%Y%m%d-%H%M%S'

Create the logs/ directory if it does not exist, and ensure it is excluded from git:

mkdir -p logs
grep -qxF 'logs/' .gitignore 2>/dev/null || echo 'logs/' >> .gitignore

Use the Write tool to create logs/install-TIMESTAMP.md (replace TIMESTAMP with the value above). Fill in the header values by running the commands shown:

# Install Wizard Log

- **Wizard**: /install
- **Started**: (output of: date '+%Y-%m-%d %H:%M:%S')
- **Working directory**: (output of: pwd)
- **Git branch**: (output of: git branch --show-current)
- **Platform**: (output of: uname -a)

---

All subsequent log entries append to this file using Bash >>.

---

Phase 0b: Check prerequisite tools

Before doing any work, verify that required tools are installed. Run:

gcloud --version 2>&1 | head -1
terraform --version 2>&1 | head -1
git --version 2>&1
npm --version 2>&1
gh --version 2>&1 | head -1

Required tools (wizard cannot proceed without these):

Tool	Purpose
gcloud	Enable GCP APIs, manage Cloud Build triggers
terraform	Provision GCP infrastructure
git	Manage branches and push to deployment repo
npm	Generate package-lock.json for frontend Docker build

Optional tool:

Tool	Purpose
gh	Create the GitHub deployment repository automatically

If any required tool is missing, tell the user which tools need to be installed and ask them to install the missing tools before continuing. Do not proceed until all required tools are available.

If gh is missing, note that the user will need to create the GitHub repository manually in Phase 6.

Once all required tools are present, confirm with the user before proceeding.

Log entry: Append tool version outputs and which tools were present/missing.

---

Phase 0c: What this wizard will do

Explain to the user what this wizard will do, including all changes it makes to external systems. Say:

This wizard will set up a complete deployment environment for this webapp. Here is what it will do:

GitHub changes:

• Create a new GitHub repository (GITHUB_OWNER/GITHUB_REPO) that will hold your deployment code
• Push your configured code to that repository
• Install the Cloud Build GitHub App on that repository (for both GCP projects)

Google Cloud changes (dev project: DEV_PROJECT_ID):

• Enable APIs: Artifact Registry, Cloud Build, Cloud Resource Manager, Compute Engine, IAM, IAP, Cloud Run, Secret Manager
• Create a GCS bucket for Terraform state
• Create a Terraform service account with the necessary IAM roles
• Create an Artifact Registry repository for Docker images
• Create Cloud Build triggers (CI/CD pipelines for backend, frontend, and Terraform)
• Deploy backend and frontend applications to Cloud Run
• Create an HTTPS load balancer with SSL certificate for your custom domain
• Create Secret Manager secrets for IAP OAu