specweave 1.0.261 → 1.0.262

package/plugins/specweave/commands/validate-features.md

@@ -1,207 +0,0 @@
----
-description: Validate feature folder consistency across project folders. Detects orphaned features, missing FEATURE.md, and auto-repairs discrepancies. Use for periodic health checks of living docs structure.
----
-
-# Validate Feature Folder Consistency
-
-Validates that feature folders in project directories (e.g., `specweave/FS-XXX/`) have proper structure.
-
-**Note**: The `_features/` folder is OBSOLETE. Features live in `{project}/FS-XXX/`.
-If you find features in `_features/`, they should be migrated to the correct project folder.
-
----
-
-## STEP 1: Parse Arguments
-
-```
-Arguments: [user's arguments]
-```
-
-**Options**:
-- `--repair`: Auto-repair discrepancies (create missing project folders)
-- `--dry-run`: Show what would be repaired without making changes
-
----
-
-## STEP 2: Run Consistency Validation
-
-**Execute**:
-
-```typescript
-import { FeatureConsistencyValidator } from './dist/src/core/living-docs/feature-consistency-validator.js';
-
-const validator = new FeatureConsistencyValidator(process.cwd(), {
-  defaultProject: 'specweave'
-});
-
-// Parse repair flag
-const autoRepair = process.argv.includes('--repair');
-const dryRun = process.argv.includes('--dry-run');
-
-if (dryRun) {
-  console.log('DRY RUN MODE - No files will be modified\n');
-}
-
-// Run validation
-const result = await validator.validate(autoRepair && !dryRun);
-```
-
----
-
-## STEP 3: Report Results
-
-**Output format**:
-
-```
-===================================================
-FEATURE CONSISTENCY VALIDATION REPORT
-===================================================
-
-Total features scanned: {total}
-Consistent: {consistent}
-Discrepancies found: {discrepancies}
-
----------------------------------------------------
-{if discrepancies > 0}
-DISCREPANCIES FOUND
-
-{for each discrepancy}
-Feature: {featureId}
-Type: {type}
-Description: {description}
-Auto-repairable: {yes/no}
-{if linkedIncrement}
-Linked increment: {incrementId} ({exists/not found})
-{/if}
-
-{/for}
----------------------------------------------------
-{/if}
-
-{if repairs}
-REPAIR RESULTS
-
-{for each repair}
-{SUCCESS/FAILED} {featureId}: {action}
-{if error}   Error: {error}{/if}
-{/for}
-{/if}
-
-===================================================
-```
-
----
-
-## STEP 4: Provide Next Steps
-
-```
-NEXT STEPS
----------------------------------------------------
-
-{if discrepancies > 0 && !repair}
-To auto-repair these discrepancies:
-  /sw:validate-features --repair
-
-This will:
-  - Create missing project folders
-  - Generate README.md files
-  - Link to existing FEATURE.md
-{/if}
-
-{if all repaired}
-All discrepancies have been repaired!
-
-Verify the repairs:
-  ls -la .specweave/docs/internal/specs/specweave/
-{/if}
-
-{if orphaned features}
-Some features could not be auto-repaired.
-
-Manual intervention required for:
-{list orphaned features}
-
-Options:
-  1. Delete orphaned folder if no longer needed
-  2. Re-sync from increment if increment still exists
-  3. Move to correct project folder manually
-{/if}
-```
-
----
-
-## EXAMPLES
-
-### Example 1: Check for discrepancies
-```
-User: /sw:validate-features
-
-Output:
-===================================================
-FEATURE CONSISTENCY VALIDATION REPORT
-===================================================
-
-Total features scanned: 7
-Consistent: 6
-Discrepancies found: 1
-
----------------------------------------------------
-DISCREPANCIES FOUND
-
-Feature: FS-062
-Type: missing_feature_md
-Description: Feature FS-062 folder exists but missing FEATURE.md
-Auto-repairable: Yes
-Linked increment: 0062-test-living-docs-auto-sync (not found)
-
----------------------------------------------------
-
-To repair: /sw:validate-features --repair
-===================================================
-```
-
-### Example 2: Auto-repair discrepancies
-```
-User: /sw:validate-features --repair
-
-Output:
-===================================================
-FEATURE CONSISTENCY VALIDATION REPORT
-===================================================
-
-Total features scanned: 7
-Consistent: 7
-Discrepancies found: 1
-
----------------------------------------------------
-REPAIR RESULTS
-
-SUCCESS FS-062: Created .specweave/docs/internal/specs/specweave/FS-062/README.md
-
-===================================================
-```
-
----
-
-## WHEN TO USE
-
-**Use this command when**:
-- Feature folders are missing FEATURE.md or us-*.md files
-- After interrupted/failed sync operations
-- After manual cleanup of increments
-- Periodic health check of living docs structure
-- Legacy migration from `_features/` to `{project}/` folders
-
-**Root cause of discrepancies**:
-1. Sync interrupted during feature creation
-2. Increment deleted without cleaning up living docs
-3. Manual editing of living docs structure
-4. Legacy `_features/` folders not yet migrated
-
----
-
-## RELATED COMMANDS
-
-- `/sw:sync-specs` - Sync increment to living docs (includes consistency check)
-- `/sw:validate` - Validate increment structure
-- `/sw:archive` - Archive completed increments

