aiwf 0.1.0 → 0.3.0

package/claude-code/aiwf/ko/.claude/commands/aiwf/aiwf_initialize.md

@@ -0,0 +1,134 @@
+# AIWF 프레임워크 초기화
+
+Initialize the AIWF project management framework through an adaptive, interactive process.
+
+## Create a TODO with EXACTLY these items
+
+1. Scan and analyze the project
+2. Interactive confirmation with user
+3. Check for existing AIWF documents
+4. Guide document creation process
+5. Create first milestone for AIWF
+6. Generate project manifest
+7. Provide next steps
+
+## DETAILS on every TODO item
+
+### 1. Scan and analyze the project
+
+**Detect project characteristics:**
+
+- Check for package.json, requirements.txt, composer.json, etc.
+- Identify project type (Node.js, Python, PHP, etc.)
+- Scan overall project structure
+- Check if this is a new or existing project
+- Look for existing documentation (README, docs/, etc.)
+
+**Keep findings brief** - Just identify the essentials
+
+### 2. Interactive confirmation with user
+
+**Present findings conversationally:**
+
+```
+I found this to be a [project type] project named [detected name].
+Is this correct? Should I proceed with AIWF setup?
+```
+
+**Get user confirmation before continuing**
+
+### 3. Check for existing AIWF documents
+
+**Scan .aiwf/ directory for:**
+
+- Any documents in 01_PROJECT_DOCS/
+- Any milestones in 02_REQUIREMENTS/
+- Any existing sprints or tasks
+- Current manifest status
+
+**Interactive decision:**
+
+- If documents found: "I found existing documents: [list]. Should we work with these or extend them?"
+- If no documents: "No AIWF documents found yet. Do you have any existing project documentation you'd like to copy in before we continue?"
+
+**Allow user to:**
+
+- Use existing documents
+- Add new documents
+- Start fresh
+- Cancel to add documents manually first
+
+### 4. Guide document creation process
+
+**Based on user's choice:**
+
+**If starting fresh or extending:**
+
+- Perform deep analysis of the codebase
+- Identify key components and architecture patterns
+- Create draft ARCHITECTURE.md based on analysis
+- Use Q&A style to refine and complete:
+  - "What's the main purpose of this project?"
+  - "What are the key technical decisions?"
+  - "Any important constraints or requirements?"
+
+**If using existing docs:**
+
+- Import and adapt existing documentation
+- Fill in any AIWF-specific sections
+- Ensure compatibility with framework structure
+
+**Keep it conversational and adaptive**
+
+### 5. Create first milestone for AIWF
+
+**Determine appropriate first milestone:**
+
+- If new project: Start with setup/foundation milestone
+- If existing project: Identify current phase and create appropriate milestone
+
+**Interactive milestone creation:**
+
+- "Based on the project state, I suggest creating milestone: [name]"
+- "What would you like to focus on in this milestone?"
+- Create milestone structure with initial requirements
+- Keep scope realistic and focused
+
+### 6. Generate project manifest
+
+**Automatically generate manifest using:**
+
+- Information gathered during setup
+- Created/imported documentation
+- Current milestone details
+- Project metadata
+
+**No user interaction needed** - Just inform when complete
+
+### 7. Provide next steps
+
+**Customized guidance based on setup:**
+
+```
+✅ AIWF initialized for [project name]!
+
+Current setup:
+- Project type: [type]
+- Current milestone: [milestone]
+- Documents: [created/imported]
+
+Next steps:
+- Review your architecture: 01_PROJECT_DOCS/ARCHITECTURE.md
+- Check milestone requirements: 02_REQUIREMENTS/[milestone]/
+- Start first task: /project:aiwf:create_general_task
+
+Ready to begin development!
+```
+
+## ADAPTIVE PROCESS NOTES
+
+- **Stay conversational** - Ask questions naturally, not like a form
+- **Be smart** - Use AI to understand context and make intelligent suggestions
+- **Allow flexibility** - User can skip, cancel, or modify at any point
+- **Focus on value** - Only create what's useful for the specific project
+- **Keep it simple** - Don't overwhelm with options or details

package/claude-code/aiwf/ko/.claude/commands/aiwf/aiwf_issue_create.md

