moai-adk 0.9.0__py3-none-any.whl → 0.15.1__py3-none-any.whl

moai_adk/templates/.claude/commands/alfred/2-run.md

@@ -1,10 +1,6 @@
 ---
 name: alfred:2-run
-description: "Execute planned work (TDD implementation, prototyping, documentation, etc.)"
-# Translations:
-# - ko: "계획된 작업 실행 (TDD 구현, 프로토타이핑, 문서화 등)"
-# - ja: "計画されたタスクの実行（TDD実装、プロトタイピング、ドキュメント作成など）"
-# - zh: "执行计划任务（TDD实现、原型开发、文档编写等）"
+description: "Execute TDD implementation cycle"
 argument-hint: "SPEC-ID - All with SPEC ID to implement (e.g. SPEC-001) or all \"SPEC Implementation\""
 allowed-tools:
   - Read
@@ -25,6 +21,12 @@ allowed-tools:
 
 # ⚒️ MoAI-ADK Phase 2: Run the plan - Flexible implementation strategy
 > **Note**: Interactive prompts use `AskUserQuestion tool (documented in moai-alfred-interactive-questions skill)` for TUI selection menus. The skill is loaded on-demand when user interaction is required.
+>
+> **Batched Design**: All AskUserQuestion calls follow batched design principles (1-4 questions per call) to minimize user interaction turns. See CLAUDE.md section "Alfred Command Completion Pattern" for details.
+
+<!-- @CODE:ALF-WORKFLOW-002:CMD-RUN -->
+
+**4-Step Workflow Integration**: This command implements Step 3 of Alfred's workflow (Task Execution with TodoWrite tracking). See CLAUDE.md for full workflow details.
 
 ## 🎯 Command Purpose
 
@@ -154,12 +156,12 @@ STEP 1 consists of **two independent phases** to provide flexible workflow based
 Invoking the Task tool (Explore agent):
 - subagent_type: "Explore"
 - description: "Explore existing code structures and patterns"
-- prompt: "Please explore existing code related to SPEC-$ARGUMENTS:
- - Similar function implementation code (src/)
- - Test patterns for reference (tests/)
- - Architectural patterns and design patterns
- - Current libraries and versions (package.json, requirements.txt)
- thoroughness level: medium"
+- prompt: "SPEC-$ARGUMENTS와 관련된 기존 코드를 탐색해주세요:
+ - 유사한 기능 구현 코드 (src/)
+ - 참고할 테스트 패턴 (tests/)
+ - 아키텍처 패턴 및 디자인 패턴
+ - 현재 라이브러리 및 버전 (package.json, requirements.txt)
+ 상세도 수준: medium"
 ```
 
 **Note**: If you skip Phase A, proceed directly to Phase B.
@@ -178,15 +180,15 @@ This phase is **always required** regardless of whether Phase A was executed.
 Task tool call:
 - subagent_type: "implementation-planner"
 - description: "SPEC analysis and establishment of execution strategy"
-- prompt: "Please analyze the SPEC of $ARGUMENTS and establish an execution plan.
- It must include the following:
- 1. SPEC requirements extraction and complexity assessment
- 2. Library and tool selection (using WebFetch)
- 3. TAG chain design
- 4. Step-by-step execution plan
- 5. Risks and response plans
- 6. Create action plan and use `AskUserQuestion tool (documented in moai-alfred-interactive-questions skill)` to confirm the next action with the user
- (Optional) Explore results: $EXPLORE_RESULTS"
+- prompt: "$ARGUMENTS의 SPEC을 분석하고 실행 계획을 수립해주세요.
+ 다음을 포함해야 합니다:
+ 1. SPEC 요구사항 추출 및 복잡도 평가
+ 2. 라이브러리 및 도구 선택 (WebFetch 사용)
+ 3. TAG 체인 설계
+ 4. 단계별 실행 계획
+ 5. 위험 요소 및 대응 계획
+ 6. 행동 계획을 작성하고 `AskUserQuestion 도구 (moai-alfred-interactive-questions 스킬 참고)`로 사용자와 다음 단계를 확인합니다
+ (선택사항) 탐색 결과: $EXPLORE_RESULTS"
 ```
 
 **Note**: If Phase A was executed, pass the exploration results via `$EXPLORE_RESULTS` variable.
@@ -229,9 +231,191 @@ After reviewing the action plan, select one of the following:
 
 ---
 