package/plugins/specweave/skills/archive-increments/SKILL.md

@@ -1,209 +0,0 @@
----
-description: Intelligent increment archiving expert that analyzes age, status, and activity to recommend archiving. Use when workspace has too many increments, cleaning up completed work, or organizing the _archive folder. Follows the 10-10-10 rule for workspace organization.
-user-invocable: false
----
-
-# Increment Archive Manager
-
-Expert at keeping the `.specweave/increments/` folder clean and organized through intelligent archiving.
-
-## Core Knowledge
-
-### Archiving Philosophy
-
-**The 10-10-10 Rule**:
-- **10 Active**: Keep last 10 increments readily accessible
-- **10 Days**: Archive increments inactive for >10 days
-- **10 Seconds**: Archive operation should take <10 seconds
-
-### Archive Structure
-
-```
-.specweave/increments/
-├── 0023-0032 (Active)          ← Last 10 increments
-├── _archive/                   ← Completed/old increments
-├── _abandoned/                 ← Failed/obsolete increments
-├── _paused/                    ← Paused increments (blocked on dependency)
-└── _backlog/                   ← Planned but not started (future work)
-```
-
-Only these 4 underscore folders are recognized lifecycle folders. Unknown folders (e.g. `_analysis`, `_temp`) are flagged by `specweave doctor` and auto-cleaned by `specweave update`.
-
-### Auto-Archive Trigger (v1.0.257+)
-
-When `archiving.autoArchiveThreshold` (default: 10) numbered increment directories exist:
-- **Interactive mode**: LLM is prompted to suggest `specweave archive --keep-last 10`
-- **Auto mode**: Archiving runs automatically in the background
-- **Rate-limited**: Once per day to avoid noise
-
-### Smart Detection Rules
-
-#### Never Archive
-- **Active increments** (status: active)
-- **Paused increments** (status: paused) - may resume
-- **Recent increments** (last 10 by default)
-- **Increments with open GitHub/JIRA/ADO issues**
-- **Increments with uncommitted changes**
-
-#### Always Archive
-- **Completed >60 days ago**
-- **No activity >30 days** (and status: completed)
-- **Superseded increments** (replaced by newer version)
-- **Failed experiments** (after confirmation)
-
-#### Smart Grouping
-- **Release groups**: Archive all v0.7.x after v0.8.0 ships
-- **Feature groups**: Archive related increments together
-- **Time-based**: Quarter/month-based archiving
-
-## Usage Patterns
-
-### Keep Workspace Clean
-```bash
-# Interactive archiving - prompts for confirmation
-/sw:archive-increments
-
-# Keep only last 5 increments
-/sw:archive-increments --keep-last 5
-
-# Archive all completed increments
-/sw:archive-increments --archive-completed
-```
-
-### Prepare for Release
-```bash
-# Archive all pre-release increments
-/sw:archive-increments --pattern "v0.7"
-
-# Archive by date range
-/sw:archive-increments --older-than 30d
-```
-
-### Restore from Archive
-```bash
-# List archived increments
-/sw:archive-increments --list-archived
-
-# Restore specific increment
-/sw:archive-increments --restore 0015
-```
-
-## Configuration
-
-### Default Settings
-```json
-{
-  "archiving": {
-    "keepLast": 10,              // Keep last 10 increments
-    "autoArchive": false,        // Manual by default
-    "autoArchiveThreshold": 10,  // Suggest archive when >= 10 increments
-    "archiveAfterDays": 60,      // Archive after 60 days
-    "preserveActive": true,      // Never archive active
-    "archiveCompleted": false    // Manual control
-  }
-}
-```
-
-### Aggressive Cleanup
-```json
-{
-  "archiving": {
-    "keepLast": 5,               // Minimal workspace
-    "autoArchive": true,         // Auto-archive on completion
-    "archiveAfterDays": 14,      // Archive after 2 weeks
-    "archiveCompleted": true     // Auto-archive completed
-  }
-}
-```
-
-## Archive Statistics
-
-### Current State Analysis
-When asked about archiving, I analyze:
-- Number of active increments
-- Age of oldest active increment
-- Total size of increments folder
-- Number of completed increments
-- External sync status
-
-### Recommendations
-Based on analysis, I suggest:
-- **Overcrowded** (>20 active): Archive all but last 10
-- **Stale** (many >30 days old): Archive by age
-- **Post-release**: Archive previous version increments
-- **Large size** (>100MB): Archive largest completed increments
-
-## Safety Features
-
-### Pre-Archive Checks
-1. **Metadata validation**: Check increment status
-2. **External sync**: Verify no open issues
-3. **Git status**: Check for uncommitted changes
-4. **Dependencies**: Check if referenced by active increments
-5. **User confirmation**: Show what will be archived
-
-### Archive Operations
-- **Atomic moves**: Use fs.move with overwrite protection
-- **Preserve structure**: Maintain full increment structure
-- **Update references**: Fix links in living docs
-- **Reversible**: Easy restore from archive
-- **Audit trail**: Log all archive operations
-
-## Smart Suggestions
-
-### When to Archive
-- **After major release**: Archive all pre-release increments
-- **Quarterly cleanup**: Archive increments >3 months old
-- **Before new project phase**: Archive previous phase work
-- **Low disk space**: Archive largest completed increments
-
-### Archive Patterns
-- **By version**: `--pattern "v0.7"` (all v0.7.x increments)
-- **By feature**: `--pattern "auth|login"` (auth-related)
-- **By date**: `--older-than 30d` (time-based)
-- **By status**: `--archive-completed` (all completed)
-
-## Integration Points
-
-### Status Line
-- Shows "23-32 (10 active, 22 archived)" format
-- Warns when >15 active increments
-- Suggests archiving when appropriate
-
-### Increment Commands
-- `/sw:done` can trigger auto-archive
-- `/sw:status` shows archive statistics
-- `/sw:next` considers archived increments
-
-### Living Docs
-- Archive preserves living docs references
-- Restore updates living docs links
-- Archive included in docs statistics
-
-## Best Practices
-
-1. **Regular Cleanup**: Archive monthly or after releases
-2. **Keep Recent**: Always keep last 5-10 increments
-3. **Preserve Active**: Never force-archive active work
-4. **Group Related**: Archive feature groups together
-5. **Document Reasons**: Add archive notes for context
-
-## Quick Reference
-
-```bash
-# Archive old increments
-/sw:archive-increments --older-than 30d
-
-# Keep workspace minimal
-/sw:archive-increments --keep-last 5
-
-# Archive after release
-/sw:archive-increments --pattern "pre-release"
-
-# Restore for reference
-/sw:archive-increments --restore 0015
-
-# Check archive stats
-/sw:archive-increments --stats
-```
-