aiwf 0.3.8 → 0.3.12

package/claude-code/aiwf/en/.aiwf/10_STATE_OF_PROJECT/2025-06-14-08-30-infrastructure-challenges.md

@@ -1,141 +0,0 @@
-# Project Review - [2025-06-14 08:30]
-
-## 🎭 Review Sentiment
-
-⚠️💪🔧
-
-## Executive Summary
-
-- **Result:** NEEDS_WORK
-- **Scope:** Full project review including architecture, testing, and sprint progress
-- **Overall Judgment:** infrastructure-challenges
-
-## Test Infrastructure Assessment
-
-- **Test Suite Status**: FAILING (19/759 failures)
-- **Test Pass Rate**: 97.5% (740 passed, 19 failed)
-- **Test Health Score**: 8/10
-- **Infrastructure Health**: DEGRADED
-  - Import errors: 4 (supertest imports)
-  - Configuration errors: 2 (database optimizer methods)
-  - Fixture issues: 0
-- **Test Categories**:
-  - Unit Tests: ~95% passing
-  - Integration Tests: ~98% passing  
-  - API Tests: Mixed due to TypeScript errors
-- **Critical Issues**:
-  - TypeScript compilation errors in supertest imports preventing E2E tests
-  - Missing method definitions in database optimizer base classes
-  - Dashboard service logic errors with undefined handling
-  - Excessive console.log statements throughout test code
-- **Sprint Coverage**: 80% of sprint deliverables have tests but many are broken
-- **Blocking Status**: BLOCKED - TypeScript compilation errors preventing reliable CI/CD
-- **Recommendations**:
-  - Fix supertest import syntax immediately
-  - Add missing getPerformanceMetrics and getSlowQueries methods to BaseDatabaseOptimizer
-  - Remove console.log statements from production code and tests
-
-## Development Context
-
-- **Current Milestone:** M01 - MVP 안정화 및 핵심 기능 강화
-- **Current Sprint:** S01 - 테스트 인프라 복구
-- **Expected Completeness:** Sprint S01 should be establishing stable test infrastructure as foundation for all other work
-
-## Progress Assessment
-
-- **Milestone Progress:** 20% complete (significant work done on monitoring/optimization but core issues remain)
-- **Sprint Status:** 40% complete but blocked by fundamental infrastructure issues
-- **Deliverable Tracking:** 
-  - ❌ Test infrastructure: Not stable (19 failing tests)
-  - ❌ File system cleanup: Directory typos still exist (`entites`, `tabel-query`)
-  - ❌ Root directory cleanup: `identifier.sqlite` and `package-lock.json` still in root
-  - ⚠️ Test coverage: Tests exist but quality is poor
-
-## Architecture & Technical Assessment
-
-- **Architecture Score:** 7/10 - Well-structured NestJS modular design but implementation has gaps
-- **Technical Debt Level:** MEDIUM with specific examples:
-  - Duplicate entity directories (`entites` vs `entities`)
-  - Inconsistent error handling across modules
-  - Global knex connection map pattern creates potential memory leaks
-  - Console.log statements scattered throughout production code
-- **Code Quality:** Good structure marred by implementation details and test quality issues
-
-## File Organization Audit
-
-- **Workflow Compliance:** CRITICAL_VIOLATIONS
-- **File Organization Issues:** 
-  - Directory misspellings: `/src/auth/entites/` should be `/src/auth/entities/`
-  - Directory misspellings: `/src/widget/tabel-query/` should be `/src/widget/table-query/`
-  - Root directory pollution: `identifier.sqlite` and `package-lock.json` files in project root
-  - Duplicate entity directories in auth module
-- **Cleanup Tasks Needed:** 
-  - Rename `entites` → `entities` in auth module
-  - Rename `tabel-query` → `table-query` in widget module  
-  - Remove `identifier.sqlite` and `package-lock.json` from project root
-  - Update all imports to reflect corrected directory names
-
-## Critical Findings
-
-### Critical Issues (Severity 8-10)
-
-#### Test Infrastructure Blocking CI/CD
-
-TypeScript compilation failures prevent reliable automated testing and deployment:
-- Supertest import syntax errors in compression and warmup tests
-- Missing method definitions in BaseDatabaseOptimizer class
-- Dashboard service undefined reference errors
-
-#### File System Inconsistencies
-
-Directory name typos create confusion and maintenance burden:
-- `entites` instead of `entities` in auth module
-- `tabel-query` instead of `table-query` in widget module
-- These inconsistencies are referenced throughout the codebase
-
-### Improvement Opportunities (Severity 4-7)
-
-#### Code Quality Improvements
-
-Remove console.log statements from production code:
-- Dashboard service has extensive debugging output
-- Serverless bootstrap has console.log statements
-- Test files contain debugging output that should use proper logging
-
-#### Architecture Refinements  
-
-Global connection map pattern needs review:
-- `knexConnections` global Map in ConnectionService creates potential memory leaks
-- No cleanup mechanism for stale connections
-- Consider connection pooling strategy aligned with Lambda lifecycle
-
-## John Carmack Critique 🔥
-
-1. **"You're overthinking the simple stuff"** - Directory names like `entites` and `tabel-query` are basic typos that should never make it to production. These create cognitive overhead for every developer who touches the code.
-
-2. **"Console.log is not a logging strategy"** - Scattered console.log statements throughout production code indicate lack of proper logging infrastructure. In a serverless environment, this creates noise and makes debugging harder, not easier.
-
-3. **"Test quality reflects system quality"** - 97.5% pass rate sounds good until you realize 19 tests failing due to TypeScript errors means your build pipeline is fundamentally broken. A test that doesn't compile is worse than no test at all.
-
-## Recommendations
-
-Based on your findings recommend Action items - chose whatever fits your findings
-
-- **Important fixes:** 
-  - Fix TypeScript compilation errors in test files (supertest imports)
-  - Rename misspelled directories and update all imports
-  - Add missing methods to BaseDatabaseOptimizer class
-  - Remove console.log statements from production code
-  - Clean up root directory files
-
-- **Optional fixes/changes:** 
-  - Improve connection pool management strategy
-  - Standardize error handling patterns across modules
-  - Enhance test quality with proper assertions instead of structure tests
-  - Implement proper correlation ID tracking throughout request lifecycle
-
-- **Next Sprint Focus:** 
-  - Cannot proceed to next sprint until S01 deliverables are complete
-  - Test infrastructure must be stable before moving to system stability improvements
-  - File system cleanup is a prerequisite for reliable development workflow
-  - Recommend completing current sprint before advancing to S02