@@ -0,0 +1,65 @@
+# Create GitHub Issue from Task
+
+Automatically create a GitHub issue based on a task file.
+
+## Create TODO with EXACTLY these 5 items
+
+1. Parse task file and extract information
+2. Generate issue template
+3. Create issue via GitHub API
+4. Update task file with issue number
+5. Report results
+
+## 1 · Parse Task File
+
+Get task ID from <$ARGUMENTS>:
+- Sprint tasks: Search `.aiwf/03_SPRINTS/`
+- General tasks: Search `.aiwf/04_GENERAL_TASKS/`
+
+Extract from task file:
+- Title
+- Description
+- Acceptance criteria
+- Labels (sprint number, task type)
+
+## 2 · Generate Issue Template
+
+```markdown
+## 📋 Task: {task_title}
+
+### Description
+{task_description}
+
+### Acceptance Criteria
+{acceptance_criteria}
+
+### Related Information
+- Task ID: {task_id}
+- Sprint: {sprint_id}
+- Task file: `.aiwf/.../{task_file}`
+```
+
+## 3 · Create GitHub Issue
+
+```bash
+gh issue create \
+  --title "{task_id}: {task_title}" \
+  --body "{issue_body}" \
+  --label "task,{sprint_label}" \
+  --assignee "@me"
+```
+
+Capture the created issue number
+
+## 4 · Update Task File
+
+Add to task file frontmatter:
+```yaml
+github_issue: #{issue_number}
+```
+
+## 5 · Report Results
+
+✅ **Issue Created**: #{issue_number}
+🔗 **Link**: {issue_url}
+📄 **Task**: {task_id}

package/claude-code/aiwf/ko/.claude/commands/aiwf/aiwf_mermaid.md

