specweave 1.0.593 → 2.0.3

package/plugins/specweave/skills/jira-sync/README.md

@@ -1,291 +0,0 @@
-# jira-sync Skill
-
-**Status**: To be developed
-**Priority**: Medium
-
-## Purpose
-
-Bidirectional sync between SpecWeave increments and JIRA (Atlassian)
-
-**Note**: This skill handles ONLY JIRA. For Azure DevOps, see `ado-sync` skill.
-
-## Features
-
-### Export to JIRA
-- Create JIRA issues from SpecWeave increments
-- Map spec.md user stories → JIRA Stories
-- Map tasks.md tasks → JIRA Sub-tasks
-- Create Epics if specified in spec.md
-- Set priorities, labels, components
-
-### Import from JIRA
-- Sync JIRA updates back to SpecWeave
-- Import existing JIRA issues as increments
-- Update status, assignees, comments
-
-### Bidirectional Sync
-- Keep status in sync (To Do, In Progress, Done)
-- Sync descriptions and acceptance criteria
-- Sync comments
-- Handle conflicts intelligently
-
-## JIRA-Specific Concepts
-
-### Mapping: SpecWeave → JIRA
-
-| SpecWeave | JIRA |
-|-----------|------|
-| spec.md (with Epic) | Epic |
-| spec.md User Story | Story |
-| tasks.md Task | Sub-task |
-| Acceptance Tests (spec.md) | Acceptance Criteria (Story) |
-| Acceptance Criteria (tasks.md) | Sub-task checklist |
-| Status: planned | To Do |
-| Status: in-progress | In Progress |
-| Status: completed | Done |
-
-### JIRA Structure Example
-
-**spec.md with JIRA structure**:
-```markdown
----
-increment: 002-payment-processing
-status: planned
-structure: jira
-jira_epic: PROJ-123
----
-
-## Epic: E-commerce Infrastructure
-**JIRA**: PROJ-123
-
-### Story: Subscribe to Plan
-**JIRA**: PROJ-124
-**Priority**: P1
-**Labels**: payments, stripe
-**Components**: Backend, Frontend
-
-**Description**:
-As a user, I want to subscribe to a monthly plan...
-
-**Acceptance Criteria**:
-- User can select plan
-- Payment processed
-- Subscription activated
-```
-
-**tasks.md creates Sub-tasks**:
-```markdown
-## Tasks for PROJ-124 (Subscribe to Plan)
-
-### Task T001: Create StripeService
-**JIRA**: PROJ-125 (Sub-task of PROJ-124)
-**Agent**: nodejs-backend
-
-**Description**: Create Stripe service class...
-
-**Acceptance Criteria**:
-- [ ] StripeService class exists
-- [ ] Unit tests passing
-```
-
-## Authentication
-
-**JIRA Cloud**:
-
-
-**JIRA Server/Data Center**:
-```yaml
-jira_sync:
-  type: "server"
-  url: "https://jira.your-company.com"
-  username: "user"
-  password: "${JIRA_PASSWORD}"  # From environment variable
-  project_key: "PROJ"
-```
-
-## Configuration
-
-
-
-## Workflow
-
-### Export Workflow (SpecWeave → JIRA)
-
-```
-User: Creates increment in SpecWeave
-  .specweave/increments/0002-payment/
-    spec.md (with structure: jira)
-    tasks.md
-
-↓ jira-sync detects new increment
-
-Creates in JIRA:
-  Epic: PROJ-123 "E-commerce Infrastructure"
-    Story: PROJ-124 "Subscribe to Plan"
-      Sub-task: PROJ-125 "Create StripeService"
-      Sub-task: PROJ-126 "Create API endpoints"
-
-Links created:
-  spec.md → PROJ-124
-  tasks.md T001 → PROJ-125
-  tasks.md T002 → PROJ-126
-```
-
-### Import Workflow (JIRA → SpecWeave)
-
-```
-User: Updates JIRA issue status to "In Progress"
-
-↓ JIRA webhook triggers
-
-jira-sync:
-  Detects change to PROJ-124
-  Finds linked increment: 002-payment
-  Updates: .specweave/increments/0002-payment/spec.md
-    status: planned → in-progress
-```
-
-### Bidirectional Sync
-
-```
-User: Checks off task in tasks.md
-  - [x] T001: Create StripeService
-
-↓ jira-sync detects change
-
-Updates JIRA:
-  PROJ-125 status → Done
-
-User: Changes PROJ-124 to "Done" in JIRA
-
-↓ JIRA webhook triggers
-
-jira-sync updates SpecWeave:
-  .specweave/increments/0002-payment/spec.md
-    status: in-progress → completed
-```
-
-## API Integration
-
-### JIRA REST API Endpoints Used
-
-```typescript
-// Create Epic
-POST /rest/api/3/issue
-{
-  "fields": {
-    "project": { "key": "PROJ" },
-    "issuetype": { "name": "Epic" },
-    "summary": "E-commerce Infrastructure",
-    "customfield_10011": "epic-name"  // Epic Name field
-  }
-}
-
-// Create Story (linked to Epic)
-POST /rest/api/3/issue
-{
-  "fields": {
-    "project": { "key": "PROJ" },
-    "issuetype": { "name": "Story" },
-    "summary": "Subscribe to Plan",
-    "parent": { "key": "PROJ-123" }  // Link to Epic
-  }
-}
-
-// Create Sub-task
-POST /rest/api/3/issue
-{
-  "fields": {
-    "project": { "key": "PROJ" },
-    "issuetype": { "name": "Sub-task" },
-    "parent": { "key": "PROJ-124" },
-    "summary": "Create StripeService"
-  }
-}
-
-// Update status
-POST /rest/api/3/issue/{issueKey}/transitions
-{
-  "transition": { "id": "31" }  // "In Progress"
-}
-```
-
-## Webhooks
-
-### Setup JIRA Webhook
-
-1. Go to JIRA Settings → System → Webhooks
-2. Create webhook:
-   - URL: `https://your-app.com/api/webhooks/jira`
-   - Events: Issue created, updated, deleted
-   - Secret: Random string (store in JIRA_WEBHOOK_SECRET)
-
-### Webhook Handler
-
-```typescript
-// Receives JIRA webhook
-POST /api/webhooks/jira
-
-// jira-sync processes:
-1. Verify webhook signature
-2. Extract issue data
-3. Find linked SpecWeave increment
-4. Update spec.md or tasks.md
-5. Commit changes (optional)
-```
-
-## Conflict Resolution
-
-**Scenario**: Both SpecWeave and JIRA updated simultaneously
-
-**Strategy**:
-1. **Timestamp-based**: Latest change wins
-2. **User prompt**: Ask user which to keep
-3. **Merge**: Combine changes if possible
-
-**Example**:
-```
-SpecWeave: status → in-progress (10:00 AM)
-JIRA: status → done (10:05 AM)
-
-jira-sync:
-  Latest is JIRA (10:05 AM)
-  Update SpecWeave → done
-```
-
-## Error Handling
-
-**Common errors**:
-- JIRA API rate limits → Retry with exponential backoff
-- Authentication failed → Notify user, check credentials
-- Issue not found → Create if export, skip if import
-- Network errors → Queue for retry
-
-## Testing
-
-**Test scenarios**:
-1. Create increment → Creates JIRA issues
-2. Update JIRA → Updates SpecWeave
-3. Update SpecWeave → Updates JIRA
-4. Conflict resolution
-5. Webhook handling
-6. Error recovery
-
-## Integration with Other Skills
-
-- **task-builder**: Reads JIRA structure from spec.md
-- **increment-planner**: Can specify structure: jira
-
-## Future Enhancements
-
-- Support for JIRA sprints/iterations
-- Sync custom fields
-- Attachment sync
-- Advanced filtering (which issues to sync)
-- Bulk import from JIRA
-
----
-
-**To implement**: See task in .specweave/increments/
-
-**See also**: `ado-sync` skill for Azure DevOps integration

