moai-adk 0.32.8__py3-none-any.whl → 0.41.2__py3-none-any.whl

moai_adk/templates/.claude/commands/moai/0-project.md

@@ -2,7 +2,7 @@
 name: moai:0-project
 description: "Initialize project metadata and documentation"
 argument-hint: "[<empty>|setting|update|--glm-on <token>]"
-allowed-tools: Read, Write, Edit, Grep, Glob, WebFetch, WebSearch, Bash, TodoWrite, AskUserQuestion, Task, Skill
+allowed-tools: Task, AskUserQuestion, TodoWrite
 model: inherit
 ---
 
@@ -36,7 +36,7 @@ Workflow Integration: This command implements Step 0 of Alfred's three-step exec
 
 ---
 
-##  Command Purpose
+## Command Purpose
 
 Initialize or update project metadata using language-first architecture. The system supports five execution modes:
 
@@ -52,7 +52,7 @@ IMPACT: Users can navigate project lifecycle without manual intervention.
 
 ---
 
-##  Associated Agents and Skills
+## Associated Agents and Skills
 
 The following agents and skills support this command:
 
@@ -68,7 +68,7 @@ IMPACT: Each agent optimizes its domain while maintaining system coherence.
 
 ---
 
-##  Language Configuration
+## Language Configuration
 
 Core Principle: Language configuration originates from moai-adk CLI initialization or update commands.
 
@@ -105,8 +105,8 @@ All configuration questions are defined in YAML files under .moai/config/questio
 
 - _schema.yaml: Schema definition and constraints
 - tab1-user.yaml: User and language settings (3 questions)
-- tab2-project.yaml: Project metadata (4 questions)
-- tab3-git.yaml: Git strategy and workflow (25 conditional questions)
+- tab2-project.yaml: Project metadata (2 questions)
+- tab3-git.yaml: Git strategy and workflow (26 questions, includes GitHub Profile)
 - tab4-quality.yaml: Quality principles and reports (7 questions)
 - tab5-system.yaml: System and GitHub integration (7 questions)
 