package/claude-code/aiwf/en/.aiwf/10_STATE_OF_PROJECT/2025-06-16-21-48-critical-foundation-issues.md

@@ -1,177 +0,0 @@
-# Project Review - 2025-06-16 21:48
-
-## 🎭 Review Sentiment
-
-😰🔥⚠️
-
-## Executive Summary
-
-- **Result:** CRITICAL_ISSUES
-- **Scope:** Full project review covering all 7 sprints and technical infrastructure
-- **Overall Judgment:** Critical Foundation Issues
-
-## Test Infrastructure Assessment
-
-- **Test Suite Status**: FAILING (817/850 tests passing)
-- **Test Pass Rate**: 96.1% (817 passed, 33 failed)
-- **Test Health Score**: 3/10
-- **Infrastructure Health**: BROKEN
-  - Import errors: 8+ modules
-  - Configuration errors: 12+ TypeScript compilation failures
-  - Fixture issues: 3+ test setup problems
-- **Test Categories**:
-  - Unit Tests: ~400/450 passing (89%)
-  - Integration Tests: ~200/220 passing (91%)
-  - API Tests: ~217/180 passing (120% - more tests than expected)
-- **Critical Issues**:
-  - **DashboardLayout class declaration order**: TypeScript compilation error affecting 5+ test files
-  - **Missing custom-logger.service**: Module import failures in QTT-002 tests
-  - **Streaming service async/await**: 3+ test files with incorrect async handling
-  - **Express app type mismatch**: NestJS testing setup issues
-  - **JWT Auth Guard missing**: Import path errors in metrics controller
-- **Sprint Coverage**: 0% of S01 deliverables have passing tests (S01 is 0% complete)
-- **Blocking Status**: BLOCKED - Critical test infrastructure prevents reliable development
-- **Recommendations**:
-  - **EMERGENCY**: Fix TypeScript compilation errors immediately
-  - **P0**: Resolve missing module imports and path issues
-  - **P1**: Standardize async/await patterns in streaming tests
-  - **P2**: Implement missing authentication modules
-
-## Development Context
-
-- **Current Milestone:** M01 - MVP 안정화 및 핵심 기능 강화 (35% complete)
-- **Current Sprint:** S01 - 테스트 인프라 복구 (0% complete)
-- **Expected Completeness:** S01 should be 100% complete before any other sprints
-
-## Progress Assessment
-
-- **Milestone Progress:** 35% (critically behind schedule)
-- **Sprint Status:** REVERSED PRIORITY - S01 (0%) while S05-S07 (95-100%)
-- **Deliverable Tracking:** Fatal sprint sequence violation detected
-
-**Sprint Completion Matrix:**
-- S01 (Foundation): 0% ❌ **CRITICAL**
-- S02 (Stability): 17% ❌ **CRITICAL** 
-- S03 (DB Performance): 29% ⚠️
-- S04 (API Optimization): 0% ❌
-- S05 (Frontend): 100% ✅ **OUT OF ORDER**
-- S06 (Data Processing): 100% ✅ **OUT OF ORDER**
-- S07 (Monitoring): 95% ✅ **OUT OF ORDER**
-
-## Architecture & Technical Assessment
-
-- **Architecture Score:** 6/10 - Good design undermined by execution issues
-- **Technical Debt Level:** HIGH with critical infrastructure debt
-  - 22 failing tests in production codebase
-  - Node.js 14.x (EOL) version
-  - TypeScript strict mode disabled
-  - Sprint dependency violations
-  - Duplicate dependencies (sequelize + TypeORM)
-- **Code Quality:** Mixed - excellent modular design but broken CI/CD pipeline
-
-**Strengths:**
-- Modular NestJS architecture with 33 well-organized domains
-- Comprehensive monitoring and optimization systems
-- 50+ chart types with React component architecture
-- Dual ORM pattern (TypeORM + Knex) for flexible DB connections
-
-**Critical Weaknesses:**
-- Test infrastructure collapse
-- Sprint sequencing violations  
-- Foundation components not implemented
-- Production-ready features built on unstable base
-
-## File Organization Audit
-
-- **Workflow Compliance:** CRITICAL_VIOLATIONS
-- **File Organization Issues:** 
-  - Root directory pollution: `identifier.sqlite`, unnecessary `package-lock.json`, `node_modules/`
-  - Test files scattered in `/src/` instead of `/tests/`
-  - Temporary files committed: `test-results.log`, `snowflake.log`, `sqlite.db`
-  - Development scripts in wrong locations: `test-warmup.js`, `init.sh`
-- **Cleanup Tasks Needed:** 
-  - Remove 4+ unnecessary root files
-  - Reorganize 50+ test files to proper directories
-  - Move 3+ scripts to `/scripts/` directories
-  - Add 10+ file patterns to `.gitignore`
-
-## Critical Findings
-
-### Critical Issues (Severity 8-10)
-
-#### Foundation Collapse
-- **S01 sprint (0% complete)** is the foundation for all other work
-- 22 failing tests prevent reliable development pipeline
-- TypeScript compilation errors block CI/CD
-- No basic error handling or logging infrastructure
-
-#### Development Process Breakdown
-- **Sprint sequence completely reversed** - building roof before foundation
-- Test-driven development impossible with broken test infrastructure
-- Quality assurance pipeline non-functional
-
-#### Technical Infrastructure Debt
-- **Node.js 14.x EOL version** poses security and compatibility risks
-- **Dual ORM without proper abstraction** creates maintenance complexity
-- **Missing authentication guards** in production code
-
-### Improvement Opportunities (Severity 4-7)
-
-#### Documentation Excellence Undermined
-- Exceptional documentation quality but implementation doesn't follow
-- Architecture decisions well-documented but not enforced
-- Sprint planning detailed but not followed
-
-#### Over-Engineering vs Under-Engineering
-- **Over-engineered**: 25 CloudWatch metrics, excessive optimization
-- **Under-engineered**: Basic error handling, authentication, logging
-
-#### Advanced Features on Unstable Base
-- Sophisticated monitoring system built without basic infrastructure
-- Complex database optimizations before query fundamentals
-- Enterprise-grade features without production-ready foundation
-
-## John Carmack Critique 🔥
-
-1. **"You're optimizing the graphics engine while the input system is broken"** - The project has advanced monitoring and optimization features (S05-S07) but fails at basic test infrastructure (S01). This violates the fundamental principle of building solid foundations first.
-
-2. **"Complexity is the enemy of reliability"** - The dual ORM pattern (TypeORM + Knex) and 25 monitoring metrics add complexity that isn't justified when basic functionality doesn't work reliably. Focus on making one thing work well before adding layers.
-
-3. **"Testing isn't optional in shipped code"** - Having 22 failing tests in production code is unacceptable. No feature should be considered "complete" without passing tests. The sprint reversal has created a house of cards that will collapse under real usage.
-
-## Recommendations
-
-### Emergency Actions (Within 24 hours)
-- **STOP all new feature development**
-- **Fix all 22 TypeScript compilation errors**
-- **Complete S01 sprint: test infrastructure recovery**
-- **Establish passing test pipeline before any other work**
-
-### Critical Fixes (Within 1 week)
-- **Upgrade Node.js 14.x → 18.x LTS**
-- **Enable TypeScript strict mode**
-- **Implement global error handling (S02)**
-- **Clean up file organization violations**
-
-### Important Fixes (Within 2 weeks)
-- **Complete S02 system stability foundations**
-- **Review and test all S05-S07 features for stability**
-- **Establish proper sprint dependency enforcement**
-- **Reduce monitoring complexity to essential metrics**
-
-### Optional Improvements (Within 1 month)
-- **Standardize API response patterns**
-- **Consolidate dual ORM usage patterns**
-- **Implement missing authentication features**
-- **Document actual vs planned architecture**
-
-### Next Sprint Focus
-**Cannot proceed to next sprint until S01 is 100% complete.**
-
-Current sprint progression should be:
-1. **Emergency S01 completion** (test infrastructure)
-2. **S02 system stability** (error handling, logging)
-3. **Verification of S05-S07** (ensure stability on solid foundation)
-4. **Continue with S03-S04** (performance optimization)
-
-**Final Assessment:** This project demonstrates excellent architectural vision and advanced technical capabilities, but has fundamentally violated software development principles by building advanced features on an unstable foundation. Immediate correction is required to prevent total system collapse.

