aiwf 0.1.0 → 0.3.0

package/README.md

@@ -1,30 +1,33 @@
-[Read in Korean (한국어로 보기)](README.ko.md)
+# AIWF (AI Workflow Framework)
 
-# aiwf
+[Read in Korean (한국어로 보기)](README.ko.md)
 
-This project is an updated version of [Simone](https://github.com/Helmi/claude-simone).
+[![NPM Version](https://img.shields.io/npm/v/aiwf.svg)](https://www.npmjs.com/package/aiwf)
+[![License](https://img.shields.io/npm/l/aiwf.svg)](https://github.com/aiwf/aiwf/blob/main/LICENSE)
+[![Downloads](https://img.shields.io/npm/dm/aiwf.svg)](https://www.npmjs.com/package/aiwf)
 
-> 🚀 Quick installer for the Moonklabs project management framework for Claude Code
+## What is AIWF?
 
-## What is Moonklabs?
+AIWF is a markdown-based project management framework designed specifically for AI-assisted development with Claude Code. It helps break down software projects into manageable units that AI can effectively handle, maximizing productivity.
 
-Moonklabs is a markdown-based project management framework designed specifically for AI-assisted development with Claude Code. It helps break down software projects into manageable chunks for effective AI handling.
+This project is an updated version of [Simone](https://github.com/Helmi/claude-simone).
 
-## Installation
+## 📦 Installation
 
-Install Moonklabs in any project directory:
+Install AIWF in any project directory:
 
 ```bash
 npx aiwf
 ```
 
-That's it! The installer will:
+The installer will:
 
-- Create the `.moonklabs/` directory structure for project management
-- Set up `.claude/commands/moonklabs/` for custom Claude commands
-- Download the latest templates and documentation
+1. **Language Selection**: Choose between English and Korean
+2. **Directory Setup**: Create the `.aiwf/` directory structure for project management
+3. **Commands**: Set up `.claude/commands/aiwf/` with localized Claude commands
+4. **Content**: Download the latest templates and documentation in your selected language
 
-## Usage
+## 🚀 Usage
 
 ### First Time Installation
 
@@ -34,7 +37,7 @@ npx aiwf
 
 ### Update Existing Installation
 
-If Moonklabs is already installed, the installer will detect it and offer options to:
+If AIWF is already installed, the installer will automatically detect it and offer options to:
 
 - Update (with automatic backup)
 - Skip installation
@@ -42,76 +45,100 @@ If Moonklabs is already installed, the installer will detect it and offer option
 
 ### Force Installation
 
-Skip all prompts and force installation:
+Skip all prompts and force installation (defaults to English):
 
 ```bash
 npx aiwf --force
 ```
 
-## What Gets Installed
+### Language-Specific Installation
 
-```
-aiwf/
-├── AI-WORKFLOW.md
-├── CHANGELOG.md
-├── claude-code/
-│   ├── docker/
-│   │   └── Dockerfile
-│   ├── moonklabs/
-│   └── simone/
-│       ├── CHANGELOG.md
-│       ├── LICENSE
-│       ├── README.md
-│       ├── SYNC_GUIDE.md
-│       └── sync-simone.sh
-├── COMMANDS_GUIDE.md
-├── LICENSE
-├── package-lock.json
-├── package.json
-├── PRD.ko.md
-├── PRD.md
-├── README.ko.md
-├── README.md
-└── rules/
-    ├── global/
-    │   ├── code-style-guide.md
-    │   ├── coding-principles.md
-    │   ├── development-process.md
-    │   └── global-rules.md
-    └── manual/
-        └── generate-plan-docs.md
+The installer automatically selects the appropriate language version based on your choice:
+
+- English version: English commands and documentation (default)
+- Korean version: Korean commands and documentation
+
+## 📁 What Gets Installed
+
+### Directory Structure
+
+```text
+your_project/
+├── .aiwf/                        # Project management root
+│   ├── 00_PROJECT_MANIFEST.md    # Central tracking document
+│   ├── 01_PROJECT_DOCS/          # Project documentation
+│   ├── 02_REQUIREMENTS/          # Milestone requirements
+│   ├── 03_SPRINTS/              # Sprint execution tracking
+│   ├── 04_GENERAL_TASKS/        # Standalone tasks
+│   ├── 05_ARCHITECTURE_DECISIONS/ # ADR documents
+│   ├── 10_STATE_OF_PROJECT/     # Project state snapshots
+│   ├── 98_PROMPTS/              # Useful AI prompts
+│   └── 99_TEMPLATES/            # Document templates
+├── .claude/commands/aiwf/       # Language-specific Claude commands
+├── .cursor/rules/               # Cursor IDE development rules
+└── .windsurf/rules/             # Windsurf IDE development rules
 ```
 
-## Next Steps
+### Language-Specific Content
+
+Based on your language selection, you'll get:
+
+**English Version (`en/`)** (Default):
+
+- English Claude commands
+- English documentation and templates
+- Standard project management content
+
+**Korean Version (`ko/`)**:
+
+- Korean Claude commands (with `_kr` suffix available)
+- Korean documentation and templates
+- Localized project management content
+
+## 🎯 Getting Started
 
 After installation:
 
 1. Open your project in Claude Code
-2. Use `/project:moonklabs` commands to manage your project
-3. Start with `/project:moonklabs:initialize` to set up your project
+2. Use `/project:aiwf` commands to manage your project
+3. Start with `/project:aiwf:initialize` to set up your project
+
+### Key Commands
+
+- **Initialize**: `/project:aiwf:initialize` - Initial project setup
+- **Plan**: `/project:aiwf:plan_milestone` - Create milestone plans
+- **Sprint**: `/project:aiwf:create_sprints_from_milestone` - Generate sprints
+- **Task**: `/project:aiwf:do_task` - Execute tasks
+- **Review**: `/project:aiwf:code_review` - Code review
+- **GitHub Integration**: `/project:aiwf:issue_create`, `/project:aiwf:pr_create`
 
-## Command Reference
+## 📚 Documentation
 
-For a full list of available Moonklabs commands and detailed usage, see [COMMANDS_GUIDE.md](COMMANDS_GUIDE.md).
+For a complete list of AIWF commands and detailed usage, see [COMMANDS_GUIDE.md](docs/COMMANDS_GUIDE.md).
 
-## Features
+## ✨ Features
 
-- 🎨 Beautiful CLI with colors and progress indicators
-- 🔄 Smart update detection with automatic backups
-- 📦 Downloads directly from the official GitHub repository
-- 🚀 Works with `npx` - no global installation needed
-- 💾 Creates timestamped backups when updating
+- 🌍 **Multi-language Support** - Complete English and Korean support
+- 🎨 **Beautiful CLI** - User-friendly interface with colors and progress indicators
+- 🔄 **Smart Updates** - Intelligent update detection with automatic backups
+- 📦 **Direct Download** - Downloads directly from official GitHub repository
+- 🚀 **Easy to Use** - Works with `npx` - no global installation needed
+- 💾 **Safe Backups** - Creates timestamped backups when updating
+- 🎯 **Language-Specific** - Language-specific commands and documentation
+- 🔧 **IDE Integration** - Cursor and Windsurf development rules support
+- 🔗 **GitHub Integration** - Automated issue and PR creation
+- 📊 **Project Tracking** - Systematic management of milestones, sprints, and tasks
 
-## Requirements
+## 🔧 Requirements
 
 - Node.js 14.0.0 or higher
 - Internet connection to download from GitHub
 
-## Source
+## 📖 Source
 
-This installer fetches the Moonklabs framework from:
-https://github.com/moonklabs/aiwf
+This installer fetches the AIWF framework from:
+<https://github.com/aiwf/aiwf>
 
-## License
+## 📝 License
 
 MIT

package/claude-code/{simone/.simone → aiwf/en/.aiwf}/01_PROJECT_DOCS/ARCHITECTURE.md

@@ -1,6 +1,6 @@
 # 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 Simone framework.**
+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
 

package/claude-code/{simone/.simone → aiwf/en/.aiwf}/02_REQUIREMENTS/M01_Backend_Setup/M01_milestone_meta.md

@@ -8,6 +8,7 @@ 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
@@ -16,11 +17,13 @@ This milestone focuses on establishing the core backend infrastructure for the p
 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
@@ -30,7 +33,8 @@ This milestone will be considered complete when:
 - 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 Simone framework. The backend infrastructure established here would be the foundation for a typical web application.
+
+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
 

package/claude-code/{simone/.simone → aiwf/en/.aiwf}/02_REQUIREMENTS/M01_Backend_Setup/PRD_AMEND_01_Auth_Flow_Update.md

@@ -6,7 +6,7 @@
 
 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 Simone framework.**
+**Note: This is an example amendment document to demonstrate how requirement changes might be tracked in the AIWF framework.**
 
 ## Changes to Product Requirements
 
@@ -23,12 +23,14 @@ This amendment updates the authentication flow requirements to incorporate OAuth
 **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)
@@ -36,9 +38,11 @@ Add the following fields to the User model:
 ## 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

package/claude-code/{simone/.simone/03_SPRINTS/CLAUDE.MD → aiwf/en/.aiwf/03_SPRINTS/CLAUDE.md}

@@ -35,7 +35,7 @@ Update status as progress occurs:
 
 - planning → in_progress → review → complete
 
-Always use the template at `.simone/99_TEMPLATES/sprint_template.md` when creating new sprint meta files.
+Always use the template at `.AIWF/99_TEMPLATES/sprint_template.md` when creating new sprint meta files.
 
 ## Sprint Tasks
 
@@ -47,16 +47,37 @@ Tasks within a sprint follow a standard format:
   - 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 `.simone/99_TEMPLATES/task_template.md` when creating new sprint tasks.
+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. Update status to "in_progress"
-3. Log activities in the Output Log with timestamps after every Subtask(!)
-4. 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.
-5. Reference architectural guidelines when implementing technical solutions
-6. Ensure the task follows the structure from the task template
+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/{simone/.simone → aiwf/en/.aiwf}/03_SPRINTS/S01_M01_Initial_API/S01_sprint_meta.md

@@ -11,9 +11,11 @@ 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
@@ -21,6 +23,7 @@ Implement the foundational API structure including user authentication, basic pr
 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)
@@ -28,15 +31,19 @@ Implement the foundational API structure including user authentication, basic pr
 - [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 Simone framework. This simulates what a typical initial API development sprint might look like.
+
+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)

package/claude-code/{simone/.simone → aiwf/en/.aiwf}/03_SPRINTS/S01_M01_Initial_API/T01_S01_Setup_Project_Structure.md

@@ -9,11 +9,13 @@ last_updated: 2023-07-15
 # Task: Setup Project Structure (EXAMPLE)
 
 ## Description
+
 Set up the initial project structure for the backend API service, including directory organization, dependency installation, and basic configuration.
 
-**Note: This is an example task to demonstrate the structure of a task in the Simone framework.**
+**Note: This is an example task to demonstrate the structure of a task in the AIWF framework.**
 
 ## Goal / Objectives
+
 - Create a well-organized, scalable project structure
 - Set up the Express.js application with middleware
 - Configure MongoDB connection
@@ -22,6 +24,7 @@ Set up the initial project structure for the backend API service, including dire
 - Initialize logging system
 
 ## Acceptance Criteria
+
 - [ ] Project structure follows MVC pattern with clear separation of concerns
 - [ ] Express application is set up with necessary middleware (CORS, body-parser, etc.)
 - [ ] MongoDB connection is configured with error handling
@@ -32,6 +35,7 @@ Set up the initial project structure for the backend API service, including dire
 - [ ] Initial tests pass
 
 ## Subtasks
+
 - [ ] Initialize Node.js project with package.json
 - [ ] Install core dependencies (express, mongoose, dotenv, etc.)
 - [ ] Create directory structure for routes, controllers, models, middleware

package/claude-code/aiwf/en/.aiwf/04_GENERAL_TASKS/CLAUDE.md

@@ -0,0 +1,96 @@
+# General Tasks Instructions
+
+## General Task Structure
+
+General tasks are standalone work items not tied to sprints:
+
+- Files follow pattern: `T<NNN>_<Description>.md`
+- Completed tasks: `TX<NNN>_<Description>.md`
+
+Always use the template at `.AIWF/99_TEMPLATES/task_template.md` when creating new general tasks.
+
+## Task Formatting
+
+General tasks use standardized YAML frontmatter and sections:
+
+```yaml
+---
+task_id: T001
+status: open # open | in_progress | pending_review | done | failed | blocked
+complexity: Medium # Low | Medium | High
+last_updated: YYYY-MM-DD HH:MM
+github_issue: #123 # Optional: Link to GitHub issue
+---
+```
+
+The full task structure with all sections is defined in the task template. Always maintain this structure.
+
+## Working with General Tasks
+
+When handling general tasks:
+
+1. Check if task has a linked GitHub issue (look for `github_issue` in frontmatter)
+2. Update the status field as you progress
+3. If GitHub issue is linked, update it when starting:
+   ```bash
+   gh issue comment {issue_number} --body "🚀 Task work has started."
+   gh issue edit {issue_number} --add-label "in-progress"
+   ```
+4. Record timestamps in this format (YYYY-MM-DD HH:MM)
+5. Log all significant actions in the Output Log section:
+
+   ```plaintext
+   [YYYY-MM-DD HH:MM] Started task
+   [YYYY-MM-DD HH:MM] Modified files: file1.js, file2.js
+   ```
+
+6. Mark subtasks as they're completed: `- [x] Completed subtask`
+7. Use the Acceptance Criteria as your primary completion checklist
+8. Ensure all sections from the task template are preserved
+
+## Task Completion Process
+
+When a task is complete:
+
+1. Update status to "done"
+2. Update all Acceptance Criteria with [x]
+3. Add final Output Log entry
+4. If GitHub issue is linked, update it:
+   ```bash
+   gh issue comment {issue_number} --body "✅ Task has been completed."
+   gh issue edit {issue_number} --remove-label "in-progress" --add-label "completed"
+   ```
+5. Rename file from T... to TX... (e.g., `TX001_Task_Name.md`)
+
+## GitHub Integration
+
+### Creating Issues from Tasks
+
+To create a GitHub issue from a general task:
+
+```bash
+/project:aiwf:issue_create {task_id}
+```
+
+### Linking Existing Issues
+
+Add to task frontmatter:
+
+```yaml
+github_issue: #123
+```
+
+### Commit Integration
+
+When committing changes for a task with a linked issue:
+
+- Use `fixes #123` to auto-close the issue
+- Use `relates to #123` to reference without closing
+
+### Pull Request Creation
+
+After task completion, create a PR:
+
+```bash
+/project:aiwf:pr_create {task_id}
+```

package/claude-code/{simone/.simone → aiwf/en/.aiwf}/04_GENERAL_TASKS/T002_API_Rate_Limiting.md

@@ -8,11 +8,13 @@ last_updated: 2023-07-25T09:15:00Z
 # Task: API Rate Limiting (EXAMPLE)
 
 ## Description
+
 Implement rate limiting for the API to prevent abuse and ensure fair usage across all clients. This task involves adding middleware to track and limit requests based on client IP or API key.
 
-**Note: This is an example general task to demonstrate how non-sprint-specific tasks might be structured in the Simone framework.**
+**Note: This is an example general task to demonstrate how non-sprint-specific tasks might be structured in the AIWF framework.**
 
 ## Goal / Objectives
+
 - Protect API endpoints from abuse and excessive requests
 - Implement configurable rate limits based on client authentication
 - Track usage statistics for billing and monitoring
@@ -20,6 +22,7 @@ Implement rate limiting for the API to prevent abuse and ensure fair usage acros
 - Ensure minimal performance impact on normal API operation
 
 ## Acceptance Criteria
+
 - [ ] Rate limiting is applied to all public API endpoints
 - [ ] Different rate limits are configurable based on client tier/authentication
 - [ ] Response headers include rate limit information (limit, remaining, reset)
@@ -29,6 +32,7 @@ Implement rate limiting for the API to prevent abuse and ensure fair usage acros
 - [ ] Usage statistics are collected for monitoring and analysis
 
 ## Subtasks
+
 - [x] Research rate limiting strategies and best practices
 - [x] Evaluate libraries (express-rate-limit, rate-limiter-flexible, etc.)
 - [x] Design rate limit tiers for different client types
@@ -40,7 +44,8 @@ Implement rate limiting for the API to prevent abuse and ensure fair usage acros
 - [ ] Document rate limiting behavior for API consumers
 
 ## Output Log
-*(This section is populated as work progresses on the task)*
+
+_(This section is populated as work progresses on the task)_
 
 [2023-07-23 10:30:00] Started task
 [2023-07-23 13:45:22] Completed research on rate limiting strategies

package/claude-code/{simone/.simone → aiwf/en/.aiwf}/04_GENERAL_TASKS/TX001_Refactor_Logging_Module.md

@@ -8,11 +8,13 @@ last_updated: 2023-07-22T16:45:00Z
 # Task: Refactor Logging Module (EXAMPLE)
 
 ## Description
+
 The current logging implementation is basic and needs to be enhanced to provide better visibility and monitoring capabilities. This task involves refactoring the logging module to add structured logging, log rotation, and improved error tracking.
 
-**Note: This is an example general task to demonstrate how non-sprint-specific tasks might be structured in the Simone framework.**
+**Note: This is an example general task to demonstrate how non-sprint-specific tasks might be structured in the AIWF framework.**
 
 ## Goal / Objectives
+
 - Implement structured JSON logging for better parsing by log analysis tools
 - Add log rotation to prevent log files from growing too large
 - Enable different log levels based on environment
@@ -20,6 +22,7 @@ The current logging implementation is basic and needs to be enhanced to provide
 - Improve error logging with stack traces and contextual information
 
 ## Acceptance Criteria
+
 - [x] Logs are output in structured JSON format
 - [x] Log files are rotated based on size and/or date
 - [x] Different log levels are used appropriately (debug, info, warn, error)
@@ -29,6 +32,7 @@ The current logging implementation is basic and needs to be enhanced to provide
 - [x] Documentation is updated to reflect new logging capabilities
 
 ## Subtasks
+
 - [x] Evaluate and select appropriate logging libraries and tools
 - [x] Design the structured log format with required fields
 - [x] Implement log rotation configuration
@@ -39,7 +43,8 @@ The current logging implementation is basic and needs to be enhanced to provide
 - [x] Document the new logging system
 
 ## Output Log
-*(This section is populated as work progresses on the task)*
+
+_(This section is populated as work progresses on the task)_
 
 [2023-07-15 10:30:00] Started task
 [2023-07-15 11:15:22] Researched logging libraries: winston, pino, bunyan

package/claude-code/{simone/.simone → aiwf/en/.aiwf}/05_ARCHITECTURAL_DECISIONS/ADR001_Chosen_Database_System.md

@@ -12,9 +12,10 @@ Accepted
 
 The backend system needs a database to store user accounts, projects, tasks, and other application data. The choice of database system will impact performance, scalability, development speed, and maintenance requirements.
 
-**Note: This is an example Architecture Decision Record to demonstrate how ADRs might be structured in the Simone framework.**
+**Note: This is an example Architecture Decision Record to demonstrate how ADRs might be structured in the AIWF framework.**
 
 We evaluated several options including:
+
 - Relational databases (PostgreSQL, MySQL)
 - Document databases (MongoDB, CouchDB)
 - Key-value stores (Redis, DynamoDB)
@@ -40,6 +41,7 @@ The decision was based on the following factors:
 6. **Ecosystem**: The robust Node.js ecosystem around MongoDB with libraries like Mongoose provides tools for validation, middleware, and other features that align with our development approach.
 
 Some concerns were raised about:
+
 - Lack of ACID transactions across multiple documents (though MongoDB does support multi-document transactions now)
 - Potential for data duplication in document model
 
@@ -50,11 +52,13 @@ We determined these concerns were manageable for our use case and outweighed by
 ### PostgreSQL
 
 Pros:
+
 - Mature, proven technology with strong ACID compliance
 - Excellent for complex relational data and joins
 - Support for JSON data types provides some schema flexibility
 
 Cons:
+
 - Schema migrations could slow development velocity
 - Object-relational mapping adds complexity
 - Less natural fit for our document-oriented data model
@@ -62,11 +66,13 @@ Cons:
 ### DynamoDB
 
 Pros:
+
 - Fully managed service with automatic scaling
 - Predictable performance with guaranteed low-latency
 - Strong consistency options
 
 Cons:
+
 - Less flexible query capabilities
 - AWS lock-in
 - Potentially higher cost for our access patterns