specweave 1.0.593 → 2.0.3

package/plugins/specweave/skills/github-multi-project/SKILL.md

@@ -1,258 +0,0 @@
----
-description: "[DEPRECATED] Use `sw:multi-project --tool github` instead. Organizes specs and splits tasks across multiple GitHub repositories. This skill will be removed in SpecWeave v1.3.0."
-version: 1.0.0
-user-invokable: false
----
-
-# GitHub Multi-Project Management Skill
-
-## Migration
-
-> Deprecated. Use: `sw:multi-project --tool github`
-
-This skill has been consolidated into the unified `sw:multi-project` skill. Replace any invocation of `sw:github-multi-project` with `sw:multi-project --tool github`. The flag-based skill supports GitHub, Azure DevOps, and Jira under a single interface. See `plugins/specweave/skills/multi-project/SKILL.md`.
-
-Scheduled for removal in SpecWeave v1.3.0.
-
-Expert skill for managing SpecWeave projects across multiple GitHub repositories.
-
-## Core Capabilities
-
-### 1. Spec Organization
-- Organizes specs in `.specweave/docs/internal/projects/{project-id}/` structure
-- Maps increments to specific projects/repos
-- Maintains traceability across repositories
-- Handles cross-project dependencies
-
-### 2. Task Splitting
-When a SpecWeave increment spans multiple repositories:
-- Analyzes tasks in `tasks.md`
-- Identifies which tasks belong to which repo
-- Creates repo-specific task lists
-- Maintains cross-repo coordination
-
-### 3. Repository Architectures
-
-#### Single Repository
-```
-my-app/
-├── .specweave/
-│   └── docs/internal/projects/default/
-└── src/
-```
-
-#### Multi-Repository (Polyrepo)
-```
-my-app-frontend/
-├── .git
-└── src/
-
-my-app-backend/
-├── .git
-└── src/
-
-my-app-shared/
-├── .git
-└── src/
-```
-
-#### Parent Repository Approach (Recommended for Multi-Repo)
-```
-my-app-parent/              # Parent repo with .specweave
-├── .specweave/
-│   └── docs/internal/projects/
-│       ├── frontend/
-│       ├── backend/
-│       └── shared/
-└── services/               # Implementation repos
-    ├── frontend/
-    ├── backend/
-    └── shared/
-```
-
-#### Monorepo
-```
-my-app/
-├── .specweave/
-│   └── docs/internal/projects/
-│       ├── frontend/
-│       ├── backend/
-│       └── shared/
-└── packages/
-    ├── frontend/
-    ├── backend/
-    └── shared/
-```
-
-## Task Splitting Examples
-
-### Example 1: E-commerce Platform
-**Increment**: Add shopping cart functionality
-
-**Tasks split by repository**:
-
-**Frontend (my-app-frontend)**:
-- T-001: Create CartItem component
-- T-002: Implement cart state management
-- T-003: Add cart UI with add/remove buttons
-
-**Backend (my-app-backend)**:
-- T-004: Create cart database schema
-- T-005: Implement cart API endpoints
-- T-006: Add cart validation logic
-
-**Shared (my-app-shared)**:
-- T-007: Define cart TypeScript types
-- T-008: Create cart utility functions
-
-### Example 2: Microservices Architecture
-**Increment**: Implement user notifications
-
-**Tasks split by service**:
-
-**User Service**:
-- T-001: Add notification preferences to user profile
-- T-002: Create preference API endpoints
-
-**Notification Service**:
-- T-003: Implement notification queue
-- T-004: Create email sender
-- T-005: Create push notification sender
-
-**Gateway Service**:
-- T-006: Add notification routes
-- T-007: Implement rate limiting
-
-## Commands
-
-### Analyze Task Distribution
-```typescript
-// Analyze which tasks belong to which repository
-function analyzeTaskDistribution(tasks: Task[]): Map<string, Task[]> {
-  const distribution = new Map();
-
-  for (const task of tasks) {
-    const repo = detectRepository(task);
-    if (!distribution.has(repo)) {
-      distribution.set(repo, []);
-    }
-    distribution.get(repo).push(task);
-  }
-
-  return distribution;
-}
-```
-
-### Create Repository-Specific Issues
-```typescript
-// Create GitHub issues in each repository
-async function createRepoSpecificIssues(
-  increment: Increment,
-  distribution: Map<string, Task[]>
-) {
-  for (const [repo, tasks] of distribution) {
-    const issue = await createGitHubIssue({
-      repo,
-      title: `[${increment.id}] ${increment.name} - ${repo}`,
-      body: formatTasksAsChecklist(tasks),
-      labels: ['specweave', 'increment', repo]
-    });
-
-    console.log(`Created issue #${issue.number} in ${repo}`);
-  }
-}
-```
-
-## Best Practices
-
-### 1. Parent Repository Approach
-**Recommended for multi-repo projects**:
-- Central .specweave/ folder in parent repo
-- Living docs sync to parent (single source of truth)
-- Implementation repos stay clean
-- Better for enterprise/multi-team projects
-
-### 2. Task Naming Convention
-```
-T-{repo}-{number}: {description}
-T-FE-001: Create user profile component
-T-BE-001: Implement user API
-T-SHARED-001: Define user types
-```
-
-### 3. Cross-Repository Dependencies
-Mark dependencies clearly:
-```
-T-FE-002: Consume user API
-  Dependencies: T-BE-001 (must complete first)
-```
-
-### 4. Spec Organization
-```
-.specweave/docs/internal/projects/
-├── frontend/
-│   └── specs/
-│       ├── spec-001-user-interface.md
-│       └── spec-002-cart-ui.md
-├── backend/
-│   └── specs/
-│       ├── spec-001-api-design.md
-│       └── spec-002-database.md
-└── shared/
-    └── specs/
-        └── spec-001-types.md
-```
-
-## Integration with GitHub Projects
-
-### Multi-Repo GitHub Project
-Create a GitHub Project that spans multiple repositories:
-1. Create project at organization level
-2. Add issues from all repos
-3. Use project boards for cross-repo coordination
-4. Track overall increment progress
-
-### Repository-Specific Projects
-Each repository can have its own project:
-- Frontend Project: UI tasks
-- Backend Project: API tasks
-- Shared Project: Common tasks
-
-## Automation
-
-### GitHub Actions Integration
-```yaml
-# .github/workflows/specweave-sync.yml
-name: SpecWeave Multi-Repo Sync
-
-on:
-  workflow_dispatch:
-  schedule:
-    - cron: '0 */6 * * *' # Every 6 hours
-
-jobs:
-  sync:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v3
-      - name: Sync to repositories
-        run: |
-          # Sync tasks to frontend repo
-          gh issue create --repo myorg/frontend ...
-
-          # Sync tasks to backend repo
-          gh issue create --repo myorg/backend ...
-```
-
-## Error Handling
-
-### Common Issues
-1. **Repository not found**: Ensure repos exist and token has access
-2. **Task ambiguity**: Use clear naming to indicate target repo
-3. **Cross-repo conflicts**: Use parent repo as single source of truth
-4. **Permission errors**: Token needs repo scope for all repositories
-
-## Related Skills
-- github-sync: Basic GitHub synchronization
-- github-issue-tracker: Task-level tracking
-- specweave:multi-project-spec-mapper: Intelligent spec splitting

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

@@ -1,40 +0,0 @@
----
-description: "[DEPRECATED] GitHub sync guidance. Superseded by the live sw-github:* command family. For actual syncing use sw-github:push / sw-github:pull / sw-github:close / sw-github:sync."
-version: 1.0.1
-user-invokable: false
-deprecated: true
----
-
-> ⚠️ DEPRECATED — superseded by the live `sw-github:*` command family.
-
-This skill's standalone guidance is retired. GitHub sync is performed by the
-increment-based command family, which is the source of truth:
-
-| Action | Live command |
-|--------|--------------|
-| Push local progress to GitHub Issues | `sw-github:push [increment-id]` |
-| Pull issue state back into the spec | `sw-github:pull` |
-| Create the GitHub Issue/milestone | `sw-github:create` |
-| Close issues on increment completion | `sw-github:close` |
-| Two-way reconcile | `sw-github:sync` |
-| Check sync status | `sw-github:status` |
-
-**Mapping** (per CLAUDE.md): Feature → Milestone · User Story → Issue · Task → Checkbox.
-
-## Why this skill is deprecated
-
-- The increment-based `sw-github:*` commands are the supported path. Run them
-  directly; this skill no longer carries its own workflow guidance (it was
-  contradictory — it pointed at a `sw-github:sync-spec` command that does not
-  exist and claimed increment-based sync was "removed" when it is the live flow).
-- Setup and credentials are handled by `sw:sync-setup`. Configuration lives in
-  `.specweave/config.json` (`sync.*`); the GitHub token is read from
-  `GITHUB_TOKEN` / `GH_TOKEN` in `.env` (or `gh auth login`).
-- For the deprecation policy, see
-  `.specweave/docs/internal/specs/skill-deprecation-policy.md`.
-
-## Removal
-
-Scheduled for removal once the `sw-github:*` command help fully absorbs any
-remaining setup notes. Until then this stub exists only to avoid contradictory
-guidance; it is non-activating (`user-invokable: false`).

package/plugins/specweave/skills/github-sync/evals/HOW-TO-RUN-EVALS.md

@@ -1,50 +0,0 @@
-# How to Run Evals for the GitHub Sync Skill
-
-This guide explains how to add test cases, run them, and compare quality with and without the skill.
-
-## What Are Evals?
-
-Evals are test cases that prove the skill works. Each one has:
-- A **prompt** -- something you'd actually ask (e.g., "How do I set up GitHub sync?")
-- **Assertions** -- specific things the skill should make Claude do (e.g., "mentions gh auth login", "explains spec-to-project mapping")
-
-We run each prompt twice: once with the skill loaded, once without. The difference in scores shows exactly how much value the skill adds.
-
-## File Structure
-
-```
-github-sync/
-  evals/
-    evals.json          <-- Test cases
-    HOW-TO-RUN-EVALS.md <-- This file
-```
-
-## Running Evals
-
-### Via vskill CLI
-
-```bash
-# Set the model (Opus 4.6 recommended for judging)
-export VSKILL_EVAL_MODEL=claude-opus-4-6
-export ANTHROPIC_API_KEY=sk-ant-...
-
-# Run evals for this skill
-vskill eval run specweave-github/github-sync
-```
-
-### Via Claude Code
-
-Ask Claude:
-> "Run the github-sync evals -- both with-skill and without-skill."
-
-## Adding Test Cases
-
-Open `evals.json` and add entries to the `evals` array. Each case needs:
-- A realistic prompt with specific details
-- Objectively verifiable assertions (boolean pass/fail)
-
-## Model Selection
-
-For eval generation and judging, use:
-- `claude-opus-4-6` -- highest quality, recommended for final evals
-- `claude-sonnet-4-6` -- faster, good for iteration

package/plugins/specweave/skills/github-sync/evals/evals.json

@@ -1,136 +0,0 @@
-{
-  "skill_name": "github-sync",
-  "evals": [
-    {
-      "id": 1,
-      "name": "initial-github-sync-setup",
-      "prompt": "I just started using SpecWeave on my project at github.com/myorg/backend-api. I want to sync my specs to GitHub Projects so my team can track progress. How do I set up the GitHub integration? I need two-way sync.",
-      "expected_output": "Should guide through GitHub CLI authentication (gh auth login), explain the config.json setup for the specweave-github plugin with repo and sync settings, and mention the live sw-github:push / sw-github:pull / sw-github:sync commands for manual sync.",
-      "files": [],
-      "assertions": [
-        {
-          "id": "gh-cli-auth",
-          "text": "Mentions GitHub CLI (gh) installation and authentication steps (gh auth login or gh auth status)",
-          "type": "boolean"
-        },
-        {
-          "id": "config-json-setup",
-          "text": "Shows or references the .specweave/config.json configuration with specweave-github plugin settings including repo, autoSyncSpecs, and syncDirection fields",
-          "type": "boolean"
-        },
-        {
-          "id": "specs-not-increments",
-          "text": "Clarifies that SpecWeave syncs specs (living docs) to GitHub, NOT increments, and explains why (specs are permanent, increments are temporary)",
-          "type": "boolean"
-        },
-        {
-          "id": "two-way-sync",
-          "text": "Explains two-way sync capability and mentions syncDirection: two-way as the default configuration",
-          "type": "boolean"
-        },
-        {
-          "id": "sync-command",
-          "text": "References a live sw-github:* command (sw-github:push, sw-github:pull, or sw-github:sync) for triggering manual sync operations",
-          "type": "boolean"
-        }
-      ]
-    },
-    {
-      "id": 2,
-      "name": "sync-troubleshooting-permissions",
-      "prompt": "My GitHub sync keeps failing with a 403 error when I run sw-github:push for increment 0003. I'm getting 'insufficient permissions' errors. I set up the token but something is wrong. How do I fix this?",
-      "expected_output": "Should diagnose GitHub permissions issues: check gh auth status, verify token scopes (needs repo and project access), check repository write access, suggest re-authenticating with correct scopes, and mention rate limit checking with gh api rate_limit.",
-      "files": [],
-      "assertions": [
-        {
-          "id": "check-auth-status",
-          "text": "Suggests running gh auth status to verify current authentication state and token validity",
-          "type": "boolean"
-        },
-        {
-          "id": "token-permissions",
-          "text": "Addresses token scope/permissions requirements - mentions needing repo write access or project access scopes",
-          "type": "boolean"
-        },
-        {
-          "id": "re-auth-suggestion",
-          "text": "Suggests re-authenticating (gh auth login) with correct scopes as a resolution step",
-          "type": "boolean"
-        },
-        {
-          "id": "rate-limit-check",
-          "text": "Mentions checking GitHub API rate limits (gh api rate_limit) as a potential cause of failures",
-          "type": "boolean"
-        },
-        {
-          "id": "config-verification",
-          "text": "Suggests verifying the .specweave/config.json sync configuration and repo field correctness",
-          "type": "boolean"
-        }
-      ]
-    },
-    {
-      "id": 3,
-      "name": "understand-sync-mapping",
-      "prompt": "Can you explain how SpecWeave maps to GitHub? I want to understand what becomes what. We have spec-001 with 5 user stories and each story has 3-4 acceptance criteria. What will this look like in GitHub?",
-      "expected_output": "Should explain the mapping: Spec -> GitHub Project (with title, description, columns), User Stories -> GitHub Issues (with AC as checkboxes, labels), progress tracking via checkbox updates, and automatic project column movement (Backlog -> In Progress -> Done).",
-      "files": [],
-      "assertions": [
-        {
-          "id": "spec-to-project",
-          "text": "Explains that a spec maps to a GitHub Project with title format [SPEC-001], description, and columns (Backlog, In Progress, Done)",
-          "type": "boolean"
-        },
-        {
-          "id": "story-to-issue",
-          "text": "Explains that each user story maps to a GitHub Issue with title format [US-001] and acceptance criteria as checkboxes in the issue body",
-          "type": "boolean"
-        },
-        {
-          "id": "ac-checkboxes",
-          "text": "Describes acceptance criteria being represented as checkboxes in GitHub Issues that get checked/unchecked as ACs are completed",
-          "type": "boolean"
-        },
-        {
-          "id": "labels-mentioned",
-          "text": "Mentions GitHub labels being applied to issues (e.g., user-story, spec:spec-001, priority labels)",
-          "type": "boolean"
-        },
-        {
-          "id": "progress-tracking",
-          "text": "Explains automatic progress tracking - project board column movement or percentage updates as tasks/ACs are completed",
-          "type": "boolean"
-        }
-      ]
-    },
-    {
-      "id": 4,
-      "name": "projects-v2-configuration",
-      "prompt": "We're using GitHub Projects V2 (the new board view). I want to set up SpecWeave to use our existing Projects V2 board (project number 5) with custom status fields. Our board has columns: Triage, Ready, Building, Review, Shipped. How do I configure this?",
-      "expected_output": "Should explain Projects V2 configuration with projectV2Enabled: true and projectV2Number: 5, custom status field mappings from SpecWeave states (planned, in-progress, completed) to the user's custom column names, and priority field mappings.",
-      "files": [],
-      "assertions": [
-        {
-          "id": "v2-config-fields",
-          "text": "Shows or references the projectV2Enabled: true and projectV2Number: 5 configuration settings in the sync config",
-          "type": "boolean"
-        },
-        {
-          "id": "status-field-mapping",
-          "text": "Explains statusFieldMapping configuration that maps SpecWeave states (planned, in-progress, completed) to custom column names",
-          "type": "boolean"
-        },
-        {
-          "id": "priority-field-mapping",
-          "text": "Mentions or shows priorityFieldMapping configuration for mapping P1-P4 priorities to custom priority field values",
-          "type": "boolean"
-        },
-        {
-          "id": "existing-board-reuse",
-          "text": "Addresses using an existing Projects V2 board by referencing its project number rather than creating a new one",
-          "type": "boolean"
-        }
-      ]
-    }
-  ]
-}