aiwf 0.3.7 → 0.3.12

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

@@ -1,78 +0,0 @@
-# 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/en/.aiwf/02_REQUIREMENTS/M01_Backend_Setup/M01_milestone_meta.md

@@ -1,42 +0,0 @@
----
-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/en/.aiwf/02_REQUIREMENTS/M01_Backend_Setup/PRD_AMEND_01_Auth_Flow_Update.md

@@ -1,73 +0,0 @@
-# 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/en/.aiwf/02_REQUIREMENTS/M01_Backend_Setup/PRD_Backend_Setup.md

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

package/claude-code/aiwf/en/.aiwf/02_REQUIREMENTS/M01_Backend_Setup/SPECS_API_V1.md

@@ -1,232 +0,0 @@
-# API Specifications V1
-
-This document provides detailed specifications for the API endpoints to be implemented in the backend.
-
-## Base URL
-
-All API endpoints are prefixed with: `/api/v1`
-
-## Authentication
-
-All authenticated endpoints require a valid JWT token in the Authorization header:
-
-```
-Authorization: Bearer <token>
-```
-
-## Error Handling
-
-All API endpoints follow a consistent error response format:
-
-```json
-{
-  "error": {
-    "code": "ERROR_CODE",
-    "message": "Human-readable error message",
-    "details": {} // Optional additional error details
-  }
-}
-```
-
-Common error codes:
-- `UNAUTHORIZED`: Authentication required or invalid
-- `FORBIDDEN`: Insufficient permissions
-- `NOT_FOUND`: Resource not found
-- `VALIDATION_ERROR`: Request validation failed
-- `INTERNAL_ERROR`: Server-side error
-
-## Endpoints
-
-### Authentication
-
-#### POST /api/v1/auth/register
-
-Register a new user.
-
-**Request:**
-```json
-{
-  "email": "user@example.com",
-  "password": "securepassword",
-  "name": "John Doe"
-}
-```
-
-**Response (201 Created):**
-```json
-{
-  "user": {
-    "id": "user123",
-    "email": "user@example.com",
-    "name": "John Doe",
-    "created_at": "2023-07-10T12:00:00Z"
-  },
-  "token": "jwt.token.here"
-}
-```
-
-#### POST /api/v1/auth/login
-
-Authenticate a user.
-
-**Request:**
-```json
-{
-  "email": "user@example.com",
-  "password": "securepassword"
-}
-```
-
-**Response (200 OK):**
-```json
-{
-  "user": {
-    "id": "user123",
-    "email": "user@example.com",
-    "name": "John Doe",
-    "created_at": "2023-07-10T12:00:00Z"
-  },
-  "token": "jwt.token.here"
-}
-```
-
-### Users
-
-#### GET /api/v1/users/me
-
-Get current authenticated user profile.
-
-**Response (200 OK):**
-```json
-{
-  "id": "user123",
-  "email": "user@example.com",
-  "name": "John Doe",
-  "created_at": "2023-07-10T12:00:00Z",
-  "role": "user",
-  "status": "active"
-}
-```
-
-#### PUT /api/v1/users/me
-
-Update current user profile.
-
-**Request:**
-```json
-{
-  "name": "John Smith",
-  "avatar_url": "https://example.com/avatar.jpg"
-}
-```
-
-**Response (200 OK):**
-```json
-{
-  "id": "user123",
-  "email": "user@example.com",
-  "name": "John Smith",
-  "avatar_url": "https://example.com/avatar.jpg",
-  "created_at": "2023-07-10T12:00:00Z",
-  "role": "user",
-  "status": "active"
-}
-```
-
-### Projects
-
-#### GET /api/v1/projects
-
-List all projects accessible to the authenticated user.
-
-**Query Parameters:**
-- `status` (optional): Filter by status (active, archived)
-- `limit` (optional): Maximum number of results (default: 20)
-- `offset` (optional): Pagination offset (default: 0)
-
-**Response (200 OK):**
-```json
-{
-  "total": 42,
-  "data": [
-    {
-      "id": "proj123",
-      "title": "Project Alpha",
-      "description": "This is project alpha",
-      "created_at": "2023-07-10T12:00:00Z",
-      "owner": {
-        "id": "user123",
-        "name": "John Doe"
-      },
-      "status": "active"
-    },
-    ...
-  ]
-}
-```
-
-#### POST /api/v1/projects
-
-Create a new project.
-
-**Request:**
-```json
-{
-  "title": "New Project",
-  "description": "Description of the project"
-}
-```
-
-**Response (201 Created):**
-```json
-{
-  "id": "proj456",
-  "title": "New Project",
-  "description": "Description of the project",
-  "created_at": "2023-07-15T14:30:00Z",
-  "owner": {
-    "id": "user123",
-    "name": "John Doe"
-  },
-  "status": "active"
-}
-```
-
-### Tasks
-
-#### GET /api/v1/projects/:projectId/tasks
-
-List tasks for a specific project.
-
-**Query Parameters:**
-- `status` (optional): Filter by status (todo, in_progress, done)
-- `assigned_to` (optional): Filter by assigned user ID
-- `limit` (optional): Maximum number of results (default: 50)
-- `offset` (optional): Pagination offset (default: 0)
-
-**Response (200 OK):**
-```json
-{
-  "total": 24,
-  "data": [
-    {
-      "id": "task123",
-      "title": "Implement login page",
-      "description": "Create the login page with email and password fields",
-      "due_date": "2023-08-01T00:00:00Z",
-      "status": "in_progress",
-      "priority": "high",
-      "assigned_to": {
-        "id": "user123",
-        "name": "John Doe"
-      },
-      "project_id": "proj123"
-    },
-    ...
-  ]
-}
-```
-
-## Rate Limiting
-
-API requests are rate-limited to 100 requests per minute per user. When the limit is exceeded, the API will respond with status code 429 (Too Many Requests).

package/claude-code/aiwf/en/.aiwf/03_SPRINTS/CLAUDE.md

@@ -1,83 +0,0 @@
-# Sprint Management Instructions
-
-## Important Section - Always read
-
-- When updating Tasks Logs (Output Log) always fetch current date and time first
-- Update Output Log after every Subtask
-- Always be truthful in Logs. If you cannot complete a task for technical reasons, just write it down. Don't lie!
-- Only mark lines as done if you could acctually progress them.
-- Update the task file after every completed subtask and check Acceptance criteria as well if successful.
-
-## Sprint Structure
-
-Sprints are organized by milestone and sequence:
-
-- Folders follow pattern: `S<NN>_M<NN>_<Focus_Area>/` where:
-  - `S<NN>` is the sprint sequence number
-  - `M<NN>` directly references the milestone ID this sprint belongs to
-  - `<Focus_Area>` describes the sprint's main focus
-- Each sprint has a meta file: `S<NN>_sprint_meta.md`
-- Tasks use pattern: `T<NN>_S<NN>_<Description>.md`
-
-## Sprint Meta Files
-
-Sprint meta files define sprint goals and track status:
-
-```yaml
----
-sprint_id: S01
-milestone_id: M01
-status: in_progress # planning | in_progress | review | complete
----
-```
-
-Update status as progress occurs:
-
-- planning → in_progress → review → complete
-
-Always use the template at `.AIWF/99_TEMPLATES/sprint_template.md` when creating new sprint meta files.
-
-## Sprint Tasks
-
-Tasks within a sprint follow a standard format:
-
-- Status progression: open → in_progress → pending_review → done
-- When completing a task:
-  - Ask for user confirmation
-  - Update status to "done"
-  - Rename file from T... to TX... (e.g., `TX01_S01_Task_Name.md`)
-  - Update Output Log with final entry
-  - If GitHub issue is linked, update issue status
-
-Always use the template at `.AIWF/99_TEMPLATES/task_template.md` when creating new sprint tasks.
-
-### GitHub Issue Integration
-
-When working with tasks that have GitHub issues:
-
-1. **Creating Issues**: Use `/project:aiwf:issue_create {task_id}` to create a GitHub issue from a task
-2. **Linking Issues**: Add `github_issue: #123` to task frontmatter
-3. **Status Updates**: Update issue status when task status changes
-4. **Commit Integration**: Include `fixes #123` or `relates to #456` in commit messages
-5. **Pull Requests**: Use `/project:aiwf:pr_create {task_id}` to create PR with issue linking
-
-## Working with Sprint Tasks
-
-When executing a sprint task:
-
-1. Analyze task's Acceptance Criteria and Subtasks
-2. Check if task has a linked GitHub issue (look for `github_issue` in frontmatter)
-3. Update status to "in_progress" and update GitHub issue if linked:
-   ```bash
-   gh issue comment {issue_number} --body "🚀 Task work has started."
-   gh issue edit {issue_number} --add-label "in-progress"
-   ```
-4. Log activities in the Output Log with timestamps after every Subtask(!)
-5. Mark subtasks as completed using [x] only when they are really completed. If you were not able to complete them, don't mark them and tell the user.
-6. Reference architectural guidelines when implementing technical solutions
-7. Ensure the task follows the structure from the task template
-8. When task is complete, update GitHub issue if linked:
-   ```bash
-   gh issue comment {issue_number} --body "✅ Task has been completed."
-   gh issue edit {issue_number} --remove-label "in-progress" --add-label "completed"
-   ```

