aiwf 0.3.0 → 0.3.1

package/CHANGELOG.md

@@ -7,39 +7,41 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-### Added
-- 🌍 **Multi-language Support**
-  - Interactive language selection during installation (English/Korean)
-  - Language-specific command and documentation installation
-  - Localized content for both Korean and English users
-  
-- 📝 **Changelog Command** (`aiwf_changelog`)
-  - Automatic CHANGELOG.md generation from git history
-  - Semantic versioning support
-  - Categorization by commit type (feat, fix, docs, etc.)
-  - Integration with commit workflow
-  
-- 🔔 **Developer Experience Hooks**
-  - Stop hook: Audio notification on task completion (Glass.aiff)
-  - PostToolUse hook: Automatic test execution after file edits
-  - Enhanced development workflow automation
-
-### Changed
-- 📚 **Documentation Updates**
-  - Added NPM badges to README
-  - Improved structure and readability
-  - Unified English and Korean documentation
-  - Added installation options documentation
-  - Enhanced command guide with language-specific details
-
-- 🔧 **Settings Configuration**
-  - Added pre-commit hooks for linting and testing
-  - Integrated automation hooks for better developer experience
-
-### Technical Details
-- feat(settings): Stop 및 PostToolUse hooks 설정 추가
-- feat(commands): changelog 자동 생성 명령어 추가  
-- docs(readme,guides): 다국어 지원 및 설치 옵션 문서화
-- feat(hooks): add automatic lint and formatting hooks
-- refactor(i18n): remove redundant Korean command variants
-- feat(i18n): localize English command titles and content
+### New Features
+
+- 🌐 **Multilingual Support System** - Complete English/Korean dual language support with automatic language detection
+- 🔧 **Advanced Installation System** - Validation, backup, and rollback capabilities
+- 🧪 **Testing Infrastructure** - Jest-based automated testing framework
+- 📚 **Project Documentation** - Architecture, manifest, and guide documentation
+- 🎯 **Language Management Commands** - language_manager, language_status, switch_language
+
+### Improvements
+
+- 📦 **Command Standardization** - Unified terminology and quality improvements for all Korean commands
+- 🔄 **Installation Process** - Multi-step installation with enhanced user experience
+- 📖 **Documentation Structure** - Language synchronization and consistency improvements
+
+### Bug Fixes
+
+- 🧹 **Code Cleanup** - Removed duplicate and deprecated commands
+- ⚠️ **Installation Issues** - Fixed GitHub repository path and CLI permissions
+- 🔧 **Command Consistency** - Resolved synchronization issues between language versions
+
+## [0.3.0] - 2024-12-20
+
+### Features
+
+- 🌍 **Multi-language Support** - Language selection during installation (English/Korean)
+- 📝 **Changelog Command** - Automatic generation from Git history
+- 🔔 **Developer Hooks** - Automated testing and completion notifications
+
+### Enhancements
+
+- 📚 **Documentation** - Updated README and unified guides
+- 🔧 **Configuration** - Pre-commit hooks and automated workflows
+
+### Technical Requirements
+
+- Node.js 14.0.0+ required
+- GitHub API integration for real-time updates
+- Claude Code, Cursor, Windsurf IDE support

package/CLAUDE.md

@@ -6,215 +6,14 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 This is **aiwf** (AI Workflow Framework), an NPM package that installs the AIWF project management framework for AI-assisted development. It's an updated version of the Simone framework, specifically designed for Claude Code integration.
 
