aiwf 0.1.0 → 0.3.1

package/claude-code/aiwf/en/.claude/settings.json

@@ -0,0 +1,102 @@
+{
+    "permissions": {
+        "allow": [
+            "Bash(deno task *)",
+            "Bash(npm run *)",
+            "Bash(cargo *)",
+            "Bash(go *)",
+            "Bash(git *)",
+            "Bash(git worktree *)",
+            "Bash(gh *)",
+            "Bash(docker *)",
+            "Bash(kubectl *)",
+            "Bash(terraform *)",
+            "Bash(rg *)",
+            "Bash(ripgrep *)",
+            "Bash(fd *)",
+            "Bash(fzf *)",
+            "Bash(bat *)",
+            "Bash(exa *)",
+            "Bash(eza *)",
+            "Bash(delta *)",
+            "Bash(zoxide *)",
+            "Bash(duf *)",
+            "Bash(htop *)",
+            "Bash(btop *)",
+            "Bash(jq *)",
+            "Bash(yq *)",
+            "Bash(hexyl *)",
+            "Bash(prettier *)",
+            "Bash(eslint *)",
+            "Bash(tsc *)",
+            "Bash(pnpm *)",
+            "Bash(yarn *)",
+            "Bash(mkdir -p /tmp/claude-scratch*)",
+            "Bash(touch /tmp/claude-*)",
+            "Bash(echo * > /tmp/claude-*)",
+            "Bash(cat /tmp/claude-*)"
+        ],
+        "deny": [
+            "Bash(rm -rf /)",
+            "Bash(:(){ :|:& };:)",
+            "Bash(dd if=/dev/zero of=/dev/*)",
+            "Bash(mkfs.*)",
+            "Bash(> /dev/sda*)"
+        ]
+    },
+    "env": {
+        "CLAUDE_CODE_ENABLE_TELEMETRY": "0",
+        "EDITOR": "zed",
+        "GIT_EDITOR": "zed --wait"
+    },
+    "preferredNotifChannel": "terminal_bell",
+    "verbose": true,
+    "cleanupPeriodDays": 90,
+    "includeCoAuthoredBy": false,
+    "hooks": {
+        "beforeFileEdit": [
+            {
+                "command": "npm run lint:fix --silent || true",
+                "description": "Auto lint fix before file edit"
+            }
+        ],
+        "afterFileEdit": [
+            {
+                "command": "prettier --write {file} || true",
+                "description": "Auto format after file edit"
+            }
+        ],
+        "beforeCommit": [
+            {
+                "command": "npm run lint || echo 'Lint check failed'",
+                "description": "Lint check before commit"
+            },
+            {
+                "command": "npm run test || echo 'Test failed'",
+                "description": "Run tests before commit"
+            }
+        ],
+        "Stop": [
+            {
+                "matcher": "",
+                "hooks": [
+                    {
+                        "type": "command",
+                        "command": "afplay /System/Library/Sounds/Glass.aiff"
+                    }
+                ]
+            }
+        ],
+        "PostToolUse": [
+            {
+                "matcher": "Write|Edit|MultiEdit",
+                "hooks": [
+                    {
+                        "type": "command",
+                        "command": "aiwf_test"
+                    }
+                ]
+            }
+        ]
+    }
+}

package/claude-code/aiwf/ko/.aiwf/00_PROJECT_MANIFEST.md

@@ -0,0 +1,49 @@
+---
+project_name: Your Project Name
+current_milestone_id: M01
+highest_sprint_in_milestone: S02
+current_sprint_id: S01
+status: active
+last_updated: 2025-01-01 00:00:00
+---
+
+# Project Manifest: Your Project Name
+
+This manifest serves as the central reference point for the project. It tracks the current focus and links to key documentation.
+
+## 1. Project Vision & Overview
+
+[Describe your project's core vision, purpose, and goals here. What problem does it solve? Who is it for? What makes it unique?]
+
+This project follows a milestone-based development approach.
+
+## 2. Current Focus
+
+- **Milestone:** M01 - [Your First Milestone Name]
+- **Sprint:** S01 - [Current Sprint Focus]
+
+## 3. Sprints in Current Milestone
+
+### S01 [Sprint Name] (🚧 IN PROGRESS)
+
+🚧 [First deliverable or feature]
+📋 [Second deliverable or feature]
+📋 [Third deliverable or feature]
+
+### S02 [Sprint Name] (📋 PLANNED)
+
+📋 [First planned deliverable]
+📋 [Second planned deliverable]
+📋 [Third planned deliverable]
+
+## 4. Key Documentation
+
+- [Architecture Documentation](./01_PROJECT_DOCS/ARCHITECTURE.md)
+- [Current Milestone Requirements](./02_REQUIREMENTS/M01_[Milestone_Name]/)
+- [General Tasks](./04_GENERAL_TASKS/)
+
+## 5. Quick Links
+
+- **Current Sprint:** [S01 Sprint Folder](./03_SPRINTS/S01_M01_[Sprint_Name]/)
+- **Active Tasks:** Check sprint folder for T##_S01_*.md files
+- **Project Reviews:** [Latest Review](./10_STATE_OF_PROJECT/)

package/claude-code/aiwf/ko/.aiwf/01_PROJECT_DOCS/ARCHITECTURE.md

@@ -0,0 +1,55 @@
+# Demo Project Architecture (EXAMPLE)
+
+This document outlines the high-level architecture of the Demo Project. **This is an example document to demonstrate how architecture might be documented in the AIWF framework.**
+
+## System Overview
+
+This is a demonstration of how a system architecture document might be structured. In a real project, this would contain actual architectural details.
+
+## Technical Architecture (Example)
+
+### Backend
+
+- **API Layer**: Node.js with Express.js
+- **Database**: MongoDB for primary data storage
+- **Authentication**: JWT-based authentication with OAuth support
+- **Caching**: Redis for performance optimization
+- **Testing**: Jest for unit and integration testing
+
+### Frontend
+
+- **Web Client**: React.js with TypeScript
+- **Mobile Apps**: React Native for iOS and Android
+- **State Management**: Redux for predictable state
+- **UI Framework**: Material-UI for consistent design
+
+## System Components (Example)
+
+1. **Authentication Service**: Handles user signup, login, and session management
+2. **Project Management Service**: Manages projects, teams, and permissions
+3. **Task Service**: Core task CRUD operations and business logic
+4. **Notification Service**: Manages user notifications and alerts
+5. **Analytics Service**: Provides usage statistics and reporting
+
+## Data Flow (Example)
+
+1. Clients authenticate through the Authentication Service
+2. Authenticated requests are routed to the appropriate service
+3. Services interact with the database and return responses
+4. Real-time updates are pushed to clients via WebSockets
+
+## Deployment Architecture (Example)
+
+The system is deployed using containerization with Docker and Kubernetes, providing:
+
+- Horizontal scalability for handling load spikes
+- High availability through multiple replicas
+- Zero-downtime deployments
+- Environment isolation (development, staging, production)
+
+## Security Considerations (Example)
+
+- All API endpoints are protected with proper authentication
+- Sensitive data is encrypted at rest and in transit
+- Rate limiting is implemented to prevent abuse
+- Regular security audits and penetration testing

package/claude-code/aiwf/ko/.aiwf/02_REQUIREMENTS/CLAUDE.md

@@ -0,0 +1,78 @@
+# CLAUDE.md - Requirements Folder Structure Guide
+
+## Overview
+This folder contains all project milestones and their associated requirements documentation. Each milestone represents a major project phase or feature set.
+
+## Milestone Naming Convention
+**CRITICAL**: Milestone folders MUST follow this exact pattern:
+```
+M##_Milestone_Name/
+```
+
+- `M##` - Two-digit milestone number (M01, M02, etc.)
+- `_` - Single underscore separator
+- `Milestone_Name` - Descriptive name using underscores for spaces
+
+### Examples:
+- ✅ `M01_Backend_Setup/`
+- ✅ `M02_Frontend_UI/`
+- ✅ `M03_Authentication_System/`
+- ❌ `M1_Backend/` (missing leading zero)
+- ❌ `M01-Backend-Setup/` (wrong separator)
+- ❌ `Backend_Setup/` (missing M## prefix)
+
+## Milestone Structure
+Each milestone folder MUST contain:
+
+### 1. Milestone Meta File (REQUIRED)
+- **Name**: `M##_milestone_meta.md`
+- **Purpose**: Contains milestone metadata and overview
+- **Location**: Root of milestone folder
+
+### 2. Product Requirements Documents (PRD)
+- **Pattern**: `PRD_*.md`
+- **Examples**: `PRD_Backend_Setup.md`, `PRD_User_Authentication.md`
+- **Purpose**: Define product requirements and user stories
+
+### 3. Technical Specifications
+- **Pattern**: `SPECS_*.md`
+- **Examples**: `SPECS_API_V1.md`, `SPECS_Database_Schema.md`
+- **Purpose**: Technical implementation details
+
+### 4. Amendments (as needed)
+- **Pattern**: `PRD_AMEND_##_*.md`
+- **Examples**: `PRD_AMEND_01_Additional_Endpoints.md`
+- **Purpose**: Document changes to original requirements
+
+## Example Structure
+```
+02_REQUIREMENTS/
+├── M01_Backend_Setup/
+│   ├── M01_milestone_meta.md
+│   ├── PRD_Backend_Setup.md
+│   ├── SPECS_API_V1.md
+│   └── PRD_AMEND_01_Cache_Layer.md
+├── M02_Frontend_UI/
+│   ├── M02_milestone_meta.md
+│   ├── PRD_User_Interface.md
+│   └── SPECS_Component_Library.md
+└── M03_Authentication_System/
+    ├── M03_milestone_meta.md
+    ├── PRD_Authentication.md
+    └── SPECS_OAuth_Integration.md
+```
+
+## Important Notes for Claude Code
+
+1. **Always use the M## prefix** when creating milestone folders
+2. **Use underscores** for spaces in milestone names
+3. **Create the milestone meta file first** using the template from `99_TEMPLATES/milestone_meta_template.md`
+4. **Update the project manifest** (`00_PROJECT_MANIFEST.md`) when creating new milestones
+5. **Maintain sequential numbering** - don't skip milestone numbers
+
+## Common Mistakes to Avoid
+- Creating milestones without the M## prefix
+- Using hyphens instead of underscores
+- Forgetting the milestone meta file
+- Not updating the project manifest
+- Creating milestones in the wrong location (must be in 02_REQUIREMENTS)

package/claude-code/aiwf/ko/.aiwf/02_REQUIREMENTS/M01_Backend_Setup/M01_milestone_meta.md

@@ -0,0 +1,42 @@
+---
+milestone_id: M01
+title: Backend Setup
+status: active # pending | active | completed | blocked | on_hold
+last_updated: 2023-07-10
+---
+
+# Milestone: Backend Setup (EXAMPLE)
+
+## Goals
+
+This milestone focuses on establishing the core backend infrastructure for the project, including:
+
+1. Setting up the initial project structure
+2. Defining the database schema and models
+3. Implementing basic API endpoints
+4. Establishing authentication and authorization systems
+
+## Key Documents
+
+- [Product Requirements Document](./PRD_Backend_Setup.md)
+- [API Specifications V1](./SPECS_API_V1.md)
+- [Auth Flow Update Amendment](./PRD_AMEND_01_Auth_Flow_Update.md)
+
+## Definition of Done (DoD)
+
+This milestone will be considered complete when:
+
+- The backend server can be started and responds to API requests
+- All core models are defined and can be created/updated/deleted via the API
+- Authentication is working with JWT tokens
+- Basic error handling is implemented
+- Integration tests are passing for all endpoints
+
+## Notes / Context
+
+This is an example milestone document to demonstrate how milestones might be structured in a project using the AIWF framework. The backend infrastructure established here would be the foundation for a typical web application.
+
+## Related Sprints
+
+- [S01_M01_Initial_API](../../03_SPRINTS/S01_M01_Initial_API/S01_sprint_meta.md)
+- [S02_M01_Database_Integration](../../03_SPRINTS/S02_M01_Database_Integration/S02_sprint_meta.md)

package/claude-code/aiwf/ko/.aiwf/02_REQUIREMENTS/M01_Backend_Setup/PRD_AMEND_01_Auth_Flow_Update.md

@@ -0,0 +1,73 @@
+# Amendment: Auth Flow Update (EXAMPLE)
+
+## Date: 2023-05-17
+
+## Overview
+
+This amendment updates the authentication flow requirements to incorporate OAuth 2.0 support for social logins in addition to the existing email/password authentication.
+
+**Note: This is an example amendment document to demonstrate how requirement changes might be tracked in the AIWF framework.**
+
+## Changes to Product Requirements
+
+### User Management (FR-1)
+
+**Added Requirements:**
+
+- FR-1.6: The system shall allow users to register and log in using Google OAuth
+- FR-1.7: The system shall allow users to register and log in using GitHub OAuth
+- FR-1.8: The system shall link social login accounts with existing email accounts when the email matches
+
+### Data Models (FR-2)
+
+**Updated FR-2.1 (User model):**
+
+Add the following fields to the User model:
+
+- `oauth_provider`: string (null, 'google', 'github')
+- `oauth_id`: string (provider-specific user ID)
+
+### API Endpoints (FR-3)
+
+**Added Endpoints to FR-3.1:**
+
+- GET /api/auth/oauth/google (Redirect URL for Google OAuth)
+- GET /api/auth/oauth/github (Redirect URL for GitHub OAuth)
+- GET /api/auth/oauth/callback (OAuth provider callback)
+
+## Changes to Non-Functional Requirements
+
+**Updated NFR-5:**
+
+- NFR-5: The system shall implement JWT-based authentication with support for OAuth 2.0 providers
+
+**Added NFR:**
+
+- NFR-9: The system shall securely store OAuth provider credentials in environment variables
+
+## Implementation Impact
+
+- Required libraries: `passport`, `passport-google-oauth20`, `passport-github2`
+- Additional environment variables needed:
+  - `GOOGLE_CLIENT_ID`
+  - `GOOGLE_CLIENT_SECRET`
+  - `GITHUB_CLIENT_ID`
+  - `GITHUB_CLIENT_SECRET`
+  - `OAUTH_CALLBACK_URL`
+
+## Test Cases
+
+- TC-1: User can log in with Google account
+- TC-2: User can log in with GitHub account
+- TC-3: Social login with matching email links to existing account
+- TC-4: JWT token works correctly regardless of authentication method
+
+## Timeline Impact
+
+Implementation of these changes is expected to add 3 days to the original timeline.
+
+## Approvals
+
+- Requested by: Sarah Chen (Product Manager)
+- Approved by: Mike Johnson (Technical Lead)
+- Approved by: David Lee (Project Manager)

package/claude-code/aiwf/ko/.aiwf/02_REQUIREMENTS/M01_Backend_Setup/PRD_Backend_Setup.md

@@ -0,0 +1,98 @@
+# Product Requirements Document: Backend Setup
+
+## Overview
+
+This document outlines the requirements for setting up the backend infrastructure for our application. The backend will provide API endpoints for client applications, handle data persistence, and implement business logic.
+
+## Functional Requirements
+
+### User Management
+
+- FR-1.1: The system shall allow users to register with email and password
+- FR-1.2: The system shall allow users to log in with their credentials
+- FR-1.3: The system shall allow users to reset their password via email
+- FR-1.4: The system shall allow users to update their profile information
+- FR-1.5: The system shall allow administrators to disable user accounts
+
+### Data Models
+
+- FR-2.1: The system shall implement a User model with fields for:
+  - Email (unique)
+  - Password (hashed)
+  - Profile information (name, avatar, etc.)
+  - Role (user, admin)
+  - Account status (active, disabled)
+
+- FR-2.2: The system shall implement a Project model with fields for:
+  - Title
+  - Description
+  - Creation date
+  - Owner (User reference)
+  - Members (User references)
+  - Status (active, archived)
+
+- FR-2.3: The system shall implement a Task model with fields for:
+  - Title
+  - Description
+  - Due date
+  - Assigned user (User reference)
+  - Project (Project reference)
+  - Status (todo, in_progress, done)
+  - Priority (low, medium, high)
+
+### API Endpoints
+
+- FR-3.1: The system shall provide authentication endpoints:
+  - POST /api/auth/register
+  - POST /api/auth/login
+  - POST /api/auth/reset-password
+  - POST /api/auth/reset-password-confirm
+
+- FR-3.2: The system shall provide user management endpoints:
+  - GET /api/users/me
+  - PUT /api/users/me
+  - GET /api/users (admin only)
+  - PUT /api/users/:id (admin only)
+
+- FR-3.3: The system shall provide project management endpoints:
+  - GET /api/projects
+  - POST /api/projects
+  - GET /api/projects/:id
+  - PUT /api/projects/:id
+  - DELETE /api/projects/:id
+
+- FR-3.4: The system shall provide task management endpoints:
+  - GET /api/projects/:id/tasks
+  - POST /api/projects/:id/tasks
+  - GET /api/tasks/:id
+  - PUT /api/tasks/:id
+  - DELETE /api/tasks/:id
+
+## Non-Functional Requirements
+
+- NFR-1: The backend shall be implemented using Node.js and Express
+- NFR-2: The system shall use MongoDB for data persistence
+- NFR-3: API response time shall be under 200ms for 95% of requests
+- NFR-4: The system shall handle up to 1000 concurrent users
+- NFR-5: The system shall implement JWT-based authentication
+- NFR-6: All API endpoints shall be documented using OpenAPI/Swagger
+- NFR-7: The codebase shall have at least 80% test coverage
+- NFR-8: The system shall log all errors and API requests
+
+## Constraints
+
+- The backend must be deployable to AWS and Azure
+- The system must comply with GDPR requirements for user data
+- The API must be versioned to support future changes
+
+## Assumptions
+
+- The client applications will be responsible for input validation
+- The backend will be accessed only through the API, not directly
+- The database will be hosted on a managed service (MongoDB Atlas)
+
+## Dependencies
+
+- MongoDB Atlas account
+- SMTP service for email sending
+- JWT secret key management