specweave 1.0.593 → 2.0.0

package/plugins/specweave/commands/jira-sync.md

@@ -1,254 +0,0 @@
----
-description: Sync SpecWeave increments with JIRA epics/stories. Supports import, export, two-way sync, and granular item operations
----
-
-# Sync Jira Command
-
-You are a Jira synchronization expert. Help the user sync between Jira and SpecWeave with granular control.
-
-## Available Operations
-
-### Epic-Level Operations
-
-**1. Two-way Sync (Default - Recommended)**
-```
-sw-jira:sync 0003                    # Two-way sync (default)
-sw-jira:sync 0003 --direction two-way  # Explicit
-```
-
-**2. Import Jira Epic as SpecWeave Increment**
-```
-sw-jira:sync import SCRUM-123        # One-time pull
-sw-jira:sync SCRUM-123 --direction from-jira  # Same as import
-```
-
-**3. Export SpecWeave Increment to Jira**
-```
-sw-jira:sync export 0001             # One-time push
-sw-jira:sync 0001 --direction to-jira  # Same as export
-```
-
-### Sync Direction Options
-
-**Default: `two-way`** (both directions - recommended)
-
-- `--direction two-way`: SpecWeave ↔ Jira (default)
-  - Pull changes FROM Jira (status, priority, comments)
-  - Push changes TO Jira (tasks, progress, metadata)
-
-- `--direction to-jira`: SpecWeave → Jira only
-  - Push increment progress to Jira
-  - Don't pull Jira changes back
-  - Same as `export` operation
-
-- `--direction from-jira`: Jira → SpecWeave only
-  - Pull Jira issue updates
-  - Don't push SpecWeave changes
-  - Same as `import` operation
-
-### Granular Item Operations
-
-**4. Add specific Story/Bug/Task to existing Increment**
-```
-sw-jira:sync add SCRUM-1 to 0003
-sw-jira:sync add SCRUM-1              # Adds to current increment
-```
-
-**5. Create Increment from specific items (cherry-pick)**
-```
-sw-jira:sync create "User Authentication" from SCRUM-1 SCRUM-5 SCRUM-7
-sw-jira:sync create "Bug Fixes Sprint 1" from SCRUM-10 SCRUM-15 SCRUM-20
-```
-
-**6. Show sync status**
-```
-sw-jira:sync status
-sw-jira:sync status 0003              # Status of specific increment
-```
-
-## Your Task
-
-When the user runs this command:
-
-1. **Parse the command arguments**:
-   - Operation: import, sync, export, add, create, or status
-   - ID: Jira Epic key (e.g., SCRUM-123) or Increment ID (e.g., 0001)
-
-2. **Execute the operation**:
-
-   **For import Epic**:
-   ```typescript
-   import { JiraClient } from './src/integrations/jira/jira-client';
-   import { JiraMapper } from './src/integrations/jira/jira-mapper';
-
-   const client = new JiraClient();
-   const mapper = new JiraMapper(client);
-   const result = await mapper.importEpicAsIncrement('SCRUM-123');
-   ```
-
-   **For add item**:
-   ```typescript
-   import { JiraIncrementalMapper } from './src/integrations/jira/jira-incremental-mapper';
-
-   const incrementalMapper = new JiraIncrementalMapper(client);
-   const result = await incrementalMapper.addItemToIncrement('0003', 'SCRUM-1');
-   ```
-
-   **For create from items**:
-   ```typescript
-   const result = await incrementalMapper.createIncrementFromItems(
-     'User Authentication',
-     ['SCRUM-1', 'SCRUM-5', 'SCRUM-7']
-   );
-   ```
-
-   **For sync**:
-   ```typescript
-   const result = await mapper.syncIncrement('0003');
-   ```
-
-   **For export**:
-   ```typescript
-   const result = await mapper.exportIncrementAsEpic('0001', 'SCRUM');
-   ```
-
-3. **Show results**:
-   - Display sync summary
-   - Show conflicts (if any)
-   - List created/updated files
-   - Provide links to Jira and SpecWeave
-
-4. **Handle errors gracefully**:
-   - Check if .env credentials exist
-   - Validate increment/epic exists
-   - Show clear error messages
-
-## Examples
-
-### Example 1: Import Epic
-**User**: `sw:sync-jira import SCRUM-2`
-**You**:
-- Import Epic SCRUM-2 from Jira
-- Show: "✅ Imported as Increment 0004"
-- List: "Created: spec.md, tasks.md, RFC document"
-- Link: "Jira: https://... | Increment: .specweave/increments/0004/"
-
-### Example 2: Add Story to Current Increment
-**User**: `sw:sync-jira add SCRUM-1`
-**You**:
-- Determine current increment (latest or from context)
-- Fetch SCRUM-1 from Jira
-- Add to increment's spec.md (under ## User Stories)
-- Update tasks.md
-- Update RFC
-- Show: "✅ Added Story SCRUM-1 to Increment 0003"
-- Display: "Type: story | Title: User can login | Status: in-progress"
-
-### Example 3: Add Bug to Specific Increment
-**User**: `sw:sync-jira add SCRUM-10 to 0003`
-**You**:
-- Fetch SCRUM-10 from Jira (it's a Bug)
-- Add to increment 0003's spec.md (under ## Bugs)
-- Update tasks.md
-- Update RFC
-- Show: "✅ Added Bug SCRUM-10 to Increment 0003"
-- Display: "Type: bug | Priority: P1 | Title: Fix login redirect"
-
-### Example 4: Create Increment from Multiple Items
-**User**: `sw:sync-jira create "User Authentication" from SCRUM-1 SCRUM-5 SCRUM-7`
-**You**:
-- Fetch all 3 issues from Jira
-- Determine types (story, bug, task)
-- Create new increment 0005
-- Group by type in spec.md:
-  - ## User Stories (SCRUM-1, SCRUM-5)
-  - ## Technical Tasks (SCRUM-7)
-- Generate RFC with all items
-- Show: "✅ Created Increment 0005 with 3 work items"
-- Display table:
-  ```
-  | Type  | Jira Key | Title           |
-  |-------|----------|-----------------|
-  | Story | SCRUM-1  | User login UI   |
-  | Story | SCRUM-5  | OAuth backend   |
-  | Task  | SCRUM-7  | Setup provider  |
-  ```
-
-### Example 5: Two-way Sync (Default)
-**User**: `sw-jira:sync 0003`
-**You**:
-- Read increment 0003
-- Find linked Jira items (from spec.md frontmatter.work_items)
-- Fetch current state from Jira
-
-**Detect changes (both directions)**:
-- FROM Jira: Status changes, priority updates, comments
-- FROM SpecWeave: Task completion, progress updates
-
-**Show two-way sync summary**:
-```
-✅ Two-way Sync Complete: 0003 ↔ Jira
-
-FROM Jira:
-  • SCRUM-1: Status changed to In Progress
-  • SCRUM-10: Priority raised to P1
-
-FROM SpecWeave:
-  • 3 tasks completed (T-005, T-006, T-007)
-  • Progress: 60% → 75%
-
-Conflicts: None
-```
-
-**Handle conflicts if any**:
-- Show both versions (Jira vs SpecWeave)
-- Ask user which to keep or how to merge
-- Apply resolution in both directions
-
-### Example 6: Status Overview
-**User**: `sw-jira:sync status`
-**You**:
-- Scan all increments for Jira metadata
-- Show table:
-  ```
-  | Increment | Title            | Jira Items | Last Sync          |
-  |-----------|------------------|------------|--------------------|
-  | 0003      | Test Epic        | 0 items    | 2025-10-28 17:42   |
-  | 0004      | User Auth        | 3 items    | 2025-10-28 18:00   |
-  | 0005      | Bug Fixes        | 5 items    | Never              |
-  ```
-
-## Important Notes
-
-- Always check if .env has Jira credentials before syncing
-- Never log secrets or tokens
-- Show clear progress messages
-- Display rich output with links
-- Save sync results to test-results/ if requested
-
-## Simpler Alternatives
-
-For most use cases, use the git-style commands:
-
-| Command | Purpose |
-|---------|---------|
-| `sw-jira:pull` | Pull changes from Jira (read-only) |
-| `sw-jira:push` | Push progress to Jira |
-
-Use `sw-jira:sync` for advanced operations with explicit direction control.
-
-## Related Commands
-
-| Command | Purpose |
-|---------|---------|
-| `sw-jira:pull` | Pull from Jira (git-style) |
-| `sw-jira:push` | Push to Jira (git-style) |
-| `sw-jira:import-boards` | Import Jira boards |
-| `sw-github:sync` | Sync to GitHub issues |
-| `sw:increment` | Create new increment |
-
----
-
-**Two-way by Default**: All sync operations are two-way unless you explicitly specify `--direction to-jira` or `--direction from-jira`. This keeps both systems synchronized automatically.
-
-**Granular Control**: Unlike simple epic import/export, this command supports cherry-picking individual stories, bugs, and tasks for maximum flexibility.

package/plugins/specweave/commands/jobs.md

@@ -1,52 +0,0 @@
----
-description: View and manage background jobs (cloning, imports, living-docs). Shows job status, progress, and logs. Use when saying "check jobs", "job status", or "background tasks".
-argument-hint: "[--all] [--id job-id]"
----
-
-# Background Jobs Monitor
-
-## Project Overrides
-
-**Skill Memories**: If `.specweave/skill-memories/jobs.md` exists, read and apply its learnings.
-
-Shows background job information including:
-- **Clone jobs** — repository cloning progress and status
-- **Import jobs** — issue/epic import from GitHub, JIRA, ADO
-- **Living docs** — documentation builder progress
-- **Brownfield analysis** — code-spec gap detection
-
-## Hook Execution (Default)
-
-This command is intercepted by the **UserPromptSubmit hook** for instant execution (<100ms). The hook runs `read-jobs.sh` or `jobs.js` directly.
-
-**No action needed** — the hook output appears automatically in `<system-reminder>` tags.
-
-## CLI Fallback
-
-If hook output isn't displayed (rare), execute:
-
-```bash
-specweave jobs
-```
-
-## Arguments
-
-- `sw:jobs` — Show active and recent jobs
-- `sw:jobs --all` — Show all jobs including completed
-- `sw:jobs --id <job-id>` — Show details for specific job
-
-## Data Shown
-
-| Field | Description |
-|-------|-------------|
-| Job ID | Short UUID identifier |
-| Type | clone-repos, import-issues, living-docs-builder, etc. |
-| Status | pending, running, completed, completed_with_warnings, failed |
-| Progress | `X/Y (Z%)` with progress bar |
-| Duration | Elapsed time since job started |
-
-## Related Commands
-
-- `sw:progress` — Increment task/AC completion
-- `sw-github:clone` — Trigger GitHub repo cloning
-- `sw-ado:clone` — Trigger ADO repo cloning