package/claude-code/aiwf/en/.aiwf/10_STATE_OF_PROJECT/2025-06-17-15-08-solid-progress.md

@@ -1,149 +0,0 @@
-# Project Review - 2025-06-17 15:08
-
-## 🎭 Review Sentiment
-
-🚀💪⚠️
-
-## Executive Summary
-
-- **Result:** GOOD
-- **Scope:** Full project review focusing on architecture, test infrastructure, sprint progress, and technical implementation
-- **Overall Judgment:** solid-progress
-
-## Test Infrastructure Assessment
-
-- **Test Suite Status**: FAILING (367/372 tests)
-- **Test Pass Rate**: 98.7% (367 passed, 5 failed)
-- **Test Health Score**: 7/10
-- **Infrastructure Health**: DEGRADED
-  - Import errors: 0
-  - Configuration errors: 0
-  - Fixture issues: 0
-- **Test Categories**:
-  - Unit Tests: 367/372 passing
-  - Integration Tests: Included in unit count
-  - API Tests: E2E tests present but not executed
-- **Critical Issues**:
-  - app.controller.spec.ts - Expectation mismatch
-  - connection.service.spec.ts - TypeScript compilation errors
-  - dataset/database/batch/events controller/service tests failing
-- **Sprint Coverage**: 90% of sprint deliverables have tests
-- **Blocking Status**: CLEAR - Does not block sprint progression (>95% pass rate)
-- **Recommendations**:
-  - Fix failing tests immediately
-  - Address TypeScript type mismatches
-  - Run E2E tests in CI pipeline
-
-## Development Context
-
-- **Current Milestone:** M01 - MVP 안정화 및 핵심 기능 강화 (Active)
-- **Current Sprint:** S01 per manifest, but actually working on S07 tasks
-- **Expected Completeness:** 93% of all tasks complete across all sprints
-
-## Progress Assessment
-
-- **Milestone Progress:** 93% complete (40/43 tasks)
-- **Sprint Status:** 
-  - S01-S06: 100% complete
-  - S07: 62.5% complete (5/8 tasks)
-- **Deliverable Tracking:**
-  - Monitoring infrastructure: ✅ Complete
-  - Performance optimization: ✅ Complete
-  - System stability: ⬜ Not started
-  - Large data handling: ⬜ Not started
-  - Testing enhancement: ⬜ Not started
-
-## Architecture & Technical Assessment
-
-- **Architecture Score:** 7/10 - Well-structured but overly complex in places
-- **Technical Debt Level:** MEDIUM
-  - Duplicate folders (auth/entites vs entities)
-  - Test files in root directory
-  - Overly complex optimization layers
-  - Excessive monitoring systems
-- **Code Quality:** Generally high with good separation of concerns, but suffering from over-engineering
-
-## File Organization Audit
-
-- **Workflow Compliance:** NEEDS_ATTENTION
-- **File Organization Issues:**
-  - Duplicate entity folders: `auth/entites/` and `auth/entities/`
-  - Duplicate query folders: `widget/tabel-query/` and `widget/table-query/`
-  - Test files scattered in root: `test-warmup.js`, `test-connect-info.json`
-  - Temporary controllers in src: `test-compression.controller.ts`, `test-field-selection.controller.ts`
-  - Generated/log files in root: `swagger-spec.json`, `snowflake.log`, `sqlite.db`
-- **Cleanup Tasks Needed:**
-  - Remove duplicate folders and consolidate files
-  - Move test files to appropriate test directories
-  - Remove or properly place temporary test controllers
-  - Add generated files to .gitignore
-
-## Critical Findings
-
-### Critical Issues (Severity 8-10)
-
-#### Test Infrastructure Degradation
-
-- 5 failing tests indicate broken functionality
-- TypeScript compilation errors in connection service
-- Test failures not being addressed promptly
-
-#### File Organization Violations
-
-- Duplicate folders causing confusion
-- Test files polluting root directory
-- Temporary files committed to repository
-
-### Improvement Opportunities (Severity 4-7)
-
-#### Over-Engineering
-
-- Too many monitoring systems (CloudWatch, SlowQuery, Memory, Business metrics)
-- Complex caching layers (Redis + in-memory hybrid)
-- Excessive database optimizers for each DB type
-
-#### Sprint/Task Management
-
-- Manifest shows S01 as current but work happening on S07
-- Some task statuses not updated (T04_S07 marked complete but status still "open")
-
-#### Technical Debt
-
-- Accumulating test failures
-- Complex dependency chains
-- Premature optimization
-
-## John Carmack Critique 🔥
-
-1. **"Stop building monitoring systems and start building features"** - You have CloudWatch integration, slow query monitoring, memory monitoring, business metrics, and performance monitoring. Pick ONE comprehensive solution and delete the rest. Every monitoring system is code that can break.
-
-2. **"Your 5-layer deep optimization stack is a performance anti-pattern"** - ConnectionService → DatabaseOptimizer → QueryOptimizer → CacheService → actual query. Each layer adds latency. Most queries would be faster with a direct connection and good indexes.
-
-3. **"Broken tests are worse than no tests"** - You have 5 failing tests that everyone is ignoring. Either fix them TODAY or delete them. A test suite that doesn't pass 100% trains developers to ignore failures.
-
-## Recommendations
-
-Based on your findings recommend Action items - chose whatever fits your findings
-
-- **Important fixes:**
-  1. Fix all 5 failing tests immediately
-  2. Clean up duplicate folders (auth/entites, widget/tabel-query)
-  3. Remove test files from root directory
-  4. Update task statuses to reflect reality (T04_S07)
-  5. Consolidate monitoring systems into one solution
-
-- **Optional fixes/changes:**
-  1. Simplify database optimization layers
-  2. Remove premature optimization code
-  3. Reduce monitoring overhead
-  4. Implement actual E2E test execution
-  5. Add stricter linting rules for file organization
-
-- **Next Sprint Focus:** 
-  Yes, the project can move to the next sprint, but should prioritize:
-  - System stability improvements (error handling, logging)
-  - Complete remaining S07 tasks (T05, T06)
-  - Address technical debt before adding new features
-  - Focus on core functionality over monitoring
-
-The project shows solid progress with 93% task completion and good architectural foundations. However, it's suffering from over-engineering and needs immediate attention to test failures and file organization. The team should resist adding more monitoring/optimization features and focus on completing the MVP stabilization milestone with simpler, more maintainable solutions.

package/claude-code/aiwf/en/.aiwf/10_STATE_OF_PROJECT/index.json

@@ -1,5 +0,0 @@
-{
-    "milestones": {},
-    "sprints": {},
-    "tasks": {}
-}

package/claude-code/aiwf/en/.aiwf/10_STATE_OF_PROJECT/sync-index.js

@@ -1,78 +0,0 @@
-import fs from 'fs';
-import path from 'path';
-import fg from 'fast-glob';
-import matter from 'gray-matter';
-
-const ROOT = path.resolve(process.cwd(), 'claude-code/aiwf/.aiwf');
-const OUTPUT = path.join(ROOT, '10_STATE_OF_PROJECT', 'index.json');
-
-// Directories to scan for milestone/sprint/task markdown files
-const SCAN_DIRS = [
-    '01_PROJECT_DOCS',
-    '02_REQUIREMENTS',
-    '03_SPRINTS',
-    '04_GENERAL_TASKS'
-].map(dir => path.join(ROOT, dir));
-
-function ensureDirSync(dir) {
-    if (!fs.existsSync(dir)) {
-        fs.mkdirSync(dir, { recursive: true });
-    }
-}
-
-function buildIndex() {
-    /** @type {{milestones: Record<string, any>, sprints: Record<string, any>, tasks: Record<string, any>}} */
-    const index = { milestones: {}, sprints: {}, tasks: {} };
-
-    const patterns = SCAN_DIRS.map(d => `${d}/**/*.md`);
-    const files = fg.sync(patterns, { dot: false, unique: true });
-
-    files.forEach(file => {
-        const relPath = path.relative(ROOT, file);
-        const content = fs.readFileSync(file, 'utf-8');
-        const { data } = matter(content);
-        if (!data || !data.id || !data.type) return; // skip non-annotated files
-
-        const base = {
-            title: data.title || path.basename(file, '.md'),
-            file: relPath,
-            status: data.status || 'todo',
-            ...(data.assignee ? { assignee: data.assignee } : {}),
-            ...(data.tags ? { tags: data.tags } : {}),
-            ...(data.lockedBy ? { lockedBy: data.lockedBy } : {})
-        };
-
-        if (data.type === 'milestone') {
-            index.milestones[data.id] = {
-                ...base,
-                due: data.due || null,
-                sprints: data.sprints || []
-            };
-        } else if (data.type === 'sprint') {
-            index.sprints[data.id] = {
-                ...base,
-                milestone: data.milestone || null,
-                tasks: data.tasks || []
-            };
-        } else if (data.type === 'task') {
-            index.tasks[data.id] = {
-                ...base,
-                sprint: data.sprint || null,
-                milestone: data.milestone || null
-            };
-        }
-    });
-
-    return index;
-}
-
-function main() {
-    const index = buildIndex();
-    ensureDirSync(path.dirname(OUTPUT));
-    fs.writeFileSync(OUTPUT, JSON.stringify(index, null, 2));
-    console.log(`[aiwf] index.json generated with ${Object.keys(index.milestones).length} milestones, ${Object.keys(index.sprints).length} sprints, ${Object.keys(index.tasks).length} tasks.`);
-}
-
-if (require.main === module) {
-    main();
-} 

package/claude-code/aiwf/en/.aiwf/98_PROMPTS/github_integration.md

@@ -1,130 +0,0 @@
-# GitHub Integration with AIWF Framework
-
-This document provides guidance on integrating GitHub issues and pull requests with the AIWF task management system.
-
-## Overview
-
-The AIWF framework now supports seamless integration with GitHub issues and pull requests, enabling better tracking and collaboration through the `gh` CLI tool.
-
-## Key Features
-
-### 1. Task-Issue Linking
-
-- Each task can be linked to a GitHub issue via the `github_issue` field in frontmatter
-- Automatic status synchronization between tasks and issues
-- Bidirectional updates ensure consistency
-
-### 2. Automated Workflows
-
-- Create GitHub issues from tasks: `/project:aiwf:issue_create {task_id}`
-- Generate pull requests with issue linking: `/project:aiwf:pr_create {task_id}`
-- Commit messages automatically include issue references
-
-### 3. Status Management
-
-- Task status changes trigger GitHub issue updates
-- Issues are labeled based on task status (in-progress, completed, etc.)
-- Comments are added to issues for transparency
-
-## Commands Reference
-
-### Issue Creation
-
-```bash
-/project:aiwf:issue_create {task_id}
-```
-
-Creates a GitHub issue from a task file with:
-
-- Title including task ID
-- Description from task content
-- Appropriate labels
-- Automatic assignment
-
-### Pull Request Creation
-
-```bash
-/project:aiwf:pr_create {task_id}
-```
-
-Creates a pull request that:
-
-- Links to the associated issue
-- Includes commit history
-- Auto-closes issue on merge
-- Assigns reviewers
-
-### Manual GitHub Commands
-
-Update issue status:
-
-```bash
-gh issue comment {issue_number} --body "Status update message"
-gh issue edit {issue_number} --add-label "label-name"
-```
-
-Create issue manually:
-
-```bash
-gh issue create \
-  --title "Task: Description" \
-  --body "Detailed description" \
-  --label "task,sprint-01"
-```
-
-## Best Practices
-
-### 1. Issue Creation Timing
-
-- Create issues when starting a sprint
-- Link issues immediately after creation
-- Update frontmatter with issue number
-
-### 2. Commit Messages
-
-- Use `fixes #123` for bug fixes
-- Use `relates to #123` for partial work
-- Include task ID in commit message
-
-### 3. Pull Request Workflow
-
-- Create PR after task completion
-- Ensure all tests pass
-- Link to original issue
-- Request appropriate reviewers
-
-## Integration Points
-
-### Task Files
-
-Add to frontmatter:
-
-```yaml
-github_issue: #123
-```
-
-### Sprint Planning
-
-- Create issues for all tasks at sprint start
-- Use labels to group by sprint
-- Track progress via GitHub Projects
-
-### YOLO Mode
-
-- Automatically creates issues if enabled
-- Creates PRs after successful commits
-- Maintains full automation flow
-
-## Troubleshooting
-
-### Common Issues
-
-1. **Missing gh CLI**: Install GitHub CLI first
-2. **Authentication**: Run `gh auth login`
-3. **Permissions**: Ensure repo access rights
-
-### Error Handling
-
-- Check task file for valid issue number
-- Verify GitHub API limits
-- Ensure branch protection rules allow automation