init-project

Init Project

MANDATORY FLOW: detect stack → ask 4 questions → WAIT for answers → generate config.

You MUST ask the 4 questions in Step 4 and WAIT for the user to answer BEFORE generating any files. Do NOT skip the questions. Do NOT generate config before receiving answers.

Step 1: Check if already initialized

If .claude/settings.json exists:

Already initialized. Use /forge sync to update or /forge audit to check score.

Exit without changes.

Step 2: Detect stacks

Scan project files silently using $DOTFORGE_DIR/stacks/detect.md as reference:

python-fastapi: pyproject.toml, requirements.txt with fastapi
react-vite-ts:  package.json with react + vite
swift-swiftui:  Package.swift, *.xcodeproj
node-express:   package.json with express/fastify (no react)
go-api:         go.mod
java-spring:    pom.xml or build.gradle with spring
supabase:       supabase/ dir or supabase in deps
docker-deploy:  Dockerfile or docker-compose*
gcp-cloud-run:  app.yaml or cloudbuild.yaml
aws-deploy:     cdk.json or template.yaml
redis:          redis in deps
data-analysis:  *.ipynb prominent
devcontainer:   .devcontainer/

Also scan existing files for additional context:

• README.md → project description
• existing test files → testing patterns
• CI config (.github/workflows, Makefile) → build/test commands

Step 3: Detect user language and ask 4 questions

Detect language: check previous messages → global CLAUDE.md → system locale → default English.

OVERRIDE RULE: For /forge init, ALWAYS present questions in the detected language, even if global CLAUDE.md says "communicate in Spanish/English/etc." The questions are part of the tool's UI, not a conversation.

Present all 4 questions together in one message. Then STOP and WAIT for the user's response. Do NOT proceed to Step 5 until the user answers.

English version:

═══ FORGE INIT ═══
Stack detected: {stacks or "none — generic config"}

4 quick questions to generate a complete config:

1. What does it do and what does it NOT do?
   → One sentence: the problem it solves, and explicit limits of v0.1.
   Example: "REST API for real-time quotes. No auth, no frontend, no historical data yet."

2. Built with what?
   → Stack, language, DB, external services, where it runs.
   Example: "Python 3.12, FastAPI, Supabase, deployed on GCP Cloud Run."

3. How do you work?
   → Solo or team, spec-first or prototype-first, testing level from day one.
   Example: "Solo, prototype-first, tests only for critical paths."

4. What domain and role?
   → What expertise does Claude need? What business concepts are critical?
   Example: "Expert in Jira API v3, agile metrics, dashboard generation.
   Key concepts: velocity, cycle time, sprint burndown, JQL."