+## Implementation Strategy Approval
+
+After the execution plan is ready, Alfred uses `AskUserQuestion` tool (documented in moai-alfred-interactive-questions skill) to obtain explicit user approval before proceeding to TDD implementation.
+
+**Example AskUserQuestion Call**:
+```python
+AskUserQuestion(
+    questions=[
+        {
+            "question": "Implementation plan is ready. How would you like to proceed?",
+            "header": "Implementation Approval",
+            "multiSelect": false,
+            "options": [
+                {
+                    "label": "✅ Proceed with TDD",
+                    "description": "Start RED → GREEN → REFACTOR cycle"
+                },
+                {
+                    "label": "🔍 Research First",
+                    "description": "Invoke Explore agent to study existing code patterns"
+                },
+                {
+                    "label": "🔄 Modify Strategy",
+                    "description": "Request changes to implementation approach"
+                },
+                {
+                    "label": "⏸️ Postpone",
+                    "description": "Save plan and return later"
+                }
+            ]
+        }
+    ]
+)
+```
+
+**Response Processing**:
+- **"✅ Proceed with TDD"** (`answers["0"] === "✅ Proceed with TDD"`) → Execute Phase 2
+  - Proceed directly to STEP 2 (TDD implementation)
+  - Invoke tdd-implementer agent with approved plan
+  - Begin RED phase (write failing tests)
+  - Display: "🔴 Starting RED phase..."
+
+- **"🔍 Research First"** (`answers["0"] === "🔍 Research First"`) → Run exploration first
+  - Invoke Explore agent to analyze existing codebase
+  - Pass exploration results to implementation-planner
+  - Re-generate plan with research insights
+  - Re-present plan for approval
+  - Display: "🔍 Codebase exploration complete. Plan updated."
+
+- **"🔄 Modify Strategy"** (`answers["0"] === "🔄 Modify Strategy"`) → Revise plan
+  - Collect strategy modification requests from user
+  - Update implementation plan with changes
+  - Re-present for approval (recursive)
+  - Display: "🔄 Plan modified. Please review updated strategy."
+
+- **"⏸️ Postpone"** (`answers["0"] === "⏸️ Postpone"`) → Save and resume later
+  - Save plan to `.moai/specs/SPEC-{ID}/plan.md`
+  - Commit with message "plan(spec): Save implementation plan for SPEC-{ID}"
+  - User can resume with `/alfred:2-run SPEC-{ID}`
+  - Display: "⏸️ Plan saved. Resume with `/alfred:2-run SPEC-{ID}`"
+
+---
+
 ## 🚀 STEP 2: Execute task (after user approval)
 