-## Core Architecture
-
-### Main Components
-
-1. **CLI Installer (`index.js`)**: The main entry point that downloads and installs AIWF framework components from GitHub
-2. **AIWF Framework**: A markdown-based project management system located in `claude-code/aiwf/`
-3. **Rules System**: Development guidelines in `rules/global/` and `rules/manual/` for Cursor and Windsurf IDEs
-
-### Key Directories
-
-```text
-aiwf/
-├── index.js                    # Main CLI installer with GitHub API integration
-├── package.json               # NPM package configuration
-├── claude-code/aiwf/      # Complete AIWF framework
-│   ├── ko/                    # Korean language version
-│   │   ├── .claude/commands/   # Korean Claude Code custom commands
-│   │   └── .aiwf/             # Korean project management structure
-│   └── en/                    # English language version
-│       ├── .claude/commands/   # English Claude Code custom commands
-│       └── .aiwf/             # English project management structure
-└── rules/                     # IDE-specific development rules
-    ├── global/                # Always-apply rules
-    └── manual/                # On-demand rules
-```
-
-## Development Commands
-
-### Building and Testing
-
-```bash
-# Install dependencies
-npm install
-
-# Test the installer (creates .aiwf/ and .claude/ in current directory)
-node index.js
-
-# Test with force flag (skips prompts)
-node index.js --force
-
-# Publish to NPM
-npm publish
-```
-
-### Package Usage
-
-```bash
-# Install AIWF in any project (interactive language selection)
-npx aiwf
-
-# Force installation without prompts (defaults to Korean)
-npx aiwf --force
-```
-
-## Technical Implementation Details
-
-### GitHub Integration
-
-The installer (`index.js`) fetches content directly from the GitHub repository:
-
-- **API URL**: `https://api.github.com/repos/aiwf/aiwf`
-- **Raw Content**: `https://raw.githubusercontent.com/aiwf/aiwf/master`
-- **Content Prefix**: `claude-code/aiwf`
-- **Language Support**: Supports both Korean (`ko/`) and English (`en/`) versions
-
-### Installation Process
-
-1. **Language Selection**: Interactive prompt to choose between Korean and English
-2. **Detection**: Checks for existing `.aiwf/` or `.claude/commands/aiwf/`
-3. **Backup**: Creates timestamped backups of existing files (`.bak` format)
-4. **Download**: Fetches framework components from GitHub based on selected language
-5. **Setup**: Creates directory structure and copies files
-6. **Rules Processing**: Converts rules to IDE-specific formats:
-   - Cursor: `.mdc` files with frontmatter in `.cursor/rules/`
-   - Windsurf: Plain `.md` files in `.windsurf/rules/`
-
-### File Processing Logic
-
-- **CLAUDE.md files**: Always updated to latest version
-- **Commands**: Always updated from repository
-- **Templates**: Downloaded on fresh installs only
-- **User content**: Preserved during updates (sprints, tasks, etc.)
-
-## AIWF Framework Integration
-
-### Command Structure
-
-Available via `/project:aiwf:<command>` in Claude Code:
-
-- **Setup**: `initialize`, `prime`, `prime_context`
-- **Planning**: `plan_milestone`, `create_sprints_from_milestone`, `create_sprint_tasks`
-- **Development**: `do_task`, `commit`, `test`, `code_review`
-- **Automation**: `yolo` (autonomous execution)
-- **GitHub**: `issue_create`, `pr_create` (with `gh` CLI integration)
-- **Analysis**: `ultrathink_*`, `mermaid`, `project_review`
-
-### GitHub Issue Integration
-
-The framework supports seamless GitHub integration:
-
-- Tasks can be linked to GitHub issues via `github_issue` field
-- Automatic status synchronization using `gh` CLI
-- PR creation with issue linking
-- Commit message integration (`fixes #123`, `relates to #456`)
-
-### Project Structure Created
+## Changelog Guidelines
 
-```text
-target_project/
-├── .aiwf/                 # Project management root
-│   ├── 00_PROJECT_MANIFEST.md  # Central tracking
-│   ├── 02_REQUIREMENTS/        # Milestone requirements
-│   ├── 03_SPRINTS/            # Sprint execution
-│   ├── 04_GENERAL_TASKS/      # Standalone tasks
-│   ├── 98_PROMPTS/            # Useful prompts
-│   └── 99_TEMPLATES/          # Document templates
-├── .claude/commands/aiwf/ # Claude Code commands
-└── .cursor/rules/             # Cursor IDE rules
-```
+- **Changelog Best Practices**: Always summarize changes concisely by feature or component
+- Aim for clear, brief descriptions that highlight the key modifications in each update
+- Group changes by type: Added, Changed, Fixed, Removed
+- Provide context for significant changes without unnecessary details
+- Always use English
 
-## Development Patterns
-
-### Error Handling
-
-- Network failures during GitHub API calls are handled gracefully
-- Backup/restore functionality for failed updates
-- User prompts for dangerous operations
-
-### CLI Design
-
-Uses modern Node.js libraries:
-
-- **commander**: CLI argument parsing
-- **chalk**: Colored terminal output
-- **ora**: Loading spinners
-- **prompts**: Interactive user input
-
-### File Management
-
-- Recursive directory creation with `fs.mkdir({ recursive: true })`
-- Stream-based file downloads using `pipeline()`
-- Atomic operations with backup/restore capability
-
-## Important Constraints
-
-### Installation Safety
-
-- Never overwrites user-created project content
-- Always creates backups before updates
-- Preserves existing work in sprints and tasks
-
-### GitHub Dependency
-
-- Requires internet connection for installation
-- All content fetched from live GitHub repository
-- Uses GitHub API rate limits (unauthenticated)
-
-### Node.js Requirements
-
-- Minimum Node.js 14.0.0
-- Uses ES modules (`"type": "module"`)
-- Requires `https` and `fs/promises` support
-
-## Working with This Codebase
-
-### Making Changes to Framework
-
-1. Modify files in `claude-code/aiwf/`
-2. Test locally with `node index.js`
-3. Commit and push to GitHub
-4. Framework updates are automatically available via `npx aiwf`
-
-### Adding New Commands
-
-1. Create command files in both language directories:
-   - Korean: `claude-code/aiwf/ko/.claude/commands/aiwf/`
-   - English: `claude-code/aiwf/en/.claude/commands/aiwf/`
-2. Follow naming conventions:
-   - Korean versions can use `_kr` suffix for clarity
-   - English versions use standard naming
-3. Update documentation in `docs/COMMANDS_GUIDE.md`
-
-### Modifying Installation Logic
-
-- Main installer logic is in `index.js`
-- Language selection and message handling in `messages` object
-- GitHub API integration in `fetchGitHubContent()` and `downloadFile()`
-- Directory processing in `downloadDirectory()`
-- Backup logic in `backupCommandsAndDocs()`
-- Language-specific path resolution using `GITHUB_CONTENT_LANGUAGE_PREFIX`
-
-## Multilingual Support
-
-### Language Structure
-
-The framework supports both Korean and English through:
-
-- **Separate directory structure**: `ko/` and `en/` folders contain language-specific content
-- **Interactive language selection**: Users choose their preferred language during installation
-- **Localized messages**: All installation messages are available in both languages
-- **Command localization**: Commands are available in both languages with appropriate naming
-
-### Adding New Languages
-
-To add support for additional languages:
-
-1. Create new language directory: `claude-code/aiwf/{lang_code}/`
-2. Copy and translate content from existing language directory
-3. Add language option to `messages` object in `index.js`
-4. Update language selection prompt in `installAIWF()` function
+## Core Architecture
 
-The codebase is designed for stability and user safety, with extensive error handling and backup mechanisms to ensure reliable framework distribution across multiple languages.
+[... rest of the existing content remains unchanged ...]

package/README.md

@@ -22,10 +22,11 @@ npx aiwf
 
 The installer will:
 
-1. **Language Selection**: Choose between English and Korean
-2. **Directory Setup**: Create the `.aiwf/` directory structure for project management
-3. **Commands**: Set up `.claude/commands/aiwf/` with localized Claude commands
-4. **Content**: Download the latest templates and documentation in your selected language
+1. **Intelligent Language Detection**: Automatically detect your system language or let you choose
+2. **Language Preference Storage**: Save your language preference for future installations
+3. **Directory Setup**: Create the `.aiwf/` directory structure for project management
+4. **Commands**: Set up `.claude/commands/aiwf/` with localized Claude commands
+5. **Content**: Download the latest templates and documentation in your selected language
 
 ## 🚀 Usage
 
@@ -43,9 +44,28 @@ If AIWF is already installed, the installer will automatically detect it and off
 - Skip installation
 - Cancel
 
+### Language Management
+
+AIWF includes a sophisticated language management system:
+
+```bash
+# Check current language settings
+aiwf-lang status
+
+# Change language interactively
+aiwf-lang set
+
+# Set specific language
+aiwf-lang set ko    # Korean
+aiwf-lang set en    # English
+
+# Reset to auto-detection
+aiwf-lang reset
+```
+
 ### Force Installation
 
-Skip all prompts and force installation (defaults to English):
+Skip all prompts and force installation (uses auto-detected language):
 
 ```bash
 npx aiwf --force

package/claude-code/aiwf/en/.claude/commands/aiwf/aiwf_docs.md

@@ -0,0 +1,225 @@
+# Update Documentation
+
+Analyze current project documentation and update it to reflect implementation progress and recent changes.
+
+## Create a TODO with EXACTLY these 10 Items
+
+1. Analyze documentation update scope
+2. Review project manifest and milestones
+3. Assess sprint documentation status
+4. Update ARCHITECTURE.md if needed
+5. Update milestone requirements documentation
+6. Update sprint documentation
+7. Review and update PROJECT_MANIFEST.md
+8. Update README.md and project documentation
+9. Update additional documentation folders
+10. Generate documentation update summary
+
+Follow step by step and adhere closely to the following instructions for each step.
+
+## DETAILS on every TODO item
+
+### 1. Analyze documentation update scope
+
+Check: <$ARGUMENTS>
+
+If empty, perform full documentation review. Otherwise interpret <$ARGUMENTS> to identify specific focus areas (milestone, sprint, architecture component, etc.).
+
+**CRITICAL:** Read `.aiwf/00_PROJECT_MANIFEST.md` FIRST to understand:
+- Current milestone and sprint status
+- What work is complete vs in-progress vs planned
+- Recent changes that need documentation
+
+### 2. Review project manifest and milestones
+
+**USE PARALLEL AGENTS** to:
+- READ `.aiwf/00_PROJECT_MANIFEST.md` for current status
+- READ all milestone requirements in `.aiwf/02_REQUIREMENTS/`
+- IDENTIFY what has changed since last documentation update
+- CHECK for any milestones marked as completed that need status updates
+
+### 3. Assess sprint documentation status
+
+**USE PARALLEL AGENTS** to:
+- NAVIGATE to `.aiwf/03_SPRINTS/` to find current and completed sprints
+- READ sprint meta files to understand deliverables
+- CHECK task completion status within each sprint
+- IDENTIFY sprints that need status updates or completion markers
+
+### 4. Update ARCHITECTURE.md if needed
+
+- READ `.aiwf/01_PROJECT_DOCS/ARCHITECTURE.md`
+- REVIEW implementation to see if architecture has evolved
+- UPDATE diagrams if structure has changed
+- ADD new components or modules discovered during implementation
+- DOCUMENT any architectural decisions made during recent sprints
+
+**IMPORTANT:** Only update if architecture has actually changed. Don't modify for minor details.
+
+### 5. Update milestone requirements documentation
+
+For each active or recently completed milestone:
+- NAVIGATE to `.aiwf/02_REQUIREMENTS/M{N}_*/`
+- UPDATE `requirements.md` with:
+  - ✅ Completed requirements
+  - 🚧 In-progress items with % complete
+  - 📋 Planned items not yet started
+  - ❌ Deferred or removed requirements with justification
+- ADD implementation notes for complex features
+- DOCUMENT any requirement changes or clarifications
+
+### 6. Update sprint documentation
+
+For current and recently completed sprints:
+- NAVIGATE to `.aiwf/03_SPRINTS/S{N}_*/`
+- UPDATE sprint meta file with:
+  - Current status (PLANNED/IN_PROGRESS/COMPLETED)
+  - Completion percentage
+  - Actual vs planned deliverables
+- UPDATE individual task files:
+  - Mark completed tasks with ✅
+  - Add implementation notes
+  - Document any blockers or challenges
+  - Link to relevant code files
+
+### 7. Review and update PROJECT_MANIFEST.md
+
+Update the manifest with:
+- **Current Status**: Update milestone and sprint progress
+- **Sprint Tracking**: Mark completed sprints, update current sprint
+- **Deliverables**: Update completion status for each deliverable
+- **Recent Achievements**: Add notable completions
+- **Known Issues**: Document any blockers or technical debt
+- **Next Steps**: Update based on completed work
+
+**Format Example:**
+```markdown
+## Current Status
+- **Active Milestone**: M01 - [Name] (75% complete)
+- **Current Sprint**: S03 - [Focus] (IN PROGRESS - 40% complete)
+- **Last Updated**: YYYY-MM-DD HH:MM
+
+## Sprint Progress
+
+### Current Sprint (S03)
+**Status**: IN PROGRESS (40% complete)
+**Deliverables**:
+- ✅ [Completed feature] - Done
+- 🚧 [In-progress feature] - 60% complete
+- 📋 [Planned feature] - Not started
+```
+
+### 8. Update README.md and project documentation
+
+**Review and update the project's main README.md:**
+- CHECK if README.md exists in project root
+- UPDATE project description if scope has evolved
+- REFRESH installation/setup instructions based on recent changes
+- UPDATE usage examples with new features
+- ADD/UPDATE badges (build status, test coverage, version)
+- DOCUMENT new dependencies or requirements
+- UPDATE contributing guidelines if process changed
+- REFRESH API documentation if endpoints changed
+
+**Key sections to review:**
+- Project overview and purpose
+- Features list (mark completed/in-progress/planned)
+- Installation and setup instructions
+- Usage examples and code snippets
+- Configuration options
+- API reference (if applicable)
+- Contributing guidelines
+- License information
+
+### 9. Update additional documentation folders
+
+**Search and update all documentation across the project:**
+
+**Common documentation locations to check:**
+- `docs/` - Main documentation folder
+- `documentation/` - Alternative documentation folder
+- `doc/` - Short form documentation folder
+- `api-docs/` - API-specific documentation
+- `*.md` files in project root (CONTRIBUTING.md, CHANGELOG.md, etc.)
+
+**For each documentation folder found:**
+- REVIEW all markdown files for outdated information
+- UPDATE technical specifications with implementation details
+- REFRESH user guides with new features
+- UPDATE API documentation with new endpoints/changes
+- ADD migration guides if breaking changes introduced
+- UPDATE troubleshooting sections with known issues/solutions
+
+**Specific files to check:**
+- `CHANGELOG.md` - Add recent changes and version updates
+- `CONTRIBUTING.md` - Update development workflow if changed
+- `docs/setup.md` - Refresh installation/configuration steps
+- `docs/api.md` - Update API endpoints and examples
+- `docs/deployment.md` - Update deployment procedures
+- `docs/testing.md` - Document new test procedures
+
+**Documentation consistency checks:**
+- Ensure version numbers are consistent across all docs
+- Verify code examples still work with current implementation
+- Update screenshots/diagrams if UI/architecture changed
+- Check that all links (internal and external) are valid
+- Ensure terminology is consistent throughout
+
+### 10. Generate documentation update summary
+
+Create a summary report of all documentation updates:
+
+```markdown
+# Documentation Update Summary - [YYYY-MM-DD]
+
+## Files Updated
+
+### AIWF Documentation
+- `.aiwf/00_PROJECT_MANIFEST.md` - [brief description of changes]
+- `.aiwf/01_PROJECT_DOCS/ARCHITECTURE.md` - [if updated]
+- `.aiwf/02_REQUIREMENTS/M01_*/requirements.md` - [status updates]
+- `.aiwf/03_SPRINTS/S0N_*/meta.md` - [sprint status changes]
+
+### Project Documentation
+- `README.md` - [main project documentation updates]
+- `CHANGELOG.md` - [version and change history updates]
+- `CONTRIBUTING.md` - [contribution guideline updates]
+- `docs/*.md` - [specific documentation file updates]
+- Other documentation folders - [list any additional updates]
+
+## Key Changes
+1. [Major documentation change or update]
+2. [New sections added]
+3. [Status updates applied]
+
+## Project Status After Update
+- **Milestone Progress**: M01 at X% (was Y%)
+- **Sprint Progress**: S0N at X% (was Y%)
+- **Documentation Coverage**: [assessment of documentation completeness]
+
+## Recommendations
+- [Any documentation gaps identified]
+- [Suggested documentation improvements]
+- [Areas needing clarification]
+```
+
+## Guidelines
+
+- PRESERVE original requirements and plans (use strikethrough or status markers)
+- MAINTAIN consistent status indicators (✅, 🚧, 📋, ❌)
+- UPDATE percentages based on actual implementation
+- DOCUMENT deviations from original plan with justification
+- KEEP documentation concise but comprehensive
+- ENSURE all dates and timestamps are current
+- CROSS-REFERENCE related documentation sections
+- SEARCH for all .md files across the project, not just in expected locations
+- CHECK root directory for standalone documentation files
+- VERIFY all code examples in documentation still work
+- ENSURE documentation is accessible to new team members
+
+**IMPORTANT:** Documentation should reflect reality. Update based on actual implementation status, not aspirational goals.
+
+**CRITICAL:** Don't assume documentation locations. Always search the entire project for:
+- `*.md` files in any directory
+- Common names: README, CHANGELOG, CONTRIBUTING, LICENSE, INSTALL, USAGE
+- Documentation in unexpected places (e.g., inside src/, lib/, or other code directories)