package/claude-code/aiwf/en/.aiwf/03_SPRINTS/S01_M01_Initial_API/S01_sprint_meta.md

@@ -1,49 +0,0 @@
----
-sprint_folder_name: S01_M01_Initial_API
-sprint_sequence_id: S01
-milestone_id: M01
-title: Initial API Development
-status: active # pending | active | completed | aborted
-goal: Implement the foundational API structure including user authentication, basic project endpoints, and the initial database models.
-last_updated: 2023-07-15
----
-
-# Sprint: Initial API Development (S01) (EXAMPLE)
-
-## Sprint Goal
-
-Implement the foundational API structure including user authentication, basic project endpoints, and the initial database models.
-
-## Scope & Key Deliverables
-
-1. Set up the project structure with Express.js and MongoDB
-2. Implement user registration and authentication endpoints
-3. Create basic project and task models
-4. Implement core API endpoints for projects and tasks
-5. Set up automated testing infrastructure
-
-## Sprint Backlog
-
-- [T01_S01_Setup_Project_Structure](./T01_S01_Setup_Project_Structure.md)
-- [T02_S01_Define_User_Model](./T02_S01_Define_User_Model.md)
-- [T03_S01_Implement_Auth_Endpoints](./T03_S01_Implement_Auth_Endpoints.md)
-- [T04_S01_Define_Project_Model](./T04_S01_Define_Project_Model.md)
-- [T05_S01_Implement_Project_Endpoints](./T05_S01_Implement_Project_Endpoints.md)
-
-## Definition of Done (for the Sprint)
-
-The sprint will be considered complete when:
-
-- All sprint tasks are completed and meet their acceptance criteria
-- All implemented endpoints pass their test cases
-- API documentation is updated to reflect implemented endpoints
-- Code has been reviewed and merged to the development branch
-
-## Notes / Context
-
-This is an example sprint document to demonstrate how sprints might be structured in a project using the AIWF framework. This simulates what a typical initial API development sprint might look like.
-
-## Related Documents
-
-- [Milestone M01: Backend Setup](../../02_REQUIREMENTS/M01_Backend_Setup/M01_milestone_meta.md)
-- [API Specifications V1](../../02_REQUIREMENTS/M01_Backend_Setup/SPECS_API_V1.md)