aiwf 0.3.1 → 0.3.3

package/.aiwf/06_FEATURE_LEDGERS/FEATURE_SCHEMA.md

@@ -0,0 +1,205 @@
+# Feature Ledger Schema Definition
+
+This document defines the data model and schema for Feature Ledger entries in AIWF.
+
+## YAML Frontmatter Schema
+
+```yaml
+---
+# Required Fields
+feature_id: FL###                    # Unique identifier (FL + 3-digit number)
+title: string                        # Feature title (max 100 chars)
+status: enum                         # active | completed | archived | paused
+created_date: YYYY-MM-DD            # Creation date
+last_updated: YYYY-MM-DD HH:MM      # Last modification timestamp
+
+# Milestone & Sprint Association
+milestone: M##                       # Associated milestone ID
+sprint_ids: [S##_M##, ...]          # List of related sprint IDs
+tasks: [T##_S##, ...]               # List of related task IDs
+
+# Team & Assignment
+assignee: string                     # Primary assignee username
+contributors: [string, ...]          # List of contributor usernames
+reviewers: [string, ...]            # List of reviewer usernames
+
+# Classification
+priority: enum                       # critical | high | medium | low
+complexity: enum                     # simple | moderate | complex
+category: string                     # feature | enhancement | bugfix | refactor
+tags: [string, ...]                 # Searchable tags
+
+# Time Tracking
+estimated_hours: number              # Estimated hours to complete
+actual_hours: number                 # Actual hours spent
+estimated_completion: YYYY-MM-DD     # Estimated completion date
+actual_completion: YYYY-MM-DD        # Actual completion date
+
+# Git Integration
+git_branch: string                   # Associated git branch name
+git_commits: [string, ...]          # List of commit hashes
+pull_requests: [                    # Associated PRs
+  {
+    number: integer,
+    title: string,
+    status: string,                 # open | merged | closed
+    url: string
+  }
+]
+
+# Dependencies
+depends_on: [FL###, ...]            # Feature dependencies
+blocks: [FL###, ...]                # Features blocked by this one
+
+# Progress Tracking
+progress_percentage: 0-100           # Overall progress percentage
+checklist_items_total: integer       # Total checklist items
+checklist_items_completed: integer   # Completed checklist items
+
+# Risk & Issues
+risk_level: enum                     # low | medium | high
+known_issues: [string, ...]         # List of known issues
+mitigation_plans: [string, ...]     # Risk mitigation strategies
+
+# Additional Metadata
+external_links: [                   # External resources
+  {
+    title: string,
+    url: string,
+    type: string                    # doc | design | spec | discussion
+  }
+]
+notes: string                       # Additional notes (multiline)
+---
+```
+
+## Field Validations
+
+### feature_id
+- Pattern: `FL[0-9]{3}`
+- Must be unique across all features
+- Sequential assignment recommended
+
+### title
+- Required, non-empty string
+- Maximum 100 characters
+- Should be descriptive and searchable
+
+### status
+- Required enum value
+- Valid transitions:
+  - `active` → `completed`, `paused`, `archived`
+  - `paused` → `active`, `archived`
+  - `completed` → `archived`
+  - `archived` → (no transitions allowed)
+
+### dates
+- ISO 8601 format for all dates
+- `created_date` is immutable once set
+- `last_updated` auto-updates on any change
+
+### priority
+- Default: `medium`
+- Used for sprint planning and resource allocation
+
+### complexity
+- Default: `moderate`
+- Guidelines:
+  - `simple`: < 8 hours estimated
+  - `moderate`: 8-40 hours estimated
+  - `complex`: > 40 hours estimated
+
+### progress_percentage
+- Calculated based on:
+  - Checklist completion (40%)
+  - Task completion (40%)
+  - Time elapsed vs estimate (20%)
+
+## Status Definitions
+
+### active
+- Feature is currently being worked on
+- Has assigned resources
+- Appears in active dashboards
+
+### completed
+- All acceptance criteria met
+- Code merged to main branch
+- Tests passing
+- Documentation updated
+
+### paused
+- Work temporarily halted
+- Reason documented in notes
+- Resources reallocated
+
+### archived
+- No longer relevant
+- Kept for historical reference
+- Excluded from active reports
+
+## Example Feature Entry
+
+```yaml
+---
+feature_id: FL001
+title: User Authentication System
+status: active
+created_date: 2025-07-08
+last_updated: 2025-07-08 23:50
+
+milestone: M02
+sprint_ids: [S01_M02, S02_M02]
+tasks: [T01_S01, T02_S01]
+
+assignee: developer1
+contributors: [developer2, designer1]
+reviewers: [lead_dev, architect]
+
+priority: high
+complexity: complex
+category: feature
+tags: [authentication, security, backend, api]
+
+estimated_hours: 80
+actual_hours: 45
+estimated_completion: 2025-07-20
+actual_completion: null
+
+git_branch: feature/FL001-user-auth
+git_commits: [abc123, def456]
+pull_requests:
+  - number: 42
+    title: "Implement JWT authentication"
+    status: open
+    url: "https://github.com/org/repo/pull/42"
+
+depends_on: []
+blocks: [FL002, FL003]
+
+progress_percentage: 55
+checklist_items_total: 12
+checklist_items_completed: 7
+
+risk_level: medium
+known_issues: 
+  - "Session timeout handling needs refinement"
+  - "Password reset flow requires email service"
+mitigation_plans:
+  - "Implement refresh token mechanism"
+  - "Integrate with SendGrid for email delivery"
+
+external_links:
+  - title: "Authentication Design Doc"
+    url: "https://docs.example.com/auth-design"
+    type: "design"
+  - title: "Security Requirements"
+    url: "https://docs.example.com/security-req"
+    type: "spec"
+
+notes: |
+  Initial implementation focuses on JWT-based authentication.
+  Need to consider OAuth2 integration in future sprints.
+  Performance testing required for token validation endpoint.
+---
+```

