multi-project-spec-mapper

# Multi-Project Spec Mapper - Intelligent Project Organization

**Purpose**: Automatically detect multiple projects in SpecWeave setup, analyze user stories to map them to the correct project (FE, BE, MOBILE, INFRA), and organize specs into project-specific folders with proper JIRA/GitHub sync.

**When to Use**:
- User has multiple JIRA projects configured (e.g., FE, BE, MOBILE)
- User has multiple GitHub repos to sync
- Brownfield projects with multiple teams/services
- Microservices architecture with separate frontend/backend/mobile codebases
- Need to split monolithic spec into project-specific specs

**Key Capabilities**:
1. ✅ **Intelligent Project Detection** - Analyze config.json to detect multi-project setup
2. ✅ **User Story Classification** - Map user stories to projects based on keywords, tech stack, components
3. ✅ **Spec Splitting** - Split monolithic specs into project-specific files
4. ✅ **Folder Organization** - Create `specs/FE/`, `specs/BE/`, `specs/MOBILE/` structure
5. ✅ **JIRA Item Type Mapping** - Suggest Epic/Story/Task hierarchy based on scope
6. ✅ **Bidirectional Sync** - Configure hooks for GitHub/JIRA sync per project

---

## How It Works

### Step 1: Detect Multi-Project Setup

**Check config.json** for:
```json
{
  "sync": {
    "profiles": {
      "jira-default": {
        "provider": "jira",
        "config": {
          "domain": "company.atlassian.net",
          "projects": ["FE", "BE", "MOBILE"]  // ← Multiple projects!
        }
      }
    }
  }
}
```

**If multiple projects found** → Activate multi-project mode

---

### Step 2: Analyze User Stories

For each user story, analyze:
- **Keywords**: "UI", "chart", "API", "mobile", "database", "deployment"
- **Tech Stack**: "React", "Node.js", "React Native", "PostgreSQL", "Kubernetes"
- **Components**: "component", "service", "screen", "controller", "pipeline"

**Example**:
```
US-001: Log a Workout (Web UI)
→ Keywords: "UI", "web", "chart"
→ Tech: "React"
→ Project: FE (90% confide