@@ -161,7 +161,7 @@ IMPACT: CLAUDE.md loads only user.yaml and language.yaml (~17 lines vs 400+ full
 
 This command uses agent execution patterns defined in CLAUDE.md (lines 96-120).
 
-### Sequential Phase-Based Chaining ✅
+### Sequential Phase-Based Chaining PASS
 
 Command implements sequential chaining through 3 main phases:
 
@@ -179,7 +179,7 @@ WHY: Sequential execution ensures proper configuration and file generation
 
 IMPACT: Skipping phases would create incomplete or misconfigured project setup
 
-### Parallel Execution ❌
+### Parallel Execution FAIL
 
 Not applicable - configuration requires sequential processing
 
@@ -190,7 +190,7 @@ WHY: Project initialization has strict ordering requirements
 
 IMPACT: Parallel execution would create configuration conflicts and invalid project state
 
-### Resumable Agent Support ❌
+### Resumable Agent Support FAIL
 
 Not applicable - command completes in single execution
 
@@ -207,7 +207,7 @@ Refer to CLAUDE.md "Agent Chaining Patterns" (lines 96-120) for complete pattern
 
 ---
 
-##  Execution Philosophy
+## Execution Philosophy
 
 The project setup follows explicit delegation pattern: Understand the user intent, Plan the execution, Execute through specialized agents.
 
@@ -233,7 +233,7 @@ Manager-project agent handles all implementation complexity including file opera
 
 ---
 
-##  PHASE 1: Command Routing and Analysis
+## PHASE 1: Command Routing and Analysis
 
 Goal: Detect subcommand intent and prepare execution context for delegation.
 
@@ -347,7 +347,242 @@ Store: Response in `$MODE_EXECUTION_RESULT`
 
 ---
 
-##  PHASE 2: Execute Mode
+## PHASE 1.5: Smart Question System (INITIALIZATION Mode Only)
+
+Goal: Collect minimal user input, research best practices via web search, and propose optimized project configuration.
+
+WHY: Reduce user burden from 40+ questions to 3 essential questions while providing expert-level recommendations based on current industry standards.
+
+IMPACT: Non-developers can create production-ready projects with minimal technical knowledge.
+
+### Step 1: Collect Essential Information (3 Questions Only)
+
+[HARD] Use AskUserQuestion to collect ONLY 3 required fields at COMMAND level.
+
+WHY: Minimal questions reduce user friction while capturing essential project identity.
+
+IMPACT: More questions would overwhelm non-developers and slow down project creation.
+
+Question 1 - Project Name:
+
+- question: Translate to user's conversation_language with friendly guidance:
+  - Korean: "프로젝트 이름을 정해주세요. 영어 소문자와 하이픈(-)만 사용할 수 있어요."
+  - English: "Choose a project name. Use only lowercase letters and hyphens (-)."
+- header: "Project Name"
+- type: text input (user selects "Other" to type)
+- examples shown to user:
+  - "snake-game" (게임 프로젝트)
+  - "my-first-app" (첫 번째 앱)
+  - "todo-list" (할 일 목록)
+- validation: lowercase, no spaces, valid directory name
+- helper: If user enters Korean or spaces, suggest alternatives automatically
+
+Question 2 - Project Type:
+
+- question: Translate to user's conversation_language with beginner-friendly tone:
+  - Korean: "어떤 종류의 프로젝트를 만들고 싶으세요?"
+  - English: "What kind of project would you like to create?"
+- header: "Project Type"
+- multiSelect: false
+- options (max 4, beginner-friendly labels):
+  - label: "Web Browser App"
+    korean_label: "웹 브라우저에서 보는 것"
+    description: "크롬, 사파리 등 브라우저에서 열어보는 프로그램 (게임, 웹사이트 등)"
+    tech_hint: "HTML, CSS, JavaScript 또는 React, Vue 사용"
+  - label: "Mobile App"
+    korean_label: "스마트폰 앱"
+    description: "아이폰이나 안드로이드에서 설치해서 사용하는 앱"
+    tech_hint: "React Native, Flutter 사용"
+  - label: "Command Line Tool"
+    korean_label: "터미널에서 실행하는 도구"
+    description: "명령어로 실행하는 프로그램 (자동화 스크립트 등)"
+    tech_hint: "Python, Node.js, Go 사용"
+  - label: "Backend API"
+    korean_label: "서버/백엔드 서비스"
+    description: "데이터를 저장하고 처리하는 서버 프로그램"
+    tech_hint: "FastAPI, Express, Django 사용"
+
+Question 3 - Project Description:
+
+- question: Translate to user's conversation_language with examples:
+  - Korean: "만들고 싶은 것을 한 문장으로 설명해주세요."
+  - English: "Describe what you want to build in one sentence."
+- header: "Description"
+- type: text input (user selects "Other" to type)
+- examples shown to user (in conversation_language):
+  - "방향키로 뱀을 조종해서 음식을 먹는 게임" (스네이크 게임)
+  - "할 일을 추가하고 완료 표시하는 앱" (투두 리스트)
+  - "날씨 정보를 보여주는 웹페이지" (날씨 앱)
+  - "사진을 업로드하고 공유하는 서비스" (갤러리)
+- validation: non-empty string
+- helper: Encourage natural language description, no technical terms required
+
+Store responses in: $PROJECT_ESSENTIAL_INFO
+
+### Step 2: Web Search for Best Practices
+
+[HARD] After collecting essential info, perform targeted web searches using WebSearch tool.
+
+WHY: Real-time research ensures recommendations reflect current industry standards (2025).
+
+IMPACT: Outdated recommendations would create technical debt from project start.
+
+Based on collected project_type, execute 3 parallel searches:
+
+Search Query 1: "[project_type] best practices 2025"
+- Extract: Design patterns, architecture recommendations, common pitfalls
+
+Search Query 2: "[project_type] recommended tech stack 2025"
+- Extract: Framework comparisons, library recommendations, version requirements
+
+Search Query 3: "[project_type] [project_description keywords] architecture patterns"
+- Extract: Domain-specific patterns, similar project architectures
+
+Analyze search results and compile:
+
+- Recommended Frameworks: Top 2-3 options with pros/cons
+- UI Library: Best options for project type
+- Testing Framework: Industry standard for project type
+- Build Tools: Current best practices
+- Deployment Target: Common deployment platforms
+
+Store analysis in: $BEST_PRACTICES_ANALYSIS
+
+### Step 3: Generate Smart Proposal
+
+[HARD] Create structured proposal based on web search analysis.
+
+WHY: Expert-curated recommendations reduce decision paralysis for non-developers.
+
+IMPACT: Poor recommendations would lead to project failure or rework.
+
+Proposal Structure:
+
+Complexity Detection (before proposing):
+- Simple Projects (recommend NO framework):
+  - Keywords: "게임", "game", "간단한", "simple", "첫", "first", "연습", "practice"
+  - Project types: Browser games, simple utilities, learning projects
+  - Recommended stack: HTML5 + CSS3 + Vanilla JavaScript (+ Canvas for games)
+  - Rationale: "프레임워크 없이 기본 기술만으로 빠르게 만들 수 있어요"
+
+- Medium Projects (recommend lightweight framework):
+  - Keywords: "블로그", "포트폴리오", "랜딩페이지"
+  - Recommended stack: Next.js or Astro with minimal dependencies
+
+- Complex Projects (recommend full framework):
+  - Keywords: "대시보드", "관리자", "SaaS", "플랫폼"
+  - Recommended stack: Full framework with state management, testing, etc.
+
+Technology Stack Proposal:
+- For Simple Projects (games, learning):
+  - Framework: "프레임워크 없음 - 순수 HTML/CSS/JavaScript로 충분해요"
+  - UI: "CSS만 사용 (Canvas for games)"
+  - Testing: "브라우저 개발자 도구로 확인"
+  - Build: "빌드 도구 없음 - 파일을 바로 브라우저에서 열면 됩니다"
+
+- For Medium/Complex Projects:
+  - Framework: Primary recommendation with rationale
+  - UI Library: Recommended option
+  - Testing: Standard for project type
+  - Build Tools: Current best practice
+
+Architecture Proposal:
+- Directory Structure: Recommended layout for project type
+- Key Patterns: Component patterns, state management approach
+- Data Flow: How data moves through the application
+
+Quality Standards:
+- Test Coverage Target: Industry standard percentage
+- TRUST 5 Level: Recommended validation level
+- Accessibility: WCAG level appropriate for project
+
+Store proposal in: $SMART_PROPOSAL
+
+### Step 4: Present Proposal and Get User Approval
+
+[HARD] Use AskUserQuestion to present proposal and get explicit user approval.
+
+WHY: User must consent before any files are created or configuration applied.
+
+IMPACT: Automatic execution without approval violates user autonomy and may create unwanted configuration.
+
+Proposal Presentation Format:
+
+Present in user's conversation_language with clear sections:
+
+```markdown
+Based on your project "{project_name}" ({project_type}), here is my recommendation:
+
+**Technology Stack**
+- Framework: {framework} - {brief_rationale}
+- UI: {ui_library} - {brief_rationale}
+- Testing: {test_framework}
+- Build: {build_tools}
+
+**Architecture**
+- Structure: {directory_pattern}
+- Patterns: {key_patterns}
+
+**Quality Standards**
+- Coverage: {coverage_target}%
+- TRUST Level: {trust_level}
+
+Sources: [List actual WebSearch sources used]
+```
+
+Approval Question:
+
+- question: Translate "Do you approve this configuration? You can modify specific parts or request a different approach." to user's conversation_language
+- header: "Approval"
+- multiSelect: false
+- options:
+  - label: "Approve and Continue"
+    description: "Create project with these settings"
+  - label: "Modify Tech Stack"
+    description: "Keep architecture, change framework/libraries"
+  - label: "Modify Architecture"
+    description: "Keep tech stack, change structure/patterns"
+  - label: "Start Over"
+    description: "Re-run search with different criteria"
+
+If user selects "Modify":
+- Use additional AskUserQuestion to collect specific changes
+- Update $SMART_PROPOSAL with modifications
+- Re-present for approval
+
+Loop until user selects "Approve and Continue"
+
+Store approval in: $USER_APPROVAL
+
+### Step 5: Delegate to Manager-Project Agent
+
+[HARD] After user approval, invoke manager-project agent with complete context.
+
+WHY: Agent receives all necessary information to generate files without further user interaction.
+
+IMPACT: Missing context would force agent to make assumptions or fail.
+
+Pass to manager-project via Task():
+
+- Mode: INITIALIZATION
+- Language: User's conversation_language
+- Project Essential Info: $PROJECT_ESSENTIAL_INFO (name, type, description)
+- Approved Proposal: $SMART_PROPOSAL (tech stack, architecture, quality)
+- User Approval Status: $USER_APPROVAL
+- WebSearch Sources: URLs used for recommendations
+
+Agent responsibilities:
+- Generate .moai/project/product.md from project description + approved proposal
+- Generate .moai/project/structure.md from architecture proposal
+- Generate .moai/project/tech.md from technology stack proposal
+- Create .moai/config/config.yaml with all settings
+- Apply language settings throughout
+
+Output: Complete project initialization with documentation
+
+---
+
+## PHASE 2: Execute Mode
 
 Goal: Execute the appropriate mode based on routing decision.
 
@@ -398,8 +633,6 @@ UPDATE MODE:
     - Preserve all user settings and customizations
     - Add meaningful comments explaining each section
     - Optimize structure (remove dead fields, consolidate duplicates)
-    - Convert preset files (presets/*.json → presets/*.yaml)
-    - Remove old JSON files after successful migration
   - Use YAML's native features:
     - Multi-line strings for long descriptions
     - Inline comments for field explanations
@@ -412,17 +645,13 @@ UPDATE MODE:
 
 ### Language-Aware Announcements
 
-After any language selection or change, auto-translate company announcements:
-
-```bash
-uv run $CLAUDE_PROJECT_DIR/.claude/hooks/moai/shared/utils/announcement_translator.py
-```
+After any language selection or change, auto-translate company announcements by executing the announcement translator script located at .claude/hooks/moai/shared/utils/announcement_translator.py using uv run.
 
-This ensures `.claude/settings.json` contains announcements in the user's selected language.
+This ensures .claude/settings.json contains announcements in the user's selected language.
 
 ---
 
-##  SETTINGS MODE: Tab-Based Configuration (NEW)
+## SETTINGS MODE: Tab-Based Configuration (NEW)
 
 > Version: v2.0.0 | Last Updated: 2025-11-19 | Changes: Removed [tab_ID] arg, added git_strategy.mode selection, expanded Tab 3 with conditional batches, fixed 26 field name errors, +16 settings
 
@@ -439,45 +668,25 @@ The SETTINGS MODE uses a tab-based batch question system to provide organized, u
 
 ### Initial Entry Point: Tab Selection Screen
 
-When user runs `/moai:0-project setting` (without tab_ID), present tab selection:
+When user runs /moai:0-project setting (without tab_ID), present tab selection using AskUserQuestion:
 
-```markdown
-Which settings tab would you like to modify?
+Question: Which settings tab would you like to modify?
 
 Options:
+- Tab 1: User and Language - Configure user name, conversation language, agent prompt language
+- Tab 2: Project Settings - Configure project name, description
+- Tab 3: Git Strategy and Workflow - Configure GitHub profile, Manual/Personal/Team Git settings, commit/branch strategy
+- Tab 4: Quality Principles and Reports - Configure TRUST 5, report generation, storage location
 
-1. Tab 1: User & Language
-
-   - Configure user name, conversation language, agent prompt language
-
-2. Tab 2: Project & GitHub Settings
-
-   - Configure project name, description, mode, GitHub Profile Name
-
-3. Tab 3: Git Strategy & Workflow
-
-   - Configure Personal/Team Git settings, commit/branch strategy
-
-4. Tab 4: Quality Principles & Reports
-
-   - Configure TRUST 5, report generation, storage location
-
-5. Tab 5: System & GitHub Integration
-
-   - Configure MoAI system, GitHub automation
-
-6. Modify All Tabs
-   - Recommended: Tab 1 → Tab 2 → Tab 3 → Others
-```
+Note: Additional option "Modify All Tabs" guides user through Tab 1 through Tab 5 in sequence. Tab 5 covers System and GitHub Integration settings.
 
 After Tab Completion:
 
-```markdown
-Would you like to modify another settings tab?
+Question: Would you like to modify another settings tab?
 
-1. No, finish settings
-2. Select another tab
-```
+Options:
+- No, finish settings
+- Select another tab
 
 ### Tab Schema Reference
 
@@ -490,26 +699,32 @@ Tab 1: User & Language (Required Foundation)
   - NOTE: conversation_language_name is auto-updated when conversation_language changes
 - Setting count: 3 | Critical checkpoint
 
-Tab 2: Project & GitHub Settings (Recommended)
+Tab 2: Project Settings (Recommended)
 
-- Batch 2.1: Project metadata (4 questions)
-  - Project name, description, mode, GitHub Profile Name (e.g., @GoosLab)
-- Batch 2.2: Auto-processed locale settings (0 questions - UPDATED: internal analysis only)
+- Batch 2.1: Project metadata (2 questions)
+  - Project name, description
+  - NOTE: GitHub Profile moved to Tab 3, Project Mode removed
+- Batch 2.2: Auto-processed locale settings (0 questions - internal analysis only)
   - project.locale, default_language, optimized_for_language (auto-determined from conversation_language)
   - NOTE: No user input needed. These 3 fields update automatically when conversation_language changes
   - Auto-Processing Delegation: Command does NOT perform auto-processing. manager-project agent receives user selections, determines derived fields, then delegates atomic update to UnifiedConfigManager skill.
-- Setting count: 4
+- Setting count: 2
 
 Tab 3: Git Strategy & Workflow (Recommended with Validation - REDESIGNED v2.0.0)
 
-- Batch 3.0: Workflow mode selection (1 question - Personal/Team/Hybrid) → Controls visibility of subsequent batches
-- Batch 3.1: Personal core settings (4 questions) - CONDITIONAL (Personal/Hybrid only)
-- Batch 3.2: Personal branch & cleanup (4 questions) - CONDITIONAL (Personal/Hybrid only)
-- Batch 3.3: Personal protection & merge (4 questions) - CONDITIONAL (Personal/Hybrid only)
-- Batch 3.4: Team core settings (4 questions) - CONDITIONAL (Team/Hybrid only)
-- Batch 3.5: Team branch & protection (4 questions) - CONDITIONAL (Team/Hybrid only)
-- Batch 3.6: Team safety & merge (2 questions) - CONDITIONAL (Team/Hybrid only)
-- Setting count: 29 (+13 from v1.0.0) | Critical checkpoint for Git conflicts & mode consistency
+- Batch 3.0a: GitHub Profile (1 question) - Always shown, required for all modes
+  - GitHub username (e.g., @GoosLab) - moved from Tab 2
+- Batch 3.0: Workflow mode selection (1 question - Manual/Personal/Team) - Controls visibility of subsequent batches
+- Batch 3.1: Manual core settings (4 questions) - CONDITIONAL (Manual only)
+- Batch 3.2: Manual push settings (1 question) - CONDITIONAL (Manual only)
+- Batch 3.3: Personal core settings (4 questions) - CONDITIONAL (Personal only)
+- Batch 3.4: Personal commit & push settings (3 questions) - CONDITIONAL (Personal only)
+- Batch 3.5: Personal branch settings (2 questions) - CONDITIONAL (Personal only)
+- Batch 3.6: Team core settings (4 questions) - CONDITIONAL (Team only)
+- Batch 3.7: Team commit & PR settings (3 questions) - CONDITIONAL (Team only)
+- Batch 3.8: Team branch & protection settings (3 questions) - CONDITIONAL (Team only)
+- Batch 3.9: Team branch naming settings (2 questions) - CONDITIONAL (Team only)
+- Setting count: 26 | Critical checkpoint for Git conflicts & mode consistency
 
 Tab 4: Quality Principles & Reports (Optional - UPDATED v2.0.0)
 
@@ -527,83 +742,68 @@ Tab 5: System & GitHub Integration (Optional - UPDATED v2.0.0)
 
 #### Step 1: Load Tab Schema
 
-```markdown
-Load: .claude/skills/moai-workflow-project/schemas/tab_schema.json
-Extract:
+Load the tab schema from .claude/skills/moai-workflow-project/schemas/tab_schema.json and extract the following:
 
-- Tab definition (label, batches)
-- Batch questions (max 4 per batch)
+- Tab definition including label and batches
+- Batch questions with maximum 4 questions per batch
 - Field mappings to config.yaml paths
-- Current values from existing config
-- Validation rules
-```
+- Current values from existing configuration
+- Validation rules for each field
 
 #### Step 2: Execute Batch via AskUserQuestion
 
 Single Batch Execution Example (Tab 1, Batch 1.1):
 
-```markdown
-Call: AskUserQuestion(
-questions: [
-{
-question: "How would you like to configure the user name? (current: GoosLab)",
-header: "User Name",
-multiSelect: false,
-options: [
-{label: "Keep Current Value", description: "Continue using GoosLab"},
-{label: "Change", description: "Select Other to enter a new name"}
-]
-},
-{
-question: "What language should Alfred use in conversations? (current: Korean/ko)",
-header: "Conversation Language",
-multiSelect: false,
-options: [
-{label: "Korean (한국어)", description: "모든 콘텐츠를 한국어로 생성"},
-{label: "English (English)", description: "All content will be generated in English"},
-{label: "Japanese (日本語)", description: "日本語で全てのコンテンツを生成"},
-{label: "Chinese (中文)", description: "中文内容生成"},
-{label: "Custom (기타)", description: "직접 언어 코드 입력 (예: th, ar, vi, nl)"}
-]
-},
-{
-question: "What is the display name for the selected language? (current: Korean)",
-header: "Language Display Name",
-multiSelect: false,
-options: [...]
-},
-{
-question: "What language should agent prompts use? (current: same as conversation)",
-header: "Agent Prompt Language",
-multiSelect: false,
-options: [...]
-}
-]
-)
+Call AskUserQuestion with the following questions array:
+
+Question 1 - User Name:
+- Question text: What is your name? To change, type your name in the text field below. (current: GoosLab)
+- Header: User Name
+- MultiSelect: false
+- Options: Keep Current Value with description to continue using current value
+
+Question 2 - Conversation Language:
+- Question text: What language should Alfred use in conversations? (current: Korean/ko)
+- Header: Conversation Language
+- MultiSelect: false
+- Options: Korean, English, Japanese, Chinese with localized descriptions
+
+Question 3 - Language Display Name:
+- Question text: What is the display name for the selected language? (current: Korean)
+- Header: Language Display Name
+- MultiSelect: false
+
+Question 4 - Agent Prompt Language:
+- Question text: What language should agent prompts use? (current: same as conversation)
+- Header: Agent Prompt Language
+- MultiSelect: false
 
 Process user responses from AskUserQuestion into config update:
-user.name → user_input_or_keep_current
-language.conversation_language → selected_value
-language.conversation_language_name → user_input_or_keep_current
-language.agent_prompt_language → selected_value
-```
+- user.name receives user input or keeps current value
+- language.conversation_language receives selected value
+- language.conversation_language_name receives user input or keeps current value
+- language.agent_prompt_language receives selected value
 
 #### Step 3: Process Responses
 
 Mapping Logic:
 
-```markdown
 For each question in batch:
 
-1. Get field path from schema (e.g., "user.name")
-2. Get user's response (selected option or custom input)
-3. Convert to config.yaml value:
-   - "Other" option → Use custom input from user
-   - Selected option → Use option's mapped value
-   - "Keep current" → Use existing value
-4. Build update object: {field_path: new_value}
-5. Collect all updates from batch
-```
+Step 1: Get field path from schema (for example, user.name)
+
+Step 2: Get user's response (selected option or custom input from Type something field)
+
+Step 3: Convert to config.yaml value using these rules:
+- If custom text input from Type something field: Use the typed value directly
+- If selected preset option: Use the option's mapped value
+- If Keep Current Value option: Use existing value from config
+
+Step 4: Build update object with field path as key and new value as value
+
+Step 5: Collect all updates from batch
+
+Note: The Type something input field is auto-added by AskUserQuestion tool. Users type custom values directly in this field instead of selecting an Other option.
 
 #### Step 4: Validate at Checkpoints
 
@@ -633,21 +833,19 @@ Checkpoint Locations (from tab_schema navigation_flow):
 
 Update Pattern (Skill-delegated):
 
-```markdown
 Delegate ALL config update operations to UnifiedConfigManager from moai-workflow-project:
 
-- Manager handles backup/rollback logic internally
-- Manager performs deep merge with validation
-- Manager writes atomically to config.yaml
-- Manager reports success/failure
+Manager responsibilities:
+- Handle backup and rollback logic internally
+- Perform deep merge with validation
+- Write atomically to config.yaml
+- Report success or failure
 
 Agent responsibilities:
-
 - Collect user responses from AskUserQuestion
 - Map responses to config field paths
 - Pass update map to Skill
 - Report results to user
-```
 
 UnifiedConfigManager Responsibilities:
 
@@ -660,158 +858,163 @@ UnifiedConfigManager Responsibilities:
 
 #### Tab 1 Execution Example
 
-User runs: `/moai:0-project setting tab_1_user_language`
+User runs: /moai:0-project setting tab_1_user_language
 
-```
 Step 1: Project-manager loads tab schema
+
 Step 2: Extracts Tab 1 (tab_1_user_language)
-Step 3: Gets Batch 1.1 (基本設定)
+
+Step 3: Gets Batch 1.1 (Basic Settings)
+
 Step 4: Loads current values from config.yaml including extended language settings:
-  - User configuration: user.name value
-  - Conversation language: language.conversation_language (ko, en, ja, zh, etc.)
-  - Agent prompt language: language.agent_prompt_language
-  - Additional language settings: git_commit_messages, code_comments, documentation, error_messages
-Step 5: Calls AskUserQuestion with 3 questions for core language settings
-  - Question 1: "The user name is currently set to [current value]. Is this correct?"
-  - Question 2: "What language should Alfred use in conversations? (current: [language display name]/[code])"
-  - Question 3: "The agent internal prompt language is currently set to [display name]/[code]. How would you like to configure this?"
+- User configuration: user.name value
+- Conversation language: language.conversation_language (ko, en, ja, zh, etc.)
+- Agent prompt language: language.agent_prompt_language
+- Additional language settings: git_commit_messages, code_comments, documentation, error_messages
+
+Step 5: Calls AskUserQuestion with 3 questions for core language settings:
+- Question 1: The user name is currently set to [current value]. Is this correct?
+- Question 2: What language should Alfred use in conversations? (current: [language display name]/[code])
+- Question 3: The agent internal prompt language is currently set to [display name]/[code]. How would you like to configure this?
+
 Step 6: Receives user responses and maps them to configuration fields
-Step 7: Processes each response (map to config fields)
-  - user.name response → user.name
-  - conversation_language response → language.conversation_language
-  - Auto-update: conversation_language_name (ko → Korean, en → English, ja → Japanese, es → Spanish)
-  - agent_prompt_language response → language.agent_prompt_language
-Step 8: Runs Tab 1 validation checkpoint
-  - Check language is valid
-  - Verify consistency
-Step 9: Delegates atomic update to UnifiedConfigManager from moai-workflow-project
-  - Manager handles backup/rollback internally
-  - Manager performs deep merge (including auto-updated conversation_language_name)
-  - Manager verifies final structure
-Step 10: Receives result from Manager
-  - Success: Report changes made (4 fields: user.name, conversation_language, conversation_language_name [auto], agent_prompt_language)
-  - Failure: Report error from Skill with recovery suggestions
-```
+
+Step 7: Processes each response (map to config fields):
+- user.name response maps to user.name
+- conversation_language response maps to language.conversation_language
+- Auto-update: conversation_language_name (ko maps to Korean, en maps to English, ja maps to Japanese, es maps to Spanish)
+- agent_prompt_language response maps to language.agent_prompt_language
+
+Step 8: Runs Tab 1 validation checkpoint:
+- Check language is valid
+- Verify consistency
+
+Step 9: Delegates atomic update to UnifiedConfigManager from moai-workflow-project:
+- Manager handles backup and rollback internally
+- Manager performs deep merge (including auto-updated conversation_language_name)
+- Manager verifies final structure
+
+Step 10: Receives result from Manager:
+- Success: Report changes made (4 fields: user.name, conversation_language, conversation_language_name [auto], agent_prompt_language)
+- Failure: Report error from Skill with recovery suggestions
 
 #### Tab 3 Validation Example (Complex - NEW v2.0.0)
 
-User runs: `/moai:0-project setting` (or `/moai:0-project setting tab_3_git_strategy`)
+User runs: /moai:0-project setting (or /moai:0-project setting tab_3_git_strategy)
 
-```
 Step 1: Load Tab 3 (tab_3_git_strategy) - 6 batches total
-Step 2: Execute Batch 3.0 (Workflow Mode Selection)
-  - User selects: Personal, Team, or Hybrid
-  - Validation: Confirm mode selection
+
+Step 2: Execute Batch 3.0 (Workflow Mode Selection):
+- User selects: Personal, Team, or Hybrid
+- Validation: Confirm mode selection
+
 Step 3: CONDITIONAL LOGIC - Based on mode:
 
-  IF mode = Personal:
-    - Execute Batch 3.1 (Personal core settings)
-    - Execute Batch 3.2 (Personal branch & cleanup)
-    - Execute Batch 3.3 (Personal protection & merge)
-    - Skip Batches 3.4, 3.5, 3.6 (Team batches)
-
-  ELSE IF mode = Team:
-    - Skip Batches 3.1, 3.2, 3.3 (Personal batches)
-    - Execute Batch 3.4 (Team core settings)
-    - Execute Batch 3.5 (Team branch & protection)
-    - Execute Batch 3.6 (Team safety & merge)
-
-  ELSE IF mode = Hybrid:
-    - Execute ALL batches (3.1-3.6) for full flexibility
-
-Step 4: Run Tab 3 validation checkpoint
-  - Validate mode selection consistency
-  - Check Personal/Team conflicts
-    - Example: If Personal: base_branch should be "main" (not "develop")
-    - Example: If Team: prevent_main_direct_merge should be true
-    - Example: If Team: default_pr_base must be "develop" or "main"
-  - Branch naming consistency
-  - Let user confirm or retry if conflicts found
+If mode is Personal:
+- Execute Batch 3.1 (Personal core settings)
+- Execute Batch 3.2 (Personal branch and cleanup)
+- Execute Batch 3.3 (Personal protection and merge)
+- Skip Batches 3.4, 3.5, 3.6 (Team batches)
+
+If mode is Team:
+- Skip Batches 3.1, 3.2, 3.3 (Personal batches)
+- Execute Batch 3.4 (Team core settings)
+- Execute Batch 3.5 (Team branch and protection)
+- Execute Batch 3.6 (Team safety and merge)
+
+If mode is Hybrid:
+- Execute ALL batches (3.1-3.6) for full flexibility
+
+Step 4: Run Tab 3 validation checkpoint:
+- Validate mode selection consistency
+- Check Personal/Team conflicts:
+  - Personal mode: base_branch should be main (not develop)
+  - Team mode: prevent_main_direct_merge should be true
+  - Team mode: default_pr_base must be develop or main
+- Branch naming consistency
+- Let user confirm or retry if conflicts found
 
 Step 5: Merge all executed batches into single update object
-Step 6: Delegate atomic update to UnifiedConfigManager from moai-workflow-project
-  - Manager handles backup/rollback internally
-  - Manager performs deep merge with final validation
+
+Step 6: Delegate atomic update to UnifiedConfigManager from moai-workflow-project:
+- Manager handles backup and rollback internally
+- Manager performs deep merge with final validation
 
 Step 7: Report all 29 settings changes (or 16-20 depending on mode)
-```
 
 #### Multi-Tab Workflow Example
 
-User runs: `/moai:0-project setting` (always interactive, no tab_ID) → Tab Selection Screen
+User runs: /moai:0-project setting (always interactive, no tab_ID) to reach Tab Selection Screen
 
-```
 Flow:
-1. Show Tab Selection Screen (Which settings tab would you like to modify?)
-2. User selects tab or "Modify All Tabs"
-3. Execute selected tab
-   - Tab 1 (REQUIRED): User & Language (1 batch, 3 questions)
-   - Tab 2 (RECOMMENDED): Project Info (2 batches, 4 questions in batch 2.1 + 0 questions auto-processing in batch 2.2)
-   - Tab 3 (RECOMMENDED): Git Strategy (6 batches, 23 questions total, conditional by mode)
-     * Batch 3.0: Mode selection (1 question)
-     * Personal mode: Batches 3.1-3.3 (12 questions)
-     * Team mode: Batches 3.4-3.6 (10 questions)
-     * Hybrid mode: All batches (22 questions)
-   - Tab 4 (OPTIONAL): Quality & Reports (2 batches, 7 questions)
-   - Tab 5 (OPTIONAL): System & GitHub (2 batches, 8 questions)
-4. After tab completion, ask: "Would you like to modify another settings tab?"
-   - No, finish settings (exit)
-   - Select another tab (return to step 1)
-5. Final atomic update after user finishes all selected tabs
+
+Step 1: Show Tab Selection Screen (Which settings tab would you like to modify?)
+
+Step 2: User selects tab or Modify All Tabs
+
+Step 3: Execute selected tab:
+- Tab 1 (REQUIRED): User and Language (1 batch, 3 questions)
+- Tab 2 (RECOMMENDED): Project Info (2 batches, 2 questions in batch 2.1 plus 0 questions auto-processing in batch 2.2)
+- Tab 3 (RECOMMENDED): Git Strategy (10 batches, 26 questions total, conditional by mode)
+  - Batch 3.0a: GitHub Profile (1 question) - always shown
+  - Batch 3.0: Mode selection (1 question)
+  - Manual mode: Batches 3.1-3.2 (5 questions)
+  - Personal mode: Batches 3.3-3.5 (9 questions)
+  - Team mode: Batches 3.6-3.9 (12 questions)
+- Tab 4 (OPTIONAL): Quality and Reports (2 batches, 7 questions)
+- Tab 5 (OPTIONAL): System and GitHub (2 batches, 8 questions)
+
+Step 4: After tab completion, ask: Would you like to modify another settings tab?
+- Option: No, finish settings (exit)
+- Option: Select another tab (return to step 1)
+
+Step 5: Final atomic update after user finishes all selected tabs
 
 Tab-level behavior:
-  - If user cancels mid-tab, changes NOT saved
-  - If tab validation fails, user can retry or skip tab
-  - After ALL selected tabs complete successfully, perform final atomic update
-  - Auto-processing happens during atomic update (e.g., conversation_language_name, locale)
-  - Tab 3 conditional batches respect mode selection (shown/hidden based on git_strategy.mode)
+- If user cancels mid-tab, changes NOT saved
+- If tab validation fails, user can retry or skip tab
+- After ALL selected tabs complete successfully, perform final atomic update
+- Auto-processing happens during atomic update (for example, conversation_language_name, locale)
+- Tab 3 conditional batches respect mode selection (shown or hidden based on git_strategy.mode)
 
 Tab completion order (recommended):
-  - Tab 1 (REQUIRED): Foundation language settings
-  - Tab 2: Project metadata
-  - Tab 3: Git workflow strategy
-  - Tab 4: Quality principles
-  - Tab 5: System integration
-```
+- Tab 1 (REQUIRED): Foundation language settings
+- Tab 2: Project metadata
+- Tab 3: Git workflow strategy (includes GitHub Profile)
+- Tab 4: Quality principles
+- Tab 5: System integration
 
 ### Tab Schema Structure
 
-```json
-{
-  "version": "1.0.0",
-  "tabs": [
-    {
-      "id": "tab_1_user_language",
-      "label": "Tab 1: User & Language",
-      "batches": [
-        {
-          "batch_id": "1.1",
-          "questions": [
-            {
-              "question": "...",
-              "header": "...",
-              "field": "user.name",
-              "type": "text_input|select_single|select_multiple|number_input",
-              "multiSelect": false,
-              "options": [...],
-              "current_value": "...",
-              "required": true
-            }
-          ]
-        }
-      ]
-    }
-  ],
-  "navigation_flow": {
-    "completion_order": ["tab_1", "tab_2", "tab_3", "tab_4", "tab_5"],
-    "validation_sequence": [
-      "Tab 1 checkpoint",
-      "Tab 3 checkpoint",
-      "Final validation"
-    ]
-  }
-}
-```
+The tab schema JSON file contains the following structure:
+
+Root Level:
+- version: Schema version (for example, 1.0.0)
+- tabs: Array of tab definitions
+- navigation_flow: Navigation and validation configuration
+
+Tab Definition:
+- id: Tab identifier (for example, tab_1_user_language)
+- label: Display label (for example, Tab 1: User and Language)
+- batches: Array of batch definitions
+
+Batch Definition:
+- batch_id: Batch identifier (for example, 1.1)
+- questions: Array of question definitions
+
+Question Definition:
+- question: Question text displayed to user
+- header: Section header text
+- field: Configuration path (for example, user.name)
+- type: Input type (text_input, select_single, select_multiple, or number_input)
+- multiSelect: Boolean for multi-select capability
+- options: Array of option definitions
+- current_value: Current configuration value
+- required: Boolean indicating if field is required
+
+Navigation Flow:
+- completion_order: Array of tab IDs in recommended order (tab_1, tab_2, tab_3, tab_4, tab_5)
+- validation_sequence: Array of validation checkpoints (Tab 1 checkpoint, Tab 3 checkpoint, Final validation)
 
 ### Critical Rules
 
@@ -838,7 +1041,7 @@ Language:
 
 ---
 
-##  PHASE 2.5: Save Phase Context
+## PHASE 2.5: Save Phase Context
 
 Goal: Persist phase execution results for explicit context passing to subsequent commands.
 
@@ -846,37 +1049,34 @@ Goal: Persist phase execution results for explicit context passing to subsequent
 
 After manager-project agent completes, extract the following information:
 
-- Project metadata: name, mode, language, GitHub Profile Name
+- Project metadata: name, description, language
 - Files created: List of generated files with absolute paths
 - Tech stack: Primary codebase language
 - Next phase: Recommended next command (1-plan)
 
 ### Step 2: Delegate Context Saving to manager-project
 
-The manager-project agent handles all context saving:
+The manager-project agent handles all context saving.
 
-```markdown
 Context data to persist:
-
-- Phase: "0-project"
-- Mode: INITIALIZATION|AUTO-DETECT|SETTINGS|UPDATE
-- Timestamp: ISO8601 UTC
-- Status: completed|failed
+- Phase: 0-project
+- Mode: INITIALIZATION, AUTO-DETECT, SETTINGS, or UPDATE
+- Timestamp: ISO8601 UTC format
+- Status: completed or failed
 - Outputs:
   - project_name
-  - mode (personal|team)
+  - project_description
   - language (conversation_language)
   - tech_stack (detected primary language)
-- Files created: [list of absolute paths]
-- Next phase: "1-plan"
+  - github_profile (from Tab 3)
+- Files created: list of absolute paths
+- Next phase: 1-plan
 
 Agent delegates to UnifiedConfigManager from moai-workflow-project:
-
 - Save context via ContextManager
 - Handle file path validation
 - Implement error recovery (non-blocking)
-- Report success/failure
-```
+- Report success or failure
 
 Error Handling Strategy:
 
@@ -886,7 +1086,7 @@ Error Handling Strategy:
 
 ---
 
-##  PHASE 3: Completion & Next Steps
+## PHASE 3: Completion and Next Steps
 
 Goal: Guide user to next action in their selected language.
 
@@ -911,7 +1111,7 @@ Critical: NO EMOJIS in AskUserQuestion fields. Use clear text only.
 
 ---
 
-##  Critical Rules
+## Critical Rules
 
 ### Mode Execution
 
@@ -1027,7 +1227,7 @@ IMPACT: Deferred language selection complicates initial setup.
 
 ---
 
-##  Output Format
+## Output Format
 
 Responses and status reports must follow structured XML format for clarity and automated processing:
 
@@ -1062,14 +1262,27 @@ IMPACT: Unstructured output reduces ability to track execution state and causes
 
 ---
 
-##  Quick Reference
+## Quick Reference
+
+Scenario: First-time setup
+- Mode: INITIALIZATION
+- Entry Point: /moai:0-project (no config)
+- Key Phases: Read language then Interview then Docs
+
+Scenario: Existing project
+- Mode: AUTO-DETECT
+- Entry Point: /moai:0-project (config exists)
+- Key Phases: Read language then Display then Options
 
-| Scenario             | Mode           | Entry Point                       | Key Phases                                                     |
-| -------------------- | -------------- | --------------------------------- | -------------------------------------------------------------- |
-| First-time setup     | INITIALIZATION | `/moai:0-project` (no config)     | Read language → Interview → Docs                               |
-| Existing project     | AUTO-DETECT    | `/moai:0-project` (config exists) | Read language → Display → Options                              |
-| Modify config        | SETTINGS       | `/moai:0-project setting`         | Interactive tab selection → Conditional batches → Skill update |
-| After package update | UPDATE         | `/moai:0-project update`          | Preserve language → Template merge → Announce                  |
+Scenario: Modify config
+- Mode: SETTINGS
+- Entry Point: /moai:0-project setting
+- Key Phases: Interactive tab selection then Conditional batches then Skill update
+
+Scenario: After package update
+- Mode: UPDATE
+- Entry Point: /moai:0-project update
+- Key Phases: Preserve language then Template merge then Announce
 
 Associated Skills:
 
@@ -1104,37 +1317,20 @@ Improvements in v2.0.0:
 
 After command execution completes, use AskUserQuestion tool to guide user to next action:
 
-```python
-AskUserQuestion({
-    "questions": [{
-        "question": "Project setup is complete. What would you like to do next?",
-        "header": "Next Steps",
-        "multiSelect": false,
-        "options": [
-            {
-                "label": "Write Specification",
-                "description": "Execute /moai:1-plan to define feature specifications"
-            },
-            {
-                "label": "Review Project Structure",
-                "description": "Check current project status and settings"
-            },
-            {
-                "label": "Start New Session",
-                "description": "Initialize workspace and start fresh"
-            }
-        ]
-    }]
-})
-```
+Question: Project setup is complete. What would you like to do next?
+Header: Next Steps
+MultiSelect: false
+Options:
+- Write Specification - Execute /moai:1-plan to define feature specifications
+- Review Project Structure - Check current project status and settings
+- Start New Session - Initialize workspace and start fresh
 
 Important:
-
 - Use conversation language from config
 - No emojis in any AskUserQuestion fields
 - Always provide clear next step options
 
-##  EXECUTION DIRECTIVE
+## EXECUTION DIRECTIVE
 
 You must NOW execute the command following the "Execution Philosophy" described above.