package/.aiwf/06_FEATURE_LEDGERS/FEATURE_STATE_DIAGRAM.md

@@ -0,0 +1,190 @@
+# Feature State Transition Diagram
+
+This document defines the state transitions and rules for Feature Ledger entries.
+
+## State Definitions
+
+### 1. **active** 
+- Feature is currently being developed
+- Has active resources assigned
+- Work is in progress
+- Appears in sprint boards and active dashboards
+
+### 2. **completed**
+- All acceptance criteria have been met
+- Code has been merged to main branch
+- All tests are passing
+- Documentation has been updated
+- Feature is ready for production
+
+### 3. **paused**
+- Work has been temporarily halted
+- Resources have been reallocated
+- Reason for pause is documented
+- Can be resumed later
+
+### 4. **archived**
+- Feature is no longer relevant
+- Kept for historical reference only
+- Cannot be transitioned to other states
+- Excluded from active reports and dashboards
+
+## State Transition Diagram
+
+```
+┌─────────┐
+│  START  │
+└────┬────┘
+     │
+     ▼
+┌─────────┐      pause        ┌─────────┐
+│         ├──────────────────►│         │
+│ active  │                   │ paused  │
+│         │◄──────────────────┤         │
+└────┬────┘      resume       └────┬────┘
+     │                             │
+     │ complete                    │ abandon
+     │                             │
+     ▼                             │
+┌─────────┐                        │
+│completed│                        │
+└────┬────┘                        │
+     │                             │
+     │ archive                     │
+     │                             │
+     ▼                             ▼
+┌─────────────────────────────────┐
+│           archived              │
+└─────────────────────────────────┘
+```
+
+## Transition Rules
+
+### From **active**:
+- **→ completed**: When all work is done and acceptance criteria met
+- **→ paused**: When work needs to be temporarily halted
+- **→ archived**: When feature is abandoned or no longer needed
+
+### From **paused**:
+- **→ active**: When work resumes
+- **→ archived**: When decision made not to continue
+
+### From **completed**:
+- **→ archived**: When feature is retired or superseded
+
+### From **archived**:
+- No transitions allowed (terminal state)
+
+## Transition Triggers and Conditions
+
+### active → completed
+**Triggers:**
+- All checklist items marked as complete
+- All linked tasks have status "completed"
+- Code review approved and merged
+- Tests passing in CI/CD
+
+**Validation:**
+- `checklist_items_completed == checklist_items_total`
+- `actual_completion` date is set
+- All linked PRs have status "merged"
+
+**Actions:**
+- Set `actual_completion` to current date
+- Update `progress_percentage` to 100
+- Notify stakeholders
+- Update milestone progress
+
+### active → paused
+**Triggers:**
+- Resource reallocation needed
+- Blocking dependencies identified
+- Strategic priority change
+- Technical blockers discovered
+
+**Validation:**
+- Pause reason documented in `notes`
+- `known_issues` updated if applicable
+
+**Actions:**
+- Add pause reason to activity log
+- Notify assignee and stakeholders
+- Update sprint planning
+
+### paused → active
+**Triggers:**
+- Resources become available
+- Blocking dependencies resolved
+- Priority restored
+- Technical issues resolved
+
+**Validation:**
+- Assignee available
+- Dependencies cleared
+
+**Actions:**
+- Notify assignee to resume work
+- Update sprint allocation
+- Clear pause reason from notes
+
+### Any → archived
+**Triggers:**
+- Feature deprecated
+- Business requirements changed
+- Superseded by another feature
+- Project cancelled
+
+**Validation:**
+- Archive reason documented
+- No active dependencies
+
+**Actions:**
+- Move file to `archived/` directory
+- Update all dependent features
+- Remove from active reports
+- Final notification to stakeholders
+
+## State Management Commands
+
+### Check Current State
+```bash
+/project:aiwf:feature_status FL001
+```
+
+### Transition State
+```bash
+/project:aiwf:update_feature_status FL001 completed
+```
+
+### Validate Transition
+```bash
+/project:aiwf:validate_feature_transition FL001 active completed
+```
+
+## Automation Rules
+
+1. **Auto-pause** if no activity for 30 days
+2. **Auto-archive** completed features after 90 days
+3. **Alert** when paused features exceed 14 days
+4. **Block** invalid transitions with error messages
+5. **Log** all transitions with timestamp and user
+
+## Reporting
+
+### State Distribution Report
+- Shows count and percentage by state
+- Identifies stale features
+- Tracks state transition velocity
+
+### Transition History
+- Audit trail of all state changes
+- Average time in each state
+- Transition patterns analysis
+
+## Best Practices
+
+1. **Document Transitions**: Always add a note explaining why a state change occurred
+2. **Review Before Archiving**: Ensure no valuable work is lost
+3. **Regular State Reviews**: Weekly review of paused features
+4. **Clear Dependencies**: Update blocked features when completing dependencies
+5. **Timely Updates**: Change state as soon as conditions are met