-After user approval (gathered through `AskUserQuestion tool (documented in moai-alfred-interactive-questions skill)`), **call the tdd-implementer agent using the Task tool**.
+After user approval (collected via the AskUserQuestion decision point above), **call the tdd-implementer agent using the Task tool**.
+
+---
+
+### 2.0.5 Domain Readiness Check (Automatic - Before Implementation)
+
+**Purpose**: Load domain-expert agents as "implementation advisors" based on SPEC.stack metadata
+
+**When to run**: After user approval, BEFORE invoking tdd-implementer
+
+**Detection Logic**:
+
+Alfred reads the SPEC metadata to identify required domains:
+
+```bash
+# Read SPEC metadata
+spec_metadata=$(grep "^domains:" .moai/specs/SPEC-{ID}/spec.md)
+
+# Or read from config.json
+selected_domains=$(jq -r '.stack.selected_domains[]' .moai/config.json)
+```
+
+**Domain Expert Advisory Pattern**:
+
+| Domain | Readiness Check | Advisory Focus |
+|--------|----------------|----------------|
+| **Frontend** | Component structure, testing strategy, state management | Component hierarchy, React/Vue best practices, UI testing patterns |
+| **Backend** | API contract, database schema, async patterns | RESTful design, database indexing, error handling, authentication |
+| **DevOps** | Docker readiness, environment variables, health checks | Containerization, CI/CD integration, deployment strategies |
+| **Database** | Schema design, migration strategy, indexing | Data modeling, query optimization, migration safety |
+| **Data Science** | Data pipeline design, notebook structure | ETL patterns, data validation, model versioning |
+| **Mobile** | Platform-specific requirements, app lifecycle | Native integration, state management, offline support |
+
+**Example Invocation** (Frontend + Backend detected):
+
+```python
+# Read SPEC metadata
+spec_domains = ["frontend", "backend"]  # from SPEC frontmatter
+
+# Invoke domain experts BEFORE tdd-implementer
+for domain in spec_domains:
+    if domain == "frontend":
+        Task(
+            subagent_type="Explore",
+            prompt="""You are consulting as frontend-expert for TDD implementation.
+
+SPEC: [SPEC-UI-001 - User Dashboard Component]
+
+Provide implementation readiness check:
+1. Component structure recommendations
+2. State management approach (Redux/Zustand/Context)
+3. Testing strategy (Jest + Testing Library)
+4. Accessibility requirements
+5. Performance optimization tips
+
+Output: Brief advisory for tdd-implementer (3-4 key points)"""
+        )
+
+    if domain == "backend":
+        Task(
+            subagent_type="Explore",
+            prompt="""You are consulting as backend-expert for TDD implementation.
+
+SPEC: [SPEC-API-001 - Authentication Endpoints]
+
+Provide implementation readiness check:
+1. API contract validation
+2. Database schema requirements
+3. Authentication/authorization patterns
+4. Error handling strategy
+5. Async processing considerations
+
+Output: Brief advisory for tdd-implementer (3-4 key points)"""
+        )
+```
+
+**Output Format** (Stored in SPEC plan.md):
+
+```markdown
+## Domain Expert Advisory (Implementation Phase)
+
+### Frontend Readiness
+- Component structure: Use compound component pattern for Dashboard
+- State management: Recommend Zustand for lightweight state
+- Testing: Prioritize user interaction tests over implementation details
+- Performance: Implement React.memo for expensive components
+
+### Backend Readiness
+- API contract: OpenAPI 3.0 spec generated from FastAPI
+- Database schema: Add index on user_id and created_at columns
+- Authentication: Use JWT with refresh token rotation
+- Async: Use background tasks for email notifications
+```
+
+**Integration with tdd-implementer**:
+
+```python
+# Pass domain expert feedback to tdd-implementer
+Task(
+    subagent_type="tdd-implementer",
+    prompt="""You are tdd-implementer agent.
+
+SPEC: SPEC-{ID}
+
+DOMAIN EXPERT ADVISORY:
+{domain_expert_feedback}
+
+Execute TDD implementation considering domain expert guidance.
+Follow RED → GREEN → REFACTOR cycle with domain best practices.
+
+$ARGUMENTS"""
+)
+```
+
+**Graceful Degradation**:
+- If SPEC.stack.domains missing → Skip advisory (greenfield implementation)
+- If domain expert unavailable → Continue with tdd-implementer only
+- Advisory is non-blocking (implementation proceeds regardless)
+
+---
 
 ### ⚙️ How to call an agent
 
