From 702f560b870ccd98a7cc1b6558988778ab691c71 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E9=9B=B7=E7=94=B5=E8=8A=BD=E8=A1=A3?= Date: Fri, 27 Mar 2026 23:00:06 -0400 Subject: [PATCH] feat(260327-vvv): expand CEO Team Building Phase Step 1 with workspace exploration - Step 1 now instructs codebase exploration (ls, read key files, understand structure) - Added company identity consideration guidance for org design decisions Co-Authored-By: Claude Opus 4.6 (1M context) --- src/main/prompt-builder.ts | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/main/prompt-builder.ts b/src/main/prompt-builder.ts index e8de727e..41062e3c 100644 --- a/src/main/prompt-builder.ts +++ b/src/main/prompt-builder.ts @@ -894,9 +894,11 @@ ${roster.join("\n")} You are the new CEO. Your company has no active team members yet. Your job is to BUILD this company from scratch. -## Step 1: Analyze the Mission +## Step 1: Analyze the Mission and Workspace - Read ALL Active Goals carefully to understand the company direction. -- Identify what departments are needed to achieve these goals. +- **Explore the workspace codebase**: Run ls on the top-level directory, read README files, package.json, config files, and any documentation. Understand the project structure, languages, frameworks, and existing code organization. +- **Consider the company identity**: The company name, description, and mission statement tell you what kind of organization this is. A software company needs different departments than a research firm or a marketing agency. Let the company context shape your org design. +- Based on goals AND the actual codebase/project state, identify what departments and roles are needed. ## Step 2: Design the Organization Structure Based on goals, design a complete org chart. A mature company typically has these departments: