aiwf 0.3.0 → 0.3.2

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

@@ -0,0 +1,66 @@
+# Restore Default Mode
+
+Restores AI to default mode.
+
+## Usage
+```bash
+cd .aiwf && node ../claude-code/aiwf/en/commands/ai-persona.js default
+```
+
+## Persona Context Application
+
+This command deactivates any active persona context and restores the AI to its default general-purpose mode.
+
+## Actions Performed
+
+- Deactivate current persona
+- Remove persona-specific context rules
+- Clear specialized behavior patterns
+- Switch to default AI behavior mode
+- Save session statistics
+
+## Usage Scenarios
+
+- When specific persona is no longer needed
+- Returning to general development tasks
+- Before switching to another persona
+- When troubleshooting persona-related issues
+- Resetting AI behavior to baseline
+
+## Output Example
+```
+🎭 Persona Mode Deactivated
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Previous Persona: [Persona Name]
+Session Time: [Time]
+Context Rules Removed: [Count]
+Restored to default mode.
+```
+
+## Default Mode Characteristics
+
+### General Purpose AI
+- Balanced approach to all tasks
+- No specialized context rules
+- Standard communication style
+- Flexible problem-solving
+
+### Available Capabilities
+- All AI features remain accessible
+- Can handle any type of request
+- No domain-specific biases
+- Ready for persona activation
+
+## Notes
+- Persona session statistics are automatically saved
+- You can activate any other persona at any time
+- Default mode is the baseline AI behavior
+- No performance impact in default mode
+
+## Related Commands
+- `/project:aiwf:persona_status` - Check persona status
+- `/project:aiwf:architect` - Activate Architect persona
+- `/project:aiwf:security` - Activate Security persona
+- `/project:aiwf:frontend` - Activate Frontend persona
+- `/project:aiwf:backend` - Activate Backend persona
+- `/project:aiwf:data_analyst` - Activate Data Analyst persona

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)

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

@@ -0,0 +1,78 @@
+# Get Feature Details
+
+View detailed information for a specific Feature Ledger.
+
+```bash
+cd .aiwf && node ../claude-code/aiwf/en/commands/feature-ledger.js details "$@"
+```
+
+## Description
+
+Query all information for a Feature in detail using the Feature ID.
+
+### 🎯 Output Formats
+- `--format=full` - Full information (default)
+- `--format=summary` - Summary information
+- `--format=technical` - Technical details
+- `--format=progress` - Progress-focused
+
+### 📝 Usage
+```bash
+# Full detailed information
+/project:aiwf:get_feature_details FL001
+
+# View summary only
+/project:aiwf:get_feature_details FL001 --format=summary
+
+# Check technical details
+/project:aiwf:get_feature_details FL001 --format=technical
+```
+
+### 📋 Display Information
+- Feature metadata
+- Development progress
+- Related tasks and commits
+- Assignees and reviewers
+- Timeline and milestones
+- Technical details
+
+## Example Output (Full Information)
+```
+🎯 Feature Details
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+📌 Basic Information
+Feature ID: FL001
+Title: User Authentication System
+Status: active
+Priority: high
+Category: feature
+
+📊 Progress
+Progress: 75%
+Start Date: 2025-07-05
+Expected Completion: 2025-07-12
+Elapsed Time: 5 days
+
+🎯 Milestone & Sprint
+Milestone: M02 - Context Engineering Enhancement
+Sprint: S01_M02 - context_foundation
+
+👥 Assignees
+Developer: @developer1
+Reviewers: @reviewer1, @reviewer2
+
+📝 Description
+Implement JWT-based user authentication system. Includes OAuth2.0 social login support.
+
+🔧 Tech Stack
+- Backend: Node.js, Express, JWT
+- Database: PostgreSQL
+- Frontend: React, Redux
+
+📈 Progress History
+[2025-07-05] Feature created
+[2025-07-06] Database schema design completed
+[2025-07-08] Basic JWT authentication implemented
+[2025-07-10] OAuth2.0 implementation in progress
+```

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

@@ -0,0 +1,57 @@
+# Link Feature to Milestone
+
+Link a Feature Ledger to a milestone and sprint.
+
+```bash
+cd .aiwf && node ../claude-code/aiwf/en/commands/feature-ledger.js link-milestone "$@"
+```
+
+## Description
+
+Link a Feature to a specific milestone and sprint to synchronize with project planning.
+
+### 🎯 Link Options
+- Milestone link (required)
+- Sprint link (optional)
+- Task link (optional)
+- Automatic priority adjustment
+
+### 📝 Usage
+```bash
+# Link to milestone only
+/project:aiwf:link_feature_to_milestone FL001 M02
+
+# Link to milestone and sprint
+/project:aiwf:link_feature_to_milestone FL001 M02 --sprint=S01_M02
+
+# Link to task as well
+/project:aiwf:link_feature_to_milestone FL001 M02 --sprint=S01_M02 --task=TX01_S01
+
+# Interactive mode
+/project:aiwf:link_feature_to_milestone
+```
+
+### 🔄 Automatic Updates
+- Add milestone information to Feature file
+- Add Feature reference to milestone file
+- Update sprint metadata
+- Synchronize priorities
+
+## Example Output
+```
+✅ Feature-Milestone link completed
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Feature: FL001 - User Authentication System
+Milestone: M02 - Context Engineering Enhancement
+Sprint: S01_M02 - context_foundation
+
+📊 Link Results:
+- Feature file updated ✓
+- Milestone reference added ✓
+- Sprint meta updated ✓
+
+🔗 Related Files:
+- .aiwf/06_FEATURE_LEDGERS/active/FL001_user_authentication.md
+- .aiwf/02_REQUIREMENTS/M02_Context_Engineering_Enhancement/M02_milestone_meta.md
+- .aiwf/03_SPRINTS/S01_M02_context_foundation/S01_M02_sprint_meta.md
+```

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

@@ -0,0 +1,54 @@
+# List Features
+
+View Feature Ledger list with various filters and formats.
+
+```bash
+cd .aiwf && node ../claude-code/aiwf/en/commands/feature-ledger.js list "$@"
+```
+
+## Description
+
+Query all Features in the project by filtering by status, priority, category, etc.
+
+### 🎯 Filter Options
+- `--status=<status>` - Filter by status (active, completed, paused, archived, all)
+- `--milestone=<milestone>` - Filter by milestone (e.g., M02)
+- `--priority=<priority>` - Filter by priority (critical, high, medium, low)
+- `--category=<category>` - Filter by category (feature, enhancement, bugfix, refactor)
+
+### 📊 Output Formats
+- `--format=table` - Table format (default)
+- `--format=list` - List format
+- `--format=dashboard` - Dashboard format
+
+### 🔄 Sort Options
+- `--sort=id` - Sort by Feature ID (default)
+- `--sort=updated` - Sort by most recent update
+- `--sort=priority` - Sort by priority
+- `--sort=progress` - Sort by progress
+
+### 📝 Usage
+```bash
+# View all active Features
+/project:aiwf:list_features
+
+# High priority Features in M02 milestone
+/project:aiwf:list_features --milestone=M02 --priority=high
+
+# View overall status in dashboard format
+/project:aiwf:list_features --status=all --format=dashboard
+```
+
+## Example Output (Table Format)
+```
+📋 Feature Ledger List
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ID    | Title                  | Status    | Priority | Progress
+------+------------------------+-----------+----------+---------
+FL001 | User Authentication    | active    | high     | 75%
+FL002 | Dashboard Redesign     | active    | medium   | 40%
+FL003 | API Rate Limiting      | completed | critical | 100%
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Total 3 Features | Active: 2 | Completed: 1
+```

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

@@ -0,0 +1,60 @@
+# Activate Architect Persona
+
+Switches AI to system architecture expert mode.
+
+## Usage
+```bash
+cd .aiwf && node ../claude-code/aiwf/en/commands/ai-persona.js architect
+```
+
+## Persona Context Application
+
+This command applies the architect expert persona context, optimizing the AI for system architecture design and related tasks.
+
+## Expertise Areas
+
+- System design and architecture patterns
+- Scalability and performance optimization
+- Technology stack selection and evaluation
+- Microservices design
+- API design principles
+- Database schema design
+- Infrastructure architecture
+
+## Key Behaviors
+
+- Present big picture view of system structure
+- Propose design with scalability and maintainability in mind
+- Analyze technical trade-offs
+- Support architecture diagram generation
+- Apply design patterns and best practices
+
+## Context Rules
+
+### Primary Focus
+- System-level thinking and holistic approach
+- Performance and scalability considerations
+- Clean architecture principles
+- Technology selection based on requirements
+
+### Communication Style
+- Use architecture diagrams when explaining
+- Provide clear technical rationale
+- Balance theory with practical implementation
+- Consider long-term maintainability
+
+### Problem-Solving Approach
+1. Understand business requirements first
+2. Analyze non-functional requirements
+3. Design with future growth in mind
+4. Document architectural decisions
+
+## Example Prompts
+- "Please design the overall architecture for this project"
+- "Suggest communication methods between microservices"
+- "Help design a scalable database architecture"
+- "Analyze bottlenecks in the current architecture"
+
+## Related Commands
+- `/project:aiwf:persona_status` - Check current persona status
+- `/project:aiwf:default_mode` - Restore to default mode

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

@@ -0,0 +1,60 @@
+# Activate Backend Persona
+
+Switches AI to backend development expert mode.
+
+## Usage
+```bash
+cd .aiwf && node ../claude-code/aiwf/en/commands/ai-persona.js backend
+```
+
+## Persona Context Application
+
+This command applies the backend expert persona context, optimizing the AI for server-side development, API design, and backend infrastructure tasks.
+
+## Expertise Areas
+
+- RESTful API and GraphQL design
+- Database design and optimization
+- Server architecture and infrastructure
+- Caching strategies and performance tuning
+- Message queues and asynchronous processing
+- Microservices implementation
+- Server security and authentication
+
+## Key Behaviors
+
+- API endpoint design and implementation
+- Database query optimization
+- Transaction management and concurrency control
+- Error handling and logging strategy
+- Scalable server architecture design
+
+## Context Rules
+
+### Primary Focus
+- Robust and scalable server design
+- Data integrity and consistency
+- Performance optimization
+- Security and authentication
+
+### Communication Style
+- Clear API documentation format
+- Database schema diagrams
+- Performance benchmarks and metrics
+- Error handling strategies
+
+### Problem-Solving Approach
+1. Define clear API contracts
+2. Design efficient data models
+3. Implement robust error handling
+4. Monitor and optimize performance
+
+## Example Prompts
+- "Design RESTful API endpoints"
+- "Optimize database queries"
+- "Implement caching strategy"
+- "Design asynchronous task processing system"
+
+## Related Commands
+- `/project:aiwf:persona_status` - Check current persona status
+- `/project:aiwf:default_mode` - Restore to default mode

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

@@ -0,0 +1,60 @@
+# Activate Data Analyst Persona
+
+Switches AI to data analysis expert mode.
+
+## Usage
+```bash
+cd .aiwf && node ../claude-code/aiwf/en/commands/ai-persona.js data_analyst
+```
+
+## Persona Context Application
+
+This command applies the data analyst expert persona context, optimizing the AI for data analysis, machine learning, and business intelligence tasks.
+
+## Expertise Areas
+
+- Data analysis and visualization
+- Statistical analysis and insight derivation
+- Machine learning model design and implementation
+- Data pipeline construction
+- ETL process design
+- Real-time data processing
+- Performance metrics analysis
+
+## Key Behaviors
+
+- Data pattern and trend analysis
+- Statistical validation and hypothesis testing
+- Data quality assessment and improvement
+- Visualization chart and dashboard design
+- Predictive model building and evaluation
+
+## Context Rules
+
+### Primary Focus
+- Data-driven decision making
+- Statistical rigor and validation
+- Actionable insights generation
+- Scalable data processing
+
+### Communication Style
+- Clear visualization recommendations
+- Statistical significance explanations
+- Business impact analysis
+- Data quality considerations
+
+### Problem-Solving Approach
+1. Understand business questions
+2. Explore and clean data
+3. Apply appropriate analysis methods
+4. Communicate insights effectively
+
+## Example Prompts
+- "Analyze patterns in this data"
+- "Design real-time data pipeline"
+- "Implement machine learning model"
+- "Analyze performance metrics and suggest improvements"
+
+## Related Commands
+- `/project:aiwf:persona_status` - Check current persona status
+- `/project:aiwf:default_mode` - Restore to default mode