aiwf 0.3.7 → 0.3.12

package/.aiwf/06_FEATURE_LEDGERS/FEATURE_INTEGRATION_GUIDE.md

@@ -1,227 +0,0 @@
-# Feature Integration Guide
-
-This document describes how Features integrate with Milestones, Sprints, and Tasks in AIWF.
-
-## Integration Architecture
-
-```
-Milestone (M##)
-    └── Features (FL###)
-         └── Sprints (S##_M##)
-              └── Tasks (T##_S##)
-```
-
-## Milestone Integration
-
-### Linking Features to Milestones
-
-Each feature is associated with exactly one milestone through the `milestone` field in the YAML frontmatter.
-
-```yaml
-milestone: M02  # Required field
-```
-
-### Milestone Progress Calculation
-
-Milestone progress is calculated based on:
-- Number of completed features vs total features
-- Weighted by feature complexity
-- Formula: `Σ(completed_features * complexity_weight) / Σ(all_features * complexity_weight)`
-
-### Complexity Weights
-- `simple`: 1.0
-- `moderate`: 2.0
-- `complex`: 3.0
-
-## Sprint Integration
-
-### Multi-Sprint Features
-
-Features often span multiple sprints. The `sprint_ids` array tracks all related sprints:
-
-```yaml
-sprint_ids: [S01_M02, S02_M02, S03_M02]
-```
-
-### Sprint Assignment Rules
-
-1. Features are assigned to sprints during sprint planning
-2. A feature can be active in multiple sprints
-3. Sprint progress includes partial feature completion
-
-### Sprint Progress Tracking
-
-For features spanning multiple sprints:
-- Track `progress_percentage` at feature level
-- Calculate sprint-specific progress based on completed tasks
-- Update feature progress after each sprint
-
-## Task Integration
-
-### Linking Tasks to Features
-
-Tasks reference their parent feature:
-
-```yaml
-# In task file
-feature_id: FL001
-```
-
-Features track their child tasks:
-
-```yaml
-# In feature file
-tasks: [T01_S01, T02_S01, T05_S02]
-```
-
-### Task Completion Impact
-
-When a task is completed:
-1. Update feature's task list
-2. Recalculate feature progress
-3. Update sprint progress
-4. Trigger milestone progress update
-
-### Progress Calculation
-
-Feature progress based on tasks:
-```
-progress = (completed_tasks / total_tasks) * 100
-```
-
-## Bidirectional Sync Mechanisms
-
-### 1. Feature Creation
-```
-Create Feature → Update Milestone → Link to Current Sprint
-```
-
-### 2. Task Creation
-```
-Create Task → Link to Feature → Update Feature Task List
-```
-
-### 3. Sprint Planning
-```
-Assign Features to Sprint → Update Feature sprint_ids → Update Sprint Scope
-```
-
-### 4. Status Updates
-```
-Complete Task → Update Feature Progress → Update Sprint Progress → Update Milestone Progress
-```
-
-## Command Integration
-
-### Create Feature with Milestone
-```bash
-/project:aiwf:create_feature_ledger "User Authentication" --milestone M02
-```
-
-### Link Feature to Sprint
-```bash
-/project:aiwf:link_feature_sprint FL001 S02_M02
-```
-
-### Update Feature from Task Completion
-```bash
-/project:aiwf:complete_task T01_S01
-# Automatically updates FL001 progress
-```
-
-## Data Consistency Rules
-
-### 1. Referential Integrity
-- Milestone must exist before feature assignment
-- Sprint must belong to the same milestone
-- Tasks must belong to linked sprints
-
-### 2. Status Consistency
-- Feature cannot be "completed" if tasks are incomplete
-- Milestone cannot be "completed" if features are incomplete
-- Archived features are excluded from progress calculations
-
-### 3. Progress Synchronization
-- Task completion triggers feature progress update
-- Feature progress updates trigger milestone recalculation
-- All updates are timestamped for audit trail
-
-## Integration Queries
-
-### Find Features by Milestone
-```bash
-/project:aiwf:list_features --milestone M02
-```
-
-### Find Features by Sprint
-```bash
-/project:aiwf:list_features --sprint S01_M02
-```
-
-### Feature Impact Analysis
-```bash
-/project:aiwf:feature_impact FL001
-# Shows: Related tasks, sprints, blocking features
-```
-
-## Reporting Integration
-
-### Milestone Report includes:
-- Feature count by status
-- Overall progress percentage
-- Feature complexity distribution
-- Estimated vs actual timeline
-
-### Sprint Report includes:
-- Active features
-- Feature progress within sprint
-- Task completion rate
-- Velocity metrics
-
-### Feature Report includes:
-- Task breakdown
-- Sprint allocation
-- Time tracking
-- Dependency graph
-
-## Best Practices
-
-1. **Plan Features First**: Define features before creating tasks
-2. **Update Regularly**: Keep progress percentages current
-3. **Cross-Reference**: Ensure bidirectional links are maintained
-4. **Review Dependencies**: Check for blocked features before sprint planning
-5. **Archive Completed**: Move completed features to maintain performance
-
-## Automated Workflows
-
-### On Feature Creation:
-1. Generate unique feature ID
-2. Link to active milestone
-3. Create in active sprint (if in progress)
-4. Initialize progress tracking
-
-### On Task Completion:
-1. Update feature task list
-2. Recalculate feature progress
-3. Check if feature is complete
-4. Propagate to milestone
-
-### On Sprint Close:
-1. Review feature progress
-2. Move incomplete features to next sprint
-3. Archive completed features
-4. Generate sprint report
-
-## Error Handling
-
-### Common Issues:
-1. **Orphaned Features**: Features without milestone
-2. **Broken References**: Tasks referencing non-existent features
-3. **Circular Dependencies**: Features depending on each other
-4. **Stale Progress**: Outdated progress percentages
-
-### Resolution:
-- Regular integrity checks
-- Automated fixing scripts
-- Manual review process
-- Audit trail for changes

package/.aiwf/06_FEATURE_LEDGERS/FEATURE_LEDGER_INDEX.md

@@ -1,23 +0,0 @@
-# Feature Ledger 인덱스
-
-마지막 업데이트: 2025-07-10T02:37:15.882Z
-
-## 활성 Features
-
-| ID | 제목 | 상태 | 우선순위 | 진행률 | 업데이트 |
-|----|------|------|----------|--------|----------|
-| FL001 | User Authentication System | active | medium | 0% | 2025-07-10 |
-| FL002 | User Authentication System | active | medium | 0% | 2025-07-10 |
-
-## 보관된 Features
-
-| ID | 제목 | 완료일 |
-|----|------|--------|
-
-## 통계
-
-- 총 Features: 2
-- 활성: 2
-- 완료: 0
-- 일시 중지: 0
-- 보관됨: 0

package/.aiwf/06_FEATURE_LEDGERS/FEATURE_SCHEMA.md

@@ -1,205 +0,0 @@
-# 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

@@ -1,190 +0,0 @@
-# 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

@@ -1,47 +0,0 @@
-# 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: (미생성)
-- 이슈: (미생성)