specweave 0.9.0 → 0.9.1

package/README.md

@@ -184,6 +184,50 @@ Organize documentation by team, repo, or microservice:
 
 **[→ Multi-Project Setup Guide](https://spec-weave.com/docs/guides/multi-project-setup)**
 
+### 🔗 Issue Tracker Integration (v0.9.0+)
+
+**Strategy-based team mapping** adapts to your organization's structure:
+
+#### **GitHub - 3 Strategies**
+
+1. **Repository-per-team** (Most Common)
+   ```bash
+   GITHUB_STRATEGY=repository-per-team
+   GITHUB_REPOS=frontend-app,backend-api,mobile-app
+   ```
+   Best for: Microservices, independent deployments
+
+2. **Team-based** (Monorepo)
+   ```bash
+   GITHUB_STRATEGY=team-based
+   GITHUB_REPO=main-product
+   GITHUB_TEAMS=frontend-team,backend-team
+   ```
+   Best for: Monorepos (Nx, Turborepo, Lerna)
+
+3. **Team-multi-repo** (Platform Teams)
+   ```bash
+   GITHUB_STRATEGY=team-multi-repo
+   GITHUB_TEAM_REPO_MAPPING='{"platform-team":["api-gateway","auth"]}'
+   ```
+   Best for: Platform teams owning multiple services
+
+#### **Jira - 3 Strategies**
+
+1. **Project-per-team** - Separate projects for each team
+2. **Component-based** - One project with components
+3. **Board-based** - One project with filtered boards
+
+#### **Azure DevOps - Team-Based**
+
+Fixed hierarchy: Organization → Project (ONE) → Teams (multiple)
+```bash
+AZURE_DEVOPS_PROJECT=MyProject
+AZURE_DEVOPS_TEAMS=Frontend,Backend,Mobile
+```
+
+**[→ Complete Integration Guide](https://spec-weave.com/docs/integrations/issue-trackers)**
+
 ### 📦 Brownfield Import
 
 Import existing documentation from external sources:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specweave",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "description": "Spec-driven development framework for Claude Code. AI-native workflow with living documentation, intelligent agents, and multilingual support (9 languages). Enterprise-grade traceability with permanent specs and temporary increments.",
   "type": "module",
   "main": "dist/index.js",

package/plugins/specweave/skills/SKILLS-INDEX.md

@@ -77,7 +77,9 @@ Step 4: Execute → Follow the increment planning workflow
 
 #### specweave-detector
 
-**Description**: Detects SpecWeave context (.specweave/ directory exists) and provides workflow documentation. v0.3.8+ features PROACTIVE auto-detection - when in SpecWeave folder, product descriptions automatically trigger increment planning. Explicit slash commands still work (/specweave:increment, /specweave:do, /specweave:progress, /specweave:validate, /specweave:done, /specweave:sync-docs, /sync-github). Keywords slash commands, specweave commands, smart workflow, auto-detection, specweave folder.
+**Description**: Detects SpecWeave context (.specweave/ directory exists) and provides workflow documentation. Explains available slash commands and workflow. Keywords slash commands, /specweave:increment, /increment, /specweave:do, /specweave:progress, /specweave:validate, /specweave:done, specweave commands, workflow help, specweave folder.
+
+**Note**: Auto-detection of product descriptions is handled by the `project-kickstarter` skill.
 
 **Location**: `.claude/skills/specweave-detector/SKILL.md`
 

package/src/templates/.env.example

@@ -43,22 +43,88 @@ VERCEL_TOKEN=your-vercel-token-here
 # Integration Services
 # ===================================
 
-# GitHub (https://github.com/settings/tokens)
+# ============================================================================
+# ISSUE TRACKER INTEGRATIONS (with Strategy-Based Team Mapping)
+# ============================================================================
+
+# ----------------------------------------------------------------------------
+# GitHub - 3 Strategies for Team Organization
+# ----------------------------------------------------------------------------
+# Guide: https://github.com/settings/tokens
 # Scopes: repo, read:org, workflow
-GITHUB_TOKEN=ghp_your-github-token-40-chars
 
-# JIRA (https://id.atlassian.com/manage-profile/security/api-tokens)
+# Required for all strategies:
+GH_TOKEN=ghp_your-github-token-40-chars
+
+# Strategy 1: Repository-per-team (MOST COMMON)
+# Use when: Each team has separate repositories (microservices, multi-repo)
+# Example: Frontend team → frontend-app, Backend team → backend-api
+GITHUB_STRATEGY=repository-per-team
+GITHUB_OWNER=myorg
+GITHUB_REPOS=frontend-app,backend-api,mobile-app,qa-tools
+
+# Strategy 2: Team-based (MONOREPO)
+# Use when: Single repository with team-based filtering
+# Example: Monorepo with teams working on different parts
+# GITHUB_STRATEGY=team-based
+# GITHUB_OWNER=myorg
+# GITHUB_REPO=main-product
+# GITHUB_TEAMS=frontend-team,backend-team,mobile-team,qa-team
+
+# Strategy 3: Team-multi-repo (COMPLEX)
+# Use when: Teams own multiple repositories (platform teams)
+# Example: Platform team owns api-gateway + auth-service
+# GITHUB_STRATEGY=team-multi-repo
+# GITHUB_OWNER=myorg
+# GITHUB_TEAM_REPO_MAPPING='{"platform-team":["api-gateway","auth-service"],"frontend-team":["web-app","mobile-app"]}'
+
+# ----------------------------------------------------------------------------
+# Jira - 3 Strategies for Team Organization
+# ----------------------------------------------------------------------------
+# Guide: https://id.atlassian.com/manage-profile/security/api-tokens
+
+# Required for all strategies:
 JIRA_API_TOKEN=your-jira-api-token
 JIRA_EMAIL=your-email@example.com
 JIRA_DOMAIN=your-domain.atlassian.net
 
-# Azure DevOps (https://dev.azure.com/)
-# Navigate to: User Settings → Personal Access Tokens
+# Strategy 1: Project-per-team (SEPARATE PROJECTS)
+# Use when: Each team has its own Jira project
+# Example: FRONTEND project, BACKEND project, MOBILE project
+JIRA_STRATEGY=project-per-team
+JIRA_PROJECTS=FRONTEND,BACKEND,MOBILE,QA
+
+# Strategy 2: Component-based (ONE PROJECT, MULTIPLE COMPONENTS)
+# Use when: Single project with components representing teams
+# Example: MAIN project with Frontend, Backend, Mobile components
+# JIRA_STRATEGY=component-based
+# JIRA_PROJECT=MAIN
+# JIRA_COMPONENTS=Frontend,Backend,Mobile,QA
+
+# Strategy 3: Board-based (ONE PROJECT, FILTERED BOARDS)
+# Use when: Single project with board filters for teams
+# Example: MAIN project with Frontend Board (123), Backend Board (456)
+# JIRA_STRATEGY=board-based
+# JIRA_PROJECT=MAIN
+# JIRA_BOARDS=123,456,789,101
+
+# ----------------------------------------------------------------------------
+# Azure DevOps - Team-Based Structure (ONE PROJECT, MULTIPLE TEAMS)
+# ----------------------------------------------------------------------------
+# Guide: https://dev.azure.com/ → User Settings → Personal Access Tokens
 # Scopes: Work Items (Read, Write), Code (Read)
+
+# Azure DevOps structure: Organization → Project (ONE) → Teams (multiple)
 AZURE_DEVOPS_PAT=your-ado-personal-access-token-52-chars-base64
 AZURE_DEVOPS_ORG=your-organization-name
 AZURE_DEVOPS_PROJECT=your-project-name
 
+# Multiple teams within the project (comma-separated):
+AZURE_DEVOPS_TEAMS=Frontend,Backend,Mobile,QA
+
+# Single team (legacy, backward compatible):
+# AZURE_DEVOPS_TEAM=Frontend
+
 # Figma (https://www.figma.com/developers/api#authentication)
 # Navigate to: Settings → Account → Personal Access Tokens
 FIGMA_ACCESS_TOKEN=figd_your-figma-token