package/plugins/specweave/skills/jira-sync/SKILL.md

@@ -1,252 +0,0 @@
----
-description: "[DEPRECATED] Sync guidance for SpecWeave increments with JIRA epics/stories (content SpecWeave→JIRA, status JIRA→SpecWeave). Use when asking about JIRA integration setup or troubleshooting sync. For actual syncing, use sw-jira:push or sw-jira:pull command instead."
-version: 1.0.0
-user-invokable: false
-deprecated: true
-allowed-tools: Read, Task
----
-
-> ⚠️ DEPRECATED: Use `sw-jira:push` / `sw-jira:pull` instead. This skill will be removed in v1.3.0.
-
-## Migration
-
-This skill has been deprecated as part of the Opus 4.7 framework alignment (increment 0669).
-
-- **Use instead**: `sw-jira:push` (content SpecWeave→JIRA) and `sw-jira:pull` (status JIRA→SpecWeave)
-- **Removal**: Scheduled for v1.3.0 (2 minor releases after v1.1.0)
-- **Why**: Consolidated sync logic moved to the `sw-jira:*` command family.
-
-For the migration policy, see `.specweave/docs/internal/specs/skill-deprecation-policy.md`.
-
----
-
-# JIRA Sync Skill
-
-Coordinates JIRA synchronization by delegating to `jira-mapper` agent.
-
-**Sync Behavior**: Content (specs, tasks) syncs SpecWeave → JIRA. Status (open/closed) syncs JIRA → SpecWeave.
-
-**⚠️ IMPORTANT**: This skill provides HELP and GUIDANCE about JIRA sync. For actual syncing, users should use the `sw-jira:sync` command directly. This skill should NOT auto-activate when the command is being invoked.
-
-## When to Activate
-
-✅ **Do activate when**:
-- User asks: "How do I set up JIRA sync?"
-- User asks: "What JIRA credentials do I need?"
-- User asks: "How does JIRA sync work?"
-- User needs help configuring JIRA integration
-
-❌ **Do NOT activate when**:
-- User invokes `sw-jira:sync` command (command handles it)
-- Command is already running (avoid duplicate invocation)
-- Task completion hook is syncing (automatic process)
-
-## Responsibilities
-
-1. Answer questions about JIRA sync configuration
-2. Help validate prerequisites (JIRA credentials, increment structure)
-3. Explain sync directions: content (SpecWeave→JIRA), status (JIRA→SpecWeave)
-4. Provide troubleshooting guidance
-
----
-
-## CRITICAL: Secrets Required (MANDATORY CHECK)
-
-**BEFORE attempting JIRA sync, CHECK for JIRA credentials.**
-
-**SECURITY RULE**: This skill MUST NOT collect, write, or store credentials. The user configures their own `.env` file. The skill only validates that credentials exist.
-
-### Step 1: Check If Credentials Exist
-
-```bash
-# Check .env file for required credentials (existence only — never read values)
-if [ -f .env ] && grep -q "^JIRA_API_TOKEN=" .env && grep -q "^JIRA_EMAIL=" .env && grep -q "^JIRA_DOMAIN=" .env; then
-  echo "JIRA credentials found in .env"
-else
-  echo "JIRA credentials missing — see setup instructions below"
-  # STOP HERE — do NOT prompt user for secrets
-fi
-```
-
-### Step 2: If Credentials Missing, Show Setup Instructions
-
-Do NOT ask the user to paste credentials into the chat. Instead, show self-service setup:
-
-```
-JIRA credentials are required but not configured.
-
-**Setup (do this yourself — the agent should NOT handle your secrets):**
-
-1. Create an API token at: https://id.atlassian.com/manage-profile/security/api-tokens
-2. Add these lines to your project `.env` file:
-
-   JIRA_API_TOKEN=<your-token>
-   JIRA_EMAIL=<your-email>
-   JIRA_DOMAIN=<your-company>.atlassian.net
-
-3. Ensure `.env` is in `.gitignore`
-4. Re-run the sync command
-
-For self-hosted JIRA: Use a Personal Access Token (PAT) and your server's hostname.
-```
-
-**IMPORTANT**: After showing instructions, STOP. Do not continue until credentials are configured by the user.
-
-### Step 3: Validate Credential Presence (Not Values)
-
-```bash
-# Validate that required keys exist and have non-empty values
-# Uses grep -qE to check pattern without reading values into variables
-MISSING=()
-for KEY in JIRA_API_TOKEN JIRA_EMAIL JIRA_DOMAIN; do
-  if ! grep -qE "^${KEY}=.+" .env; then
-    MISSING+=("$KEY")
-  fi
-done
-
-if [ ${#MISSING[@]} -gt 0 ]; then
-  echo "Missing or empty credentials: ${MISSING[*]}"
-  exit 1
-fi
-echo "All required credentials present"
-```
-
-### Step 4: Domain Validation (Strict)
-
-```bash
-# Read domain safely — quote all expansions, take first match only
-JIRA_DOMAIN="$(grep '^JIRA_DOMAIN=' .env | head -1 | cut -d '=' -f2-)"
-
-# Reject empty
-if [ -z "$JIRA_DOMAIN" ]; then
-  echo "Error: JIRA_DOMAIN is empty"
-  exit 1
-fi
-
-# Reject IP addresses FIRST — IPv4, IPv6 brackets, hex-encoded (SSRF prevention)
-if [[ "$JIRA_DOMAIN" =~ ^[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+ ]] || [[ "$JIRA_DOMAIN" =~ ^\[.*\]$ ]] || [[ "$JIRA_DOMAIN" =~ ^0x ]]; then
-  echo "Error: IP addresses not allowed — use a hostname"
-  exit 1
-fi
-
-# Reject localhost and internal hostnames
-if [[ "$JIRA_DOMAIN" =~ ^(localhost|127\.|10\.|172\.(1[6-9]|2[0-9]|3[01])\.|192\.168\.) ]]; then
-  echo "Error: Internal/localhost addresses not allowed"
-  exit 1
-fi
-
-# Must be a valid hostname — each label: alphanumeric, hyphens allowed mid-label, no consecutive dots
-if [[ ! "$JIRA_DOMAIN" =~ ^[a-zA-Z0-9]([a-zA-Z0-9-]*[a-zA-Z0-9])?(\.[a-zA-Z0-9]([a-zA-Z0-9-]*[a-zA-Z0-9])?)*$ ]]; then
-  echo "Error: JIRA_DOMAIN is not a valid hostname"
-  exit 1
-fi
-
-# Cloud JIRA: must end with .atlassian.net
-# Self-hosted JIRA: any valid hostname is accepted after user confirmation
-if [[ ! "$JIRA_DOMAIN" =~ ^[a-zA-Z0-9-]+\.atlassian\.net$ ]]; then
-  echo "Warning: Domain does not match <subdomain>.atlassian.net (Jira Cloud) pattern"
-  echo "If this is a self-hosted JIRA instance, confirm the domain is correct and proceed."
-  # Agent: use AskUserQuestion to confirm non-standard domain before continuing
-fi
-```
-
-### Step 5: Configure Sync Profile
-
-Add to `.specweave/config.json`:
-```json
-{
-  "sync": {
-    "enabled": true,
-    "preset": "bidirectional",
-    "activeProfile": "default",
-    "profiles": {
-      "default": {
-        "provider": "jira",
-        "config": {
-          "domain": "mycompany.atlassian.net",
-          "projectKey": "MYPROJ",
-          "syncOnTaskComplete": true
-        }
-      }
-    }
-  }
-}
-```
-
-For self-hosted JIRA, use your server's hostname as the domain (e.g., `jira.internal.company.com`).
-
-### Step 6: Credential Loading and API Calls
-
-This skill does NOT execute API calls directly (no Bash tool). Credential loading, authentication, and API operations are handled by the `jira-mapper` skill — see its **Security Rules** section for the hardened patterns (domain validation, HTTPS enforcement, SSRF prevention, variable quoting).
-
-### Step 7: Production Recommendations
-
-**For production deployments, use OAuth 2.0** instead of API tokens:
-
-- More secure (no long-lived credentials)
-- Fine-grained permissions (scopes)
-- Automatic token refresh
-- Audit trail in JIRA
-
-**Setup**: https://developer.atlassian.com/console/myapps/ (OAuth 2.0 with scopes: `read:jira-work`, `write:jira-work`)
-
-**For self-hosted JIRA**: Use Personal Access Tokens (PAT) instead of API tokens.
-
----
-
-## Usage
-
-**Export**: `/sync-jira export 0001`
-**Import**: `/sync-jira import PROJ-123`
-**Sync**: `/sync-jira sync 0001`
-
-All conversion logic is handled by the `jira-mapper` agent.
-
----
-
-## Confluence Page Sync
-
-JIRA and Confluence are both Atlassian products and often used together. This skill can also help with Confluence page sync.
-
-### Confluence Credentials
-
-Same authentication and security rules as JIRA — user configures `.env`, skill only validates presence. Same domain validation applies (must be `<subdomain>.atlassian.net`, HTTPS only, no IPs). `CONFLUENCE_DOMAIN` MUST pass the same validation as `JIRA_DOMAIN` (Step 4) before any Confluence API call.
-
-Required `.env` keys (configured by the user, NOT by this skill):
-```
-CONFLUENCE_API_TOKEN=<your-token>    # Same as JIRA API token
-CONFLUENCE_EMAIL=<your-email>
-CONFLUENCE_DOMAIN=<your-company>.atlassian.net
-CONFLUENCE_SPACE_KEY=<space-key>
-```
-
-### Key Confluence Operations
-
-| Operation | Endpoint | Method |
-|-----------|----------|--------|
-| Get page | `/wiki/api/v2/pages/{id}?body-format=storage` | GET |
-| Update page | `/wiki/api/v2/pages/{id}` | PUT |
-| Create page | `/wiki/api/v2/pages` | POST |
-
-### Critical: Version Increment
-
-**Every page update MUST increment the version number**:
-
-1. GET current page to retrieve `version.number` (e.g., returns 5)
-2. PUT update with `version.number` set to current + 1 (e.g., 6)
-
-If version is not incremented, the API returns `409 Conflict`.
-
-All Confluence API calls follow the same security rules as JIRA (HTTPS only, domain validation, credential handling). See the `jira-mapper` skill's **Security Rules** section for implementation patterns.
-
-### Reference Documentation
-
-For complete Confluence API details, see:
-- [confluence-page-api.md](../../reference/confluence-page-api.md)
-
-### When to Use Confluence Sync
-
-- Sync increment specs to Confluence for stakeholder visibility
-- Publish living docs to Confluence wiki
-- Sync task completion status to Confluence task lists
-- Create Confluence pages for PRDs, HLDs, ADRs