@@ -0,0 +1,272 @@
+# Mermaid 다이어그램 유지 관리
+
+Instructions for generating, maintaining and updating the mermaid diagrams in the current project's architecture documentation.
+
+## 📋 Overview
+
+The architecture documentation should include comprehensive mermaid diagrams that illustrate:
+
+- System context and component relationships
+- Module dependencies and data flows (150+ modules)
+- Class hierarchies and interactions
+- Service layer patterns and UI architecture
+
+## 📂 Diagram Locations
+
+All architecture diagrams are to be stored in `/docs/architecture/`:
+
+```
+docs/architecture/
+├── README.md                           # Main architecture overview
+├── context_diagram.md                  # System context & data flow
+├── module_overview.md                  # Module relationships (150+ modules)
+└── class_diagrams/
+    ├── core_classes.md                 # Database, DAOs, data processing
+    ├── data_models.md                  # Domain models & database schema
+    └── service_layer.md                # UI architecture & service coordination
+```
+
+## 🛠️ Update Process
+
+### Step 1: Identify Affected Diagrams
+
+Determine which diagrams need updates based on your changes:
+
+| Change Type            | Primary Diagram    | Secondary Diagrams |
+| ---------------------- | ------------------ | ------------------ |
+| New analytics module   | module_overview.md | context_diagram.md |
+| Database schema change | data_models.md     | core_classes.md    |
+| New UI component       | service_layer.md   | module_overview.md |
+| New service/manager    | service_layer.md   | module_overview.md |
+| Architecture refactor  | context_diagram.md | All others         |
+
+### Step 2: Update Mermaid Code
+
+Edit the relevant `.md` files to update mermaid diagram code:
+
+```mermaid
+# Example: Adding a new class to core_classes.md
+class NewAnalyticsService {
+    -CacheManager cache_manager
+    -Logger logger
+    +calculate_advanced_metrics() Dict
+    +generate_insights() List[str]
+}
+
+# Add relationships
+NewAnalyticsService --> CacheManager : uses
+NewAnalyticsService --> DatabaseManager : queries
+```
+
+### Step 3: Validate Diagrams
+
+Test diagram syntax and rendering:
+
+1. **Online validation**: Copy mermaid code to [Mermaid Live Editor](https://mermaid.live/)
+2. **Local preview**: Use VS Code Mermaid extensions
+3. **Check syntax**: Ensure proper mermaid formatting
+
+### Step 4: Update Cross-References
+
+Update any cross-references in documentation:
+
+- Update `docs/architecture/README.md` if adding new diagrams
+- Update navigation links between diagram files
+- Update main project README if architecture changes significantly
+
+## 📝 Mermaid Syntax Guidelines
+
+### Class Diagrams
+
+```mermaid
+classDiagram
+    class ClassName {
+        -private_field: Type
+        +public_method() ReturnType
+        #protected_method(param: Type) void
+    }
+
+    %% Relationships
+    ClassA <|-- ClassB : inherits
+    ClassA *-- ClassC : composition
+    ClassA --> ClassD : uses
+    ClassA ..> ClassE : depends on
+
+    %% Notes
+    note for ClassName "Important implementation details"
+```
+
+### Flowcharts
+
+```mermaid
+flowchart TD
+    A[Start] --> B{Decision}
+    B -->|Yes| C[Action 1]
+    B -->|No| D[Action 2]
+    C --> E[End]
+    D --> E
+
+    %% Styling
+    style A fill:#e1f5fe
+    style E fill:#e8f5e8
+```
+
+### Sequence Diagrams
+
+```mermaid
+sequenceDiagram
+    participant A as Actor
+    participant B as System
+
+    A->>B: Request
+    B->>B: Process
+    B-->>A: Response
+
+    Note over A,B: Important interaction
+```
+
+## 🎨 Styling Guidelines
+
+### Color Scheme
+
+Use consistent colors across all diagrams:
+
+```mermaid
+%% Standard color palette
+style MainComponents fill:#4ecdc4,color:#fff
+style DataLayer fill:#f3e5f5
+style CacheLayer fill:#fff8e1
+style UILayer fill:#e8f5e8
+style ExternalSystems fill:#e1f5fe
+```
+
+### Component Categories
+
+- **🏗️ Core Infrastructure**: `#4ecdc4` (teal)
+- **📊 Analytics/Data**: `#f3e5f5` (light purple)
+- **⚡ Caching/Performance**: `#fff8e1` (light yellow)
+- **🎨 UI Components**: `#e8f5e8` (light green)
+- **🔗 External Systems**: `#e1f5fe` (light blue)
+
+## 📋 Common Update Scenarios
+
+### Adding a New Analytics Module
+
+1. **Update module_overview.md**: Add to Analytics Engine section
+2. **Update class diagrams**: Add detailed class structure if significant
+3. **Update context_diagram.md**: Add if it's a major new capability
+
+```mermaid
+# Example: New trend analysis module
+TREND_ANALYZER[trend_analyzer.py<br/>📈 Advanced Trends]
+TREND_ANALYZER --> DAILY_CALC
+TREND_ANALYZER --> CACHE
+```
+
+### New UI Component or Widget
+
+1. **Update service_layer.md**: Add class definition and relationships
+2. **Update module_overview.md**: Add to UI Layer section
+3. **Consider component factory updates**
+
+```mermaid
+# Example: New dashboard widget
+class NewDashboardWidget {
+    -MetricsCalculator calculator
+    -ComponentFactory factory
+    +setup_ui() void
+    +refresh_data() void
+}
+QWidget <|-- NewDashboardWidget : inherits
+```
+
+### Database Schema Changes
+
+1. **Update data_models.md**: Modify ER diagram and class definitions
+2. **Update core_classes.md**: Update DAO methods if needed
+3. **Document migration requirements**
+
+### New Service or Manager Class
+
+1. **Update service_layer.md**: Add to appropriate service category
+2. **Update relationships**: Show dependencies and usage patterns
+3. **Update module_overview.md**: Add service layer connections
+
+## 🔍 Validation Checklist
+
+Before committing diagram updates:
+
+- [ ] **Syntax Valid**: Diagram renders without errors
+- [ ] **Consistent Styling**: Uses standard color scheme
+- [ ] **Accurate Relationships**: Reflects actual code relationships
+- [ ] **Clear Labels**: All components clearly labeled
+- [ ] **Cross-References Updated**: Navigation links work
+- [ ] **README Updated**: Main architecture README reflects changes
+
+## 🤖 Automation & Maintenance Scripts
+
+### Useful Commands for Analysis
+
+```bash
+# Find all Python classes in the codebase
+find src/ -name "*.py" -exec grep -l "^class " {} \; | sort
+
+# Check module imports to understand dependencies
+grep -r "^from src\." src/ | cut -d: -f2 | sort | uniq
+
+# Find new files since last commit
+git diff --name-only HEAD~1 | grep "\.py$"
+
+# Count modules by package
+find src/ -name "*.py" | cut -d/ -f2 | sort | uniq -c
+```
+
+### Maintenance Tasks
+
+1. **Quarterly Review**: Compare diagrams against actual codebase structure
+2. **Release Preparation**: Ensure all diagrams reflect release state
+3. **Refactoring Support**: Update diagrams during major refactors
+4. **New Developer Onboarding**: Keep diagrams current for documentation
+
+## 🚨 Best Practices
+
+### Do's
+
+- ✅ **Keep diagrams focused**: One primary concept per diagram
+- ✅ **Use consistent naming**: Match actual class/module names
+- ✅ **Add explanatory notes**: Include important design decisions
+- ✅ **Regular updates**: Keep diagrams current with code changes
+- ✅ **Validate syntax**: Always test before committing
+
+### Don'ts
+
+- ❌ **Avoid over-complexity**: Don't include every minor detail
+- ❌ **Don't duplicate**: Each relationship should appear in most appropriate diagram
+- ❌ **Avoid generic names**: Use specific, meaningful component names
+- ❌ **Don't ignore styling**: Consistent colors improve readability
+- ❌ **Don't skip validation**: Always check diagram rendering
+
+## 📞 Support & Resources
+
+### Documentation Resources
+
+- [Mermaid Documentation](https://mermaid-js.github.io/mermaid/)
+- [Mermaid Live Editor](https://mermaid.live/) - For testing diagrams
+- [VS Code Mermaid Extension](https://marketplace.visualstudio.com/items?itemName=bierner.markdown-mermaid)
+
+### Quick Reference
+
+- **Architecture overview**: `/docs/architecture/README.md`
+- **System context**: `/docs/architecture/context_diagram.md`
+- **Module relationships**: `/docs/architecture/module_overview.md`
+- **Class details**: `/docs/architecture/class_diagrams/`
+
+### Getting Help
+
+1. **Reference existing patterns**: Look at similar components in current diagrams
+2. **Check diagram history**: Use git to see how similar changes were handled
+3. **Ask in code review**: Get feedback on architectural accuracy
+
+---
+
+_Keep architecture diagrams accurate, useful, and maintainable as the project evolves. Focus on clarity and consistency to support both current development and future maintenance._

package/claude-code/aiwf/ko/.claude/commands/aiwf/aiwf_pr_create.md

@@ -0,0 +1,76 @@
+# Create Pull Request After Task Completion
+
+Create a GitHub Pull Request after task completion and link it with related issues.
+
+## Create TODO with EXACTLY these 6 items
+
+1. Check current branch and changes
+2. Generate PR body template
+3. Create GitHub PR
+4. Link issue with PR
+5. Assign reviewers
+6. Report results
+
+## 1 · Check Branch and Changes
+
+Run in parallel:
+- `git branch --show-current`: Check current branch
+- `git log main..HEAD --oneline`: Commit history
+- `git diff main...HEAD --stat`: Changed files statistics
+
+Extract GitHub issue number from task file
+
+## 2 · Generate PR Body Template
+
+```markdown
+## 🎯 Overview
+Completed implementation of {task_title}.
+
+## 📝 Changes
+{commit_list}
+
+## 📊 Changed Files
+{file_statistics}
+
+## ✅ Checklist
+- [ ] Tests pass
+- [ ] Code review completed
+- [ ] Documentation updated
+
+## 🔗 Related Information
+- Closes #{issue_number}
+- Task: {task_id}
+```
+
+## 3 · Create GitHub PR
+
+```bash
+gh pr create \
+  --title "{task_id}: {task_title}" \
+  --body "$(cat <<'EOF'
+{pr_body}
+EOF
+)" \
+  --base main \
+  --head {branch_name}
+```
+
+## 4 · Link Issue with PR
+
+Automatically included in PR body:
+- `Closes #{issue_number}`: Auto-close issue
+- `Relates to #{issue_number}`: Show relationship
+
+## 5 · Assign Reviewers
+
+```bash
+gh pr edit {pr_number} \
+  --add-reviewer {reviewer_username}
+```
+
+## 6 · Report Results
+
+✅ **PR Created**: #{pr_number}
+🔗 **Link**: {pr_url}
+🎯 **Linked Issue**: #{issue_number}
+👥 **Reviewers**: {reviewers}

package/claude-code/aiwf/ko/.claude/commands/aiwf/aiwf_prime.md

@@ -0,0 +1,9 @@
+# 지식 프라임
+
+Prime yourself with basic information about this project.
+Make sure you are aware of the environment.
+
+## USE **PARALLEL AGENTS** to
+
+- READ .aiwf/01_PROJECT_DOCS/ARCHITECTURE.md for basic Project Information
+- READ .aiwf/00_PROJECT_MANIFEST.md for the Project status

package/claude-code/aiwf/ko/.claude/commands/aiwf/aiwf_prime_context.md

@@ -0,0 +1,8 @@
+# 컨텍스트 윈도우 프라임
+
+실행:
+    git ls-files
+
+읽기:
+    README.md
+    ai_docs/claude_code_fresh_tutorials.md