project-init

/project-init

Initializes a new project with directory structure, project-specific CLAUDE.md, and Git repository.

Argument: $ARGUMENTS = [Project name]

If provided: use as project name (also used as directory name). If not provided: ask for the project name.

Execution

0. Detect Promotion Brief (Lean → Full Promotion)

If docs/PROMOTION_BRIEF.md exists (created by /lean-promote):

• Read the brief in full
• Take the project name from the path / repo name (do not ask again)
• Use the brief as bootstrap input instead of a greenfield prompt:
  • Validated findings → P0 input (proposal for /p0-problem)
  • Confirmed assumptions → carry into CLAUDE.md under "Key Decisions" with date
  • Refuted assumptions → note in CLAUDE.md under "Open Risks" as "Lean-Lessons"
  • Constitution candidates → hand off to /constitution (step 4 below)
  • Catch-up obligations → schedule later via /p4-backlog as stories; note in HANDOVER.md now

If docs/PROMOTION_BRIEF.md does not exist: follow the normal greenfield path (steps 1–6).

1. Collect project information

Ask the user for the following information (if not already known):

• Project name: Name of the project (used as directory name, kebab-case)
• Project type: Software | Business | Software+Business
• Short description: 1-2 sentences describing what the project is
• Project goals: What should be achieved at the end? (1-3 goals)
• Target audience: Who uses the result?
• Budget: Rough estimate or "still unclear"
• Timeline: When should it be done? or "open"
• Regulatory: DSGVO (GDPR), health data, financial regulation, or "Standard"
• Tech preferences: For software – are there requirements? or "open"
• Agent notes: Special instructions for specific agents? (optional)

2. Create directory structure

Create the following structure in the current directory:

mkdir -p $PROJECTNAME/.claude
mkdir -p $PROJECTNAME/docs/{discovery,concept,validation,architecture,planning,quality,launch}
mkdir -p $PROJECTNAME/src
mkdir -p $PROJECTNAME/tests