specweave 1.0.261 → 1.0.263

package/plugins/specweave/commands/external.md

@@ -1,145 +0,0 @@
----
-description: View external items dashboard - open issues from GitHub, JIRA, and Azure DevOps
-argument-hint: [--refresh]
----
-
-# External Items Dashboard
-
-**Usage**: `/sw:external [--refresh]`
-
----
-
-## Purpose
-
-Display a comprehensive dashboard of open external items from all configured providers:
-- **GitHub Issues** - Open issues in linked repository
-- **JIRA Tickets** - Open issues in configured project
-- **Azure DevOps Work Items** - Open work items in configured project
-
-Helps you stay aware of pending work and unaddressed items across all tools.
-
----
-
-## Output Format
-
-```
-External Items Dashboard
-
-GitHub Issues (4 open, 2 stale)
-  #779     DORA Metrics Workflow Failed                  10h ago
-  #778     DORA Metrics Workflow Failed                  1d ago
-  #777     DORA Metrics Workflow Failed                  1d ago   stale
-  #776     DORA Metrics Workflow Failed                  3d ago   stale
-
-JIRA: not configured
-
-ADO: not configured
-
-Total: 4 open (2 stale >7d)
-Last updated: 2 minutes ago (use --refresh to update)
-```
-
----
-
-## Options
-
-### --refresh
-
-Force refresh the cache and fetch latest data from all providers.
-
-```bash
-/sw:external --refresh
-```
-
----
-
-## Implementation
-
-When this command is invoked, execute the following:
-
-```typescript
-import { ExternalItemsCounter, displayDetailedDashboard } from '../src/core/external-tools/index';
-
-// Parse options
-const refresh = args.includes('--refresh');
-
-// Create counter
-const counter = new ExternalItemsCounter({
-  projectRoot: process.cwd(),
-  forceRefresh: refresh,
-});
-
-// Get summary
-const summary = await counter.getSummary();
-
-// Display dashboard
-displayDetailedDashboard(summary);
-```
-
----
-
-## Stale Detection
-
-Items older than 7 days are marked as "stale" with indicator:
-
-- **Stale** = created more than 7 days ago and still open
-- Review stale items regularly to avoid accumulating technical debt
-- Close or address items promptly
-
----
-
-## Caching
-
-- Default TTL: 15 minutes
-- Uses `.specweave/cache/external-items-summary.json`
-- Use `--refresh` to force update from APIs
-- Stale cache is used as fallback when rate limited
-
----
-
-## Provider Configuration
-
-### GitHub
-
-Auto-detected from git remote. Requires:
-- GitHub CLI (`gh`) installed
-- Authenticated: `gh auth login`
-
-### JIRA
-
-Set environment variables:
-- `JIRA_BASE_URL` - JIRA instance URL
-- `JIRA_EMAIL` - Your email
-- `JIRA_API_TOKEN` - API token
-- `JIRA_PROJECT_KEY` - Project key (optional)
-
-### Azure DevOps
-
-Set environment variables:
-- `ADO_ORG_URL` or `AZURE_DEVOPS_ORG_URL` - Organization URL
-- `ADO_PROJECT` or `AZURE_DEVOPS_PROJECT` - Project name
-- `ADO_PAT` or `AZURE_DEVOPS_PAT` - Personal Access Token
-
----
-
-## Integration Points
-
-External items are also shown in:
-- `/sw:status` - Summary section at bottom
-- `/sw:increment` - Notification after planning
-- `/sw:progress` - Footer line
-
----
-
-## Related Commands
-
-- `/sw:status` - Show increment status with external items summary
-- `/sw:progress` - Show detailed progress with external items footer
-- `/sw:import-external` - Import external items as increments
-
----
-
-**Command**: `/sw:external`
-**Plugin**: specweave (core)
-**Version**: v0.31.0
-**Part of**: Increment 0109 - External Items Dashboard

package/plugins/specweave/commands/import-docs.md