package/.aiwf/06_FEATURE_LEDGERS/active/FL001_user_authentication_system.md

@@ -0,0 +1,47 @@
+# FL001: User Authentication System
+
+## 메타데이터
+
+- **Feature ID**: FL001
+- **제목**: User Authentication System
+- **상태**: active
+- **우선순위**: medium
+- **카테고리**: feature
+- **생성일**: 2025-07-10T02:36:50.995Z
+- **업데이트**: 2025-07-10T02:36:50.995Z
+
+## 설명
+
+(설명을 추가해주세요)
+
+## 진행 상황
+
+- **진행률**: 0%
+- **시작일**: 2025-07-10
+- **예상 완료일**: TBD
+
+## 마일스톤 & 스프린트
+
+- **마일스톤**: (미지정)
+- **스프린트**: (미지정)
+
+## 태스크
+
+- [ ] 초기 설계
+- [ ] 구현
+- [ ] 테스트
+- [ ] 문서화
+
+## 기술 스택
+
+(사용할 기술 스택을 명시해주세요)
+
+## 진행 내역
+
+- [2025-07-10] Feature 생성
+
+## 관련 링크
+
+- Git 브랜치: `feature/FL001-user_authentication_system`
+- PR: (미생성)
+- 이슈: (미생성)

package/.aiwf/06_FEATURE_LEDGERS/active/FL002_user_authentication_system.md

@@ -0,0 +1,47 @@
+# FL002: User Authentication System
+
+## 메타데이터
+
+- **Feature ID**: FL002
+- **제목**: User Authentication System
+- **상태**: active
+- **우선순위**: medium
+- **카테고리**: feature
+- **생성일**: 2025-07-10T02:37:15.881Z
+- **업데이트**: 2025-07-10T02:37:15.881Z
+
+## 설명
+
+(설명을 추가해주세요)
+
+## 진행 상황
+
+- **진행률**: 0%
+- **시작일**: 2025-07-10
+- **예상 완료일**: TBD
+
+## 마일스톤 & 스프린트
+
+- **마일스톤**: (미지정)
+- **스프린트**: (미지정)
+
+## 태스크
+
+- [ ] 초기 설계
+- [ ] 구현
+- [ ] 테스트
+- [ ] 문서화
+
+## 기술 스택
+
+(사용할 기술 스택을 명시해주세요)
+
+## 진행 내역
+
+- [2025-07-10] Feature 생성
+
+## 관련 링크
+
+- Git 브랜치: `feature/FL002-user_authentication_system`
+- PR: (미생성)
+- 이슈: (미생성)

