Intelligent multi-project specification splitting and organization. Analyzes user stories to map them to correct projects (FE, BE, MOBILE, INFRA) based on content, tech stack, and component architecture. Creates project-specific folder structure and splits monolithic specs. Activates for multi-project JIRA/GitHub setups, brownfield projects with multiple teams, microservices architecture. Keywords: multi-project, project mapping, spec splitting, JIRA projects, multiple projects, microservices, FE/BE/MOBILE split, intelligent classification.
Intelligent multi-project specification splitting and organization. Analyzes user stories to map them to correct projects (FE, BE, MOBILE, INFRA) based on content, tech stack, and component architecture. Activates for multi-project JIRA/GitHub setups, brownfield projects with multiple teams, microservices architecture.
/plugin marketplace add anton-abyzov/specweave/plugin install sw@specweaveThis skill inherits all available tools. When active, it can use any tool Claude has access to.
MEMORY.mdPurpose: 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:
Key Capabilities:
specs/FE/, specs/BE/, specs/MOBILE/ structureCheck config.json for:
{
"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
For each user story, analyze:
Example:
US-001: Log a Workout (Web UI)
→ Keywords: "UI", "web", "chart"
→ Tech: "React"
→ Project: FE (90% confidence)
US-002: View Workout History (API)
→ Keywords: "API", "endpoint", "database"
→ Tech: "Node.js", "PostgreSQL"
→ Project: BE (95% confidence)
US-005: Cross-Platform Data Sync (Mobile)
→ Keywords: "mobile", "offline", "sync"
→ Tech: "React Native"
→ Project: MOBILE (100% confidence)
Folder Structure:
.specweave/docs/internal/specs/
├── FE/
│ ├── spec-0001-fitness-tracker-web.md
│ └── README.md
├── BE/
│ ├── spec-0001-fitness-tracker-api.md
│ └── README.md
├── MOBILE/
│ ├── spec-0001-fitness-tracker-mobile.md
│ └── README.md
└── SHARED/
├── spec-0001-fitness-tracker-shared.md (cross-cutting concerns)
└── README.md
spec.md YAML Frontmatter (v0.31.0+ MANDATORY):
# For 1-level structure (projects only)
---
increment: 0001-fitness-tracker-web
project: FE # REQUIRED
title: "Fitness Tracker Web UI"
status: planned
---
# For 2-level structure (projects + boards)
---
increment: 0001-fitness-tracker-web
project: acme-corp # REQUIRED
board: digital-operations # REQUIRED for 2-level
title: "Fitness Tracker Web UI"
status: planned
---
Detection: Use detectStructureLevel() from src/utils/structure-level-detector.ts
Each spec contains:
project: (and board: for 2-level) fields - MANDATORYHierarchical JIRA Structure:
JIRA Project: FE
├── Epic: Fitness Tracker Web UI (SPEC-0001)
│ ├── Story: US-001: Log a Workout
│ │ ├── Task: T-001: Create Workout Form Component
│ │ ├── Task: T-002: Implement Exercise Search
│ │ └── Task: T-003: Add Set Logging UI
│ └── Story: US-004: Track Progress with Charts
│ ├── Task: T-010: Integrate Recharts Library
│ └── Task: T-011: Create Chart Components
JIRA Project: BE
├── Epic: Fitness Tracker API Backend (SPEC-0001)
│ ├── Story: US-002: View Workout History (API)
│ │ ├── Task: T-004: Create GET /api/workouts Endpoint
│ │ ├── Task: T-005: Implement Filtering Logic
│ │ └── Task: T-006: Add Pagination
│ └── Story: US-003: Manage Exercise Library (API)
│ ├── Task: T-007: Create Exercise CRUD Endpoints
│ └── Task: T-008: Implement Search
JIRA Project: MOBILE
├── Epic: Fitness Tracker Mobile App (SPEC-0001)
└── Story: US-005: Cross-Platform Data Sync
├── Task: T-012: Implement Offline Mode (AsyncStorage)
├── Task: T-013: Create Sync Queue
└── Task: T-014: Handle Conflict Resolution
GitHub Hooks (.specweave/config.json):
{
"hooks": {
"post_task_completion": {
"sync_living_docs": true,
"external_tracker_sync": true
}
},
"sync": {
"enabled": true,
"activeProfile": "jira-default",
"settings": {
"autoCreateIssue": true,
"syncDirection": "bidirectional",
"projectMapping": {
"FE": {
"jiraProject": "FE",
"jiraBoards": [123],
"githubRepo": "company/frontend-web"
},
"BE": {
"jiraProject": "BE",
"jiraBoards": [456],
"githubRepo": "company/backend-api"
},
"MOBILE": {
"jiraProject": "MOBILE",
"jiraBoards": [789],
"githubRepo": "company/mobile-app"
}
}
}
}
}
Keywords:
Tech Stack:
Components:
Confidence: 30%+ for primary match
Keywords:
Tech Stack:
Components:
Confidence: 30%+ for primary match
Keywords:
Tech Stack:
Components:
Exclude: "web" keyword (penalty)
Confidence: 30%+ for primary match
Keywords:
Tech Stack:
Components:
Confidence: 30%+ for primary match
Epic (> 13 story points):
Story (3-13 story points):
Task (1-2 story points):
Subtask (< 1 story point):
Input: Monolithic spec with 35 user stories
Detection:
✓ Multi-project setup detected:
- FE (Frontend Web)
- BE (Backend API)
- MOBILE (React Native)
Classification:
Analyzing 35 user stories...
✓ US-001: Log a Workout → FE (90% confidence: React, UI, chart)
✓ US-002: View Workout History → BE (95% confidence: API, database, query)
✓ US-004: Track Progress with Charts → FE (100% confidence: Recharts, visualization)
✓ US-005: Cross-Platform Data Sync → MOBILE (100% confidence: React Native, offline)
Project Distribution:
- FE: 12 user stories (34%)
- BE: 15 user stories (43%)
- MOBILE: 6 user stories (17%)
- SHARED: 2 user stories (6%)
Output:
Creating project-specific specs...
✓ specs/FE/spec-0001-fitness-tracker-web.md (12 user stories)
✓ specs/BE/spec-0001-fitness-tracker-api.md (15 user stories)
✓ specs/MOBILE/spec-0001-fitness-tracker-mobile.md (6 user stories)
✓ specs/SHARED/spec-0001-fitness-tracker-shared.md (2 user stories)
JIRA Sync Configuration:
✓ FE → JIRA Project FE (Board 123)
✓ BE → JIRA Project BE (Board 456)
✓ MOBILE → JIRA Project MOBILE (Board 789)
Input: Spec for multi-service platform
Detection:
✓ Multi-project setup detected:
- FRONTEND (Web storefront)
- PRODUCT-SVC (Product service)
- ORDER-SVC (Order service)
- PAYMENT-SVC (Payment service)
- INFRA (Kubernetes + monitoring)
Classification:
Analyzing 50 user stories...
✓ US-010: Product Catalog UI → FRONTEND (95%)
✓ US-011: Product Search API → PRODUCT-SVC (100%)
✓ US-020: Shopping Cart → ORDER-SVC (90%)
✓ US-030: Stripe Integration → PAYMENT-SVC (100%)
✓ US-040: Kubernetes Deployment → INFRA (100%)
Project Distribution:
- FRONTEND: 15 user stories
- PRODUCT-SVC: 12 user stories
- ORDER-SVC: 10 user stories
- PAYMENT-SVC: 8 user stories
- INFRA: 5 user stories
Enable Multi-Project Mode in .specweave/config.json:
{
"multiProject": {
"enabled": true,
"autoDetect": true,
"customRules": {
"FE": {
"keywords": ["react", "ui", "chart"],
"techStack": ["react", "typescript", "recharts"],
"confidenceThreshold": 0.3
}
}
}
}
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.