@@ -1,212 +0,0 @@
----
-description: Import brownfield documentation from Notion exports, Confluence, GitHub Wiki, or any markdown folder. Automatically classifies files as specs, modules, team docs, or legacy.
-disable-model-invocation: true
----
-
-# Import Brownfield Documentation
-
-Import existing documentation from Notion exports, Confluence, GitHub Wiki, or any markdown folder.
-
-## What This Does
-
-1. **Analyzes markdown files** in source directory (recursively)
-2. **Classifies files** based on content:
-   - **Specs** - Contains "user story", "acceptance criteria", "feature"
-   - **Modules** - Contains "module", "component", "architecture"
-   - **Team** - Contains "onboarding", "convention", "workflow"
-   - **Legacy** - Everything else (no strong match)
-3. **Copies files** to appropriate destinations
-4. **Creates migration report** with classification details
-5. **Updates config** with import history
-
-## Usage
-
-```bash
-/sw:import-docs <source-path> [options]
-```
-
-### Options
-
-- `--source=<type>` - Source type: `notion`, `confluence`, `wiki`, `custom` (required)
-- `--project=<id>` - Target project ID (default: active project)
-- `--preserve-structure` - Preserve original folder structure
-- `--dry-run` - Preview classification without importing
-
-## Examples
-
-### Example 1: Notion Export
-
-```bash
-# Export Notion workspace to /tmp/notion-export/
-# Then import:
-
-/sw:import-docs /tmp/notion-export/ --source=notion
-
-# Result:
-# 📊 Analysis Results:
-#    Total files: 47
-#    - Specs: 12 files → specs/
-#    - Modules: 18 files → modules/
-#    - Team docs: 5 files → team/
-#    - Legacy: 12 files → legacy/notion/
-# ✅ Import complete!
-```
-
-### Example 2: Confluence Export
-
-```bash
-/sw:import-docs /path/to/confluence/ --source=confluence --project=web-app
-
-# Imports to: projects/web-app/specs/, modules/, team/, legacy/confluence/
-```
-
-### Example 3: Dry Run (Preview)
-
-```bash
-/sw:import-docs /tmp/docs/ --source=custom --dry-run
-
-# Shows classification without importing files
-# Use this to preview results before actual import
-```
-
-### Example 4: Preserve Structure
-
-```bash
-/sw:import-docs /path/to/wiki/ --source=wiki --preserve-structure
-
-# Preserves original folder structure:
-# legacy/wiki/engineering/backend/auth.md
-# legacy/wiki/engineering/frontend/components.md
-```
-
-## Supported Sources
-
-### Notion
-- **Export Format**: Markdown & CSV
-- **Steps**:
-  1. In Notion: Settings → Export → Export all workspace content
-  2. Choose "Markdown & CSV" format
-  3. Download ZIP file
-  4. Extract to folder (e.g., `/tmp/notion-export/`)
-  5. Run import command
-
-### Confluence
-- **Export Format**: HTML or Markdown
-- **Steps**:
-  1. Space tools → Content Tools → Export
-  2. Choose HTML or Markdown
-  3. Extract exported files
-  4. Run import command
-
-### GitHub Wiki
-- **Export Format**: Git repository
-- **Steps**:
-  1. Clone wiki: `git clone https://github.com/user/repo.wiki.git`
-  2. Run import command on cloned directory
-
-### Custom (Any Markdown)
-- Any folder containing `.md` or `.markdown` files
-- Recursive search through subdirectories
-
-## Classification Algorithm
-
-Files are classified using keyword analysis:
-
-### Specs (70%+ confidence)
-- Keywords: "user story", "acceptance criteria", "feature", "requirement"
-- Patterns: "As a [user], I want [goal]", "Given-When-Then"
-- Example: Feature specs, PRDs, user stories
-
-### Modules (70%+ confidence)
-- Keywords: "module", "component", "service", "architecture"
-- Patterns: API docs, technical design, integration points
-- Example: Auth module, payment processing, ML pipeline
-
-### Team (70%+ confidence)
-- Keywords: "onboarding", "convention", "workflow", "pr process"
-- Patterns: Team processes, coding standards, deployment guides
-- Example: Onboarding guide, code review checklist
-
-### Legacy (<70% confidence)
-- No strong match to above categories
-- Uncertain classification
-- Requires manual review
-
-## Destination Folders
-
-Files are imported to:
-
-```
-.specweave/docs/internal/projects/{project}/
-├── specs/              ← Specs (spec keywords)
-├── modules/            ← Modules (module keywords)
-├── team/               ← Team docs (team keywords)
-└── legacy/{source}/    ← Legacy (uncertain classification)
-    ├── notion/
-    ├── confluence/
-    ├── wiki/
-    └── custom/
-```
-
-## Migration Report
-
-After import, a detailed report is generated:
-
-**Location**: `.specweave/docs/internal/projects/{project}/legacy/README.md`
-
-**Contents**:
-- Import summary (counts per category)
-- Classification analysis (with confidence scores)
-- List of imported files
-- Next steps and recommendations
-
-## Configuration Updates
-
-Import history is tracked in `.specweave/config.json`:
-
-```json
-{
-  "brownfield": {
-    "importHistory": [{
-      "source": "notion",
-      "workspace": "acme-corp",
-      "importedAt": "2025-11-06T10:30:00Z",
-      "project": "web-app",
-      "filesImported": 47,
-      "destination": ".specweave/docs/internal/projects/web-app/legacy/notion/"
-    }]
-  }
-}
-```
-
-## After Import
-
-1. **Review classification** - Check migration report
-2. **Move misclassified files** - Use file manager or git
-3. **Update spec numbers** - Rename to `spec-NNN-name.md`
-4. **Clean up legacy** - Delete obsolete content
-5. **Update references** - Fix broken links
-
-## When to Use
-
-- **Migrating from Notion** to SpecWeave
-- **Consolidating wikis** from GitHub, Confluence, etc.
-- **Onboarding brownfield projects** with existing documentation
-- **Merging multiple doc sources** into single SpecWeave instance
-
-## Limitations
-
-- Only markdown files (.md, .markdown) supported
-- No direct API integration (use exports)
-- Classification is heuristic (80%+ accuracy target)
-- Manual review recommended for low-confidence files
-
-## See Also
-
-- `/sw:init-multiproject` - Set up multi-project mode first
-- [Brownfield Import Guide](https://docs.spec-weave.com/guides/brownfield-import)
-- [Migration Best Practices](https://docs.spec-weave.com/guides/migration-best-practices)
-
----
-
-**Implementation**: `src/cli/commands/import-docs.ts`

package/plugins/specweave/commands/migrate-config.md

@@ -1,104 +0,0 @@
----
-description: Migrate .env-only configuration to split secrets/config format
-disable-model-invocation: true
----
-
-Migrate your project from the old .env-only format to the new split format where secrets stay in `.env` (gitignored) and configuration moves to `.specweave/config.json` (committed to git).
-
-**What this command does:**
-
-1. Analyzes your `.env` file
-2. Classifies variables as "secrets" or "config"
-3. Backs up original `.env` file
-4. Updates `.env` (keeps only secrets)
-5. Creates/updates `.specweave/config.json` (adds config)
-6. Generates `.env.example` for team onboarding
-
-**When to use:**
-
-- You're upgrading from SpecWeave v0.23.x or earlier
-- Your `.env` contains both secrets AND configuration (domain, strategy, etc.)
-- You want to share configuration with your team via git
-
-**Command:**
-
-```bash
-node -e "require('./dist/src/cli/commands/migrate-config.js').migrateConfig()"
-```
-
-**Options:**
-
-- `--dry-run`: Preview migration without making changes
-- `--yes`: Skip confirmation prompt
-- `--force`: Force migration even if not needed
-
-**Example output:**
-
-```
-🔄 SpecWeave Configuration Migration
-
-📋 Migration Preview
-
-Classification Results:
-  Secrets: 3 variables
-  Config:  5 variables
-
-📊 Detailed Breakdown:
-
-  Secrets (will stay in .env):
-    JIRA_API_TOKEN=xyzabc***456
-    └─ Contains keyword: token
-
-    JIRA_EMAIL=user@example.com
-    └─ Email address (used for authentication)
-
-  Configuration (will move to config.json):
-    JIRA_DOMAIN=company.atlassian.net
-    └─ Non-sensitive configuration data
-
-    JIRA_STRATEGY=project-per-team
-    └─ Non-sensitive configuration data
-
-✅ Migration Successful!
-
-Summary:
-  ✓ 3 secrets kept in .env
-  ✓ 5 config items moved to config.json
-  ✓ Backup created: .env.backup.1234567890
-  ✓ .env.example generated
-
-📝 Next Steps:
-
-  1. Review .specweave/config.json (commit to git)
-  2. Share .env.example with team (commit to git)
-  3. Team members: cp .env.example .env (fill in tokens)
-```
-
-**Benefits:**
-
-- Team shares configuration via git
-- Secrets stay local (never committed)
-- Type-safe configuration with validation
-- Easy onboarding for new team members
-
-**Classification logic:**
-
-Variables classified as **secrets** (stay in .env):
-- Contains keywords: `token`, `api_token`, `pat`, `secret`, `key`, `password`, `credential`, `auth`
-- Email addresses (used for authentication)
-
-Variables classified as **config** (move to config.json):
-- Everything else: domains, strategies, project keys, organizations, etc.
-
-**Safety:**
-
-- Always creates backup before modifying `.env`
-- Atomic operation (either completes fully or rolls back)
-- Idempotent (can run multiple times safely)
-- Dry-run mode available for preview
-
-**See also:**
-
-- ADR-0050: Secrets vs Configuration Separation
-- `/sw:validate` - Validate configuration after migration
-- Documentation: `CLAUDE.md` → Configuration Management section

package/plugins/specweave/commands/notifications.md

@@ -1,94 +0,0 @@
----
-description: View and manage sync notifications - import completions, discrepancies, sync failures. Filter by type and severity, show details, dismiss notifications.
----
-
-# Notifications Command
-
-View and manage sync notifications - import completions, discrepancies, sync failures, and more.
-
-## Usage
-
-```bash
-/sw:notifications                     # List pending notifications
-/sw:notifications --all               # Include dismissed notifications
-/sw:notifications --type sync-failure # Filter by type
-/sw:notifications --severity warning  # Filter by severity
-/sw:notifications show <id>           # Show notification details
-/sw:notifications dismiss <id>        # Dismiss a notification
-/sw:notifications dismiss-all         # Dismiss all pending notifications
-```
-
-## Arguments
-
-- `--all`: Include dismissed notifications in the list
-- `--type <type>`: Filter by notification type:
-  - `import-complete`: Import job finished
-  - `discrepancy`: Code-spec discrepancy detected
-  - `sync-failure`: Sync operation failed
-  - `drift`: Status drift detected
-  - `job-complete`: Scheduled job finished
-- `--severity <level>`: Filter by severity: `info`, `warning`, `critical`
-- `--json`: Output as JSON for scripting
-
-## Subcommands
-
-### list (default)
-
-Lists notifications with severity emoji, title, and age.
-
-```
-PENDING NOTIFICATIONS (3)
-
-notif-abc123   CRITICAL   GitHub sync failed           2m ago
-notif-def456   WARNING    2 discrepancies in FS-045    1h ago
-notif-ghi789   INFO       107 items imported           3h ago
-
-Use '/sw:notifications show <id>' to view details
-Use '/sw:notifications dismiss <id>' to dismiss
-```
-
-### show <id>
-
-Shows full notification details including data payload.
-
-```
-NOTIFICATION DETAILS
-
-ID:        notif-abc123
-Type:      sync-failure
-Severity:  critical
-Title:     GitHub sync failed
-Message:   Rate limit exceeded. Retry in 15 minutes.
-Created:   2025-12-01 12:00:00 (2m ago)
-
-Data:
-  platform: github
-  error: Rate limit exceeded
-  retryAfter: 900
-```
-
-### dismiss <id>
-
-Dismisses a single notification.
-
-```
-Dismissed notification notif-abc123
-
-Remaining: 2 pending notifications
-```
-
-### dismiss-all
-
-Dismisses all pending notifications with confirmation.
-
-```
-This will dismiss 3 pending notifications.
-Proceed? [y/N]: y
-
-Dismissed 3 notifications
-```
-
-## Related
-
-- `/sw:sync-monitor`: Dashboard showing notification summary
-- `/sw:discrepancies`: View and act on discrepancy notifications