@@ -241,35 +425,39 @@ After user approval (gathered through `AskUserQuestion tool (documented in moai-
 Call the Task tool:
 - subagent_type: "tdd-implementer"
 - description: "Execute task with TDD implementation"
-- prompt: """You are tdd-implementer agent.
-
-LANGUAGE CONFIGURATION:
-- conversation_language: {{CONVERSATION_LANGUAGE}}
-- language_name: {{CONVERSATION_LANGUAGE_NAME}}
-
-CRITICAL INSTRUCTION:
-Code and technical output MUST be in English.
-Code comments MAY be in {{CONVERSATION_LANGUAGE}} if appropriate.
-Test descriptions and documentation can use {{CONVERSATION_LANGUAGE}}.
-
-SKILL INVOCATION:
-Use explicit Skill() calls when needed:
-- Skill("moai-alfred-language-detection") for project language detection
-- Skill("moai-lang-python") or language-specific Skills for best practices
-- Skill("moai-essentials-debug") when tests fail
-- Skill("moai-essentials-refactor") during REFACTOR phase
-
-TASK: Execute the task according to the plan approved in STEP 1.
-
-For TDD scenario:
-- Perform RED → GREEN → REFACTOR cycle
-- Perform the following for each TAG:
-  1. RED Phase: Write a test that fails with the @TEST:ID tag
-  2. GREEN Phase: Minimal implementation with the @CODE:ID tag
-  3. REFACTOR Phase: Improve code quality
-  4. Verify TAG completion conditions and proceed to the next TAG
-
-Execute on: $ARGUMENTS"""
+- prompt: """당신은 tdd-implementer 에이전트입니다.
+
+언어 설정:
+- 대화_언어: {{CONVERSATION_LANGUAGE}}
+- 언어명: {{CONVERSATION_LANGUAGE_NAME}}
+
+중요 지시사항:
+**Code and technical output MUST be in English.** This ensures global compatibility and maintainability.
+
+코드 문법 및 키워드: 영어 (고정).
+코드 주석:
+- 로컬 프로젝트 코드: 반드시 {{CONVERSATION_LANGUAGE}}로 작성
+- 패키지 코드 (src/moai_adk/): 반드시 영어로 작성 (글로벌 배포용)
+테스트 설명 및 문서: 반드시 {{CONVERSATION_LANGUAGE}}로 작성.
+
+스킬 호출:
+필요 시 명시적 Skill() 호출 사용:
+- Skill("moai-alfred-language-detection") - 프로젝트 언어 감지
+- Skill("moai-lang-python") 또는 언어별 스킬 - 베스트 프랙티스
+- Skill("moai-essentials-debug") - 테스트 실패 시
+- Skill("moai-essentials-refactor") - REFACTOR 단계에서
+
+작업: STEP 1에서 승인된 계획에 따라 작업을 실행합니다.
+
+TDD 시나리오의 경우:
+- RED → GREEN → REFACTOR 사이클 수행
+- 각 TAG에 대해 다음을 수행:
+  1. RED 단계: @TEST:ID 태그로 실패하는 테스트 작성
+  2. GREEN 단계: @CODE:ID 태그로 최소한의 구현
+  3. REFACTOR 단계: 코드 품질 개선
+  4. TAG 완료 조건 확인 및 다음 TAG 진행
+
+실행 대상: $ARGUMENTS"""
 ```
 
 ## 🔗 TDD optimization for each language
@@ -526,7 +714,7 @@ Only if the user selects **"Proceed"** or **"Start"** will Alfred call the tdd-i
 
 ## 🧠 Context Management
 
-> For more information: `.moai/memory/development-guide.md` - see section "Context Engineering"
+> For more information: Skill("moai-alfred-dev-guide") - see section "Context Engineering"
 
 ### Core strategy of this command
 
@@ -536,6 +724,66 @@ Only if the user selects **"Proceed"** or **"Start"** will Alfred call the tdd-i
 
 ---
 
+## Final Step
+
+### After STEP 3 (git-manager) Completes
+
+Alfred calls AskUserQuestion to collect user's next action:
+
+**Example AskUserQuestion Call**:
+```python
+AskUserQuestion(
+    questions=[
+        {
+            "question": "Implementation is complete. What would you like to do next?",
+            "header": "Next Steps",
+            "multiSelect": false,
+            "options": [
+                {
+                    "label": "📚 Synchronize Documentation",
+                    "description": "Proceed to /alfred:3-sync for documentation synchronization"
+                },
+                {
+                    "label": "🔨 Implement More Features",
+                    "description": "Continue with /alfred:2-run SPEC-XXX for next feature"
+                },
+                {
+                    "label": "🔄 New Session",
+                    "description": "Execute /clear for better context management (recommended)"
+                },
+                {
+                    "label": "✅ Complete",
+                    "description": "Finish current session"
+                }
+            ]
+        }
+    ]
+)
+```
+
+**Response Processing**:
+- **"📚 Synchronize Documentation"** (`answers["0"] === "📚 Synchronize Documentation"`) → Proceed to `/alfred:3-sync`
+  - Display: "Starting documentation synchronization..."
+  - User can execute: `/alfred:3-sync auto`
+  - This verifies TAGs, updates docs, and prepares for PR merge
+
+- **"🔨 Implement More Features"** (`answers["0"] === "🔨 Implement More Features"`) → Continue implementation
+  - Display: "Ready for next feature implementation..."
+  - User can run: `/alfred:2-run SPEC-YYY` for another feature
+  - Maintains current session context
+
+- **"🔄 New Session"** (`answers["0"] === "🔄 New Session"`) → Clear and restart
+  - Display: "⏳ Clearing session for better context management..."
+  - Recommended after large implementations
+  - Next session: Can run any command
+
+- **"✅ Complete"** (`answers["0"] === "✅ Complete"`) → End current workflow
+  - Display: "Implementation workflow complete!"
+  - Recommend next manual steps via `/alfred:3-sync`
+  - User can review work or plan next features
+
+---
+
 ## Next steps
 
 **Recommendation**: For better performance and context management, start a new chat session with the `/clear` or `/new` command before proceeding to the next step.