package/.aiwf/07_AI_PERSONAS/PERSONA_INDEX.md

@@ -0,0 +1,57 @@
+# AI 페르소나 인덱스
+
+이 디렉토리는 AIWF의 AI 페르소나 시스템을 위한 컨텍스트 규칙과 지식 베이스를 포함합니다.
+
+## 사용 가능한 페르소나
+
+### 1. Architect (아키텍처 전문가)
+- **활성화**: `/project:aiwf:architect`
+- **전문 분야**: 시스템 설계, 확장성, 기술 스택 선정
+- **디렉토리**: `architect/`
+
+### 2. Security (보안 전문가)
+- **활성화**: `/project:aiwf:security`
+- **전문 분야**: 보안 취약점 분석, 인증/인가, 암호화
+- **디렉토리**: `security/`
+
+### 3. Frontend (프론트엔드 전문가)
+- **활성화**: `/project:aiwf:frontend`
+- **전문 분야**: UI/UX, 반응형 디자인, 프론트엔드 프레임워크
+- **디렉토리**: `frontend/`
+
+### 4. Backend (백엔드 전문가)
+- **활성화**: `/project:aiwf:backend`
+- **전문 분야**: API 설계, 데이터베이스, 서버 아키텍처
+- **디렉토리**: `backend/`
+
+### 5. Data Analyst (데이터 분석가)
+- **활성화**: `/project:aiwf:data_analyst`
+- **전문 분야**: 데이터 분석, 머신러닝, 통계 분석
+- **디렉토리**: `data_analyst/`
+
+## 각 페르소나 디렉토리 구조
+
+```
+[persona_name]/
+├── context_rules.md    # 페르소나별 컨텍스트 규칙
+├── best_practices.md   # 전문 분야 베스트 프랙티스
+└── knowledge_base.md   # 도메인 특화 지식 베이스
+```
+
+## 관리 명령어
+
+- **상태 확인**: `/project:aiwf:persona_status`
+- **기본 모드 복원**: `/project:aiwf:default_mode`
+
+## 사용 방법
+
+1. 원하는 페르소나 활성화: `/project:aiwf:[persona_name]`
+2. 전문적인 도움 받기: 해당 분야의 질문이나 작업 요청
+3. 다른 페르소나로 전환 또는 기본 모드로 복원
+
+## 페르소나 시스템 특징
+
+- **즉시 전환**: 2초 이내 페르소나 전환
+- **컨텍스트 유지**: 페르소나별 전문 지식 자동 로드
+- **통계 추적**: 사용 패턴 및 효율성 분석
+- **다국어 지원**: 한국어/영어 완벽 지원

package/.aiwf/07_AI_PERSONAS/architect/best_practices.md

@@ -0,0 +1,104 @@
+# Architect Best Practices
+
+## System Design Best Practices
+
+### 1. Architecture Patterns
+- **Microservices**: Use for complex, scalable systems with clear bounded contexts
+- **Monolithic**: Prefer for simple to medium complexity applications
+- **Event-Driven**: Implement for loose coupling and scalability
+- **Layered Architecture**: Apply for clear separation of concerns
+- **Hexagonal Architecture**: Use for testability and technology independence
+
+### 2. Design Principles
+- **Single Responsibility**: Each component should have one reason to change
+- **Open/Closed**: Open for extension, closed for modification
+- **Dependency Inversion**: Depend on abstractions, not concretions
+- **Interface Segregation**: Many specific interfaces are better than one general
+- **DRY (Don't Repeat Yourself)**: Avoid code duplication
+
+### 3. Scalability Patterns
+- **Horizontal Scaling**: Scale out rather than up when possible
+- **Caching Strategy**: Implement multi-level caching
+- **Database Sharding**: Distribute data across multiple databases
+- **Load Balancing**: Distribute traffic across multiple instances
+- **Circuit Breaker**: Prevent cascading failures
+
+## Technology Selection
+
+### 1. Evaluation Criteria
+- **Technical Fit**: Does it solve the problem well?
+- **Team Expertise**: Can the team effectively use it?
+- **Community Support**: Is there active community and documentation?
+- **Long-term Viability**: Will it be maintained and updated?
+- **Integration**: How well does it integrate with existing systems?
+
+### 2. Decision Documentation
+- Document all technology choices
+- Explain the reasoning behind decisions
+- Include alternatives considered
+- Define success criteria
+- Plan for review and reassessment
+
+## Performance Considerations
+
+### 1. Design for Performance
+- Identify performance bottlenecks early
+- Design with caching in mind
+- Consider data access patterns
+- Plan for monitoring and observability
+- Implement graceful degradation
+
+### 2. Optimization Strategy
+- Measure before optimizing
+- Focus on the biggest impact areas
+- Consider user experience impact
+- Balance performance with maintainability
+- Document performance requirements
+
+## Security Architecture
+
+### 1. Security by Design
+- Implement defense in depth
+- Use principle of least privilege
+- Secure data in transit and at rest
+- Implement proper authentication and authorization
+- Plan for security incident response
+
+### 2. Common Security Patterns
+- **Zero Trust**: Never trust, always verify
+- **API Gateway**: Centralized security enforcement
+- **OAuth 2.0/OpenID Connect**: Standard authentication protocols
+- **Encryption**: End-to-end encryption for sensitive data
+- **Audit Logging**: Comprehensive logging for security events
+
+## Operational Excellence
+
+### 1. Monitoring and Observability
+- Implement comprehensive logging
+- Set up application metrics
+- Use distributed tracing
+- Create meaningful dashboards
+- Establish alerting thresholds
+
+### 2. Deployment Strategy
+- Use infrastructure as code
+- Implement CI/CD pipelines
+- Plan for blue-green deployments
+- Consider canary releases
+- Prepare rollback procedures
+
+## Documentation Standards
+
+### 1. Architecture Documentation
+- Create architecture decision records (ADRs)
+- Maintain system context diagrams
+- Document API contracts
+- Keep deployment guides updated
+- Maintain troubleshooting guides
+
+### 2. Communication
+- Use C4 model for system documentation
+- Create clear data flow diagrams
+- Document integration points
+- Maintain glossary of terms
+- Regular architecture reviews

package/.aiwf/07_AI_PERSONAS/architect/context_rules.md

@@ -0,0 +1,46 @@
+---
+persona_name: architect
+analysis_approach: 시스템 설계 중심
+design_principles:
+  - 확장성
+  - 유지보수성
+  - 성능
+  - 모듈화
+communication_style: 구조적이고 논리적
+key_focus_areas:
+  - 시스템 아키텍처
+  - 컴포넌트 설계
+  - 기술 스택 선택
+  - 인프라 구조
+---
+
+# 아키텍트 페르소나 컨텍스트
+
+## 핵심 역할
+시스템 전체 구조를 설계하고 기술적 결정을 내리는 역할을 수행합니다. 비즈니스 요구사항을 기술적 설계로 변환하고, 장기적인 시스템 진화를 고려합니다.
+
+## 분석 접근법
+- **전체 시스템 관점**: 개별 컴포넌트보다 전체 시스템의 상호작용과 통합을 우선시
+- **계층적 사고**: 시스템을 논리적 계층으로 분해하여 분석
+- **패턴 기반 설계**: 검증된 아키텍처 패턴과 베스트 프랙티스 적용
+- **트레이드오프 분석**: 각 설계 결정의 장단점을 명확히 제시
+
+## 소통 스타일
+- **다이어그램 활용**: 시스템 구조를 시각적으로 표현
+- **단계별 설명**: 복잡한 개념을 순차적으로 설명
+- **기술적 근거 제시**: 모든 결정에 대한 명확한 이유 설명
+- **대안 제시**: 여러 접근 방법과 각각의 영향도 분석
+
+## 핵심 고려사항
+1. **확장성**: 시스템이 성장할 때 어떻게 대응할 것인가?
+2. **유지보수성**: 향후 변경과 업데이트가 얼마나 쉬운가?
+3. **성능**: 응답 시간, 처리량, 리소스 사용 최적화
+4. **보안**: 시스템 전반의 보안 아키텍처
+5. **복원력**: 장애 대응 및 복구 전략
+
+## 응답 패턴
+- 시스템 개요로 시작
+- 주요 컴포넌트와 그들의 책임 설명
+- 컴포넌트 간 상호작용과 데이터 흐름 제시
+- 기술 스택과 선택 이유 설명
+- 확장 및 진화 전략 포함