specweave 0.33.5 → 0.34.0

package/plugins/specweave-github/lib/increment-issue-builder.js

@@ -154,14 +154,30 @@ class IncrementIssueBuilder {
     const incrementId = incrementData.frontmatter.increment;
     const title = `[${featureId}][${story.id}] ${story.title}`;
     let body = "";
-    body += `**Feature**: ${featureId}
+    const completedACs = story.acceptanceCriteria.filter((ac) => ac.completed).length;
+    const totalACs = story.acceptanceCriteria.length;
+    const storyTasks = incrementData.tasks.filter(
+      (t) => t.userStories.includes(story.id) || t.userStories.some((us) => us.toUpperCase() === story.id.toUpperCase())
+    );
+    const completedTasks = storyTasks.filter((t) => t.completed).length;
+    const totalTasks = storyTasks.length;
+    const overallPercentage = totalACs + totalTasks > 0 ? Math.round((completedACs + completedTasks) / (totalACs + totalTasks) * 100) : 0;
+    body += `## Progress
+
 `;
-    body += `**Status**: ${incrementData.frontmatter.status || "planning"}
+    body += `**Acceptance Criteria**: ${completedACs}/${totalACs} (${totalACs > 0 ? Math.round(completedACs / totalACs * 100) : 0}%)
 `;
-    body += `**Priority**: P1
+    body += `**Tasks**: ${completedTasks}/${totalTasks} (${totalTasks > 0 ? Math.round(completedTasks / totalTasks * 100) : 0}%)
 `;
-    body += `
----
+    body += `**Overall**: ${overallPercentage}%
+
+`;
+    const filledBlocks = Math.floor(overallPercentage / 5);
+    const emptyBlocks = 20 - filledBlocks;
+    body += `${"\u2588".repeat(filledBlocks)}${"\u2591".repeat(emptyBlocks)} ${overallPercentage}%
+
+`;
+    body += `---
 
 `;
     body += `## User Story
@@ -207,15 +223,12 @@ class IncrementIssueBuilder {
     body += `---
 
 `;
-    const storyTasks = incrementData.tasks.filter(
-      (t) => t.userStories.includes(story.id) || t.userStories.some((us) => us.toUpperCase() === story.id.toUpperCase())
-    );
     if (storyTasks.length > 0) {
       body += `## Tasks
 
 `;
-      const completedTasks = storyTasks.filter((t) => t.completed).length;
-      body += `Progress: ${completedTasks}/${storyTasks.length} tasks
+      const completedTasks2 = storyTasks.filter((t) => t.completed).length;
+      body += `Progress: ${completedTasks2}/${storyTasks.length} tasks
 
 `;
       for (const task of storyTasks) {

package/plugins/specweave-github/lib/increment-issue-builder.ts

@@ -287,11 +287,34 @@ export class IncrementIssueBuilder {
     // Build body
     let body = '';
 
-    // Header with metadata
-    body += `**Feature**: ${featureId}\n`;
-    body += `**Status**: ${incrementData.frontmatter.status || 'planning'}\n`;
-    body += `**Priority**: P1\n`;
-    body += `\n---\n\n`;
+    // ❌ REMOVED: Metadata header (Feature, Status, Priority)
+    // WHY: GitHub has NATIVE fields for this (labels, milestones)
+    // Body should contain ONLY actual work content (ACs, tasks, user story)
+    // See: .specweave/docs/internal/troubleshooting/CRITICAL-remove-metadata-header-from-github-issues.md
+
+    // Progress section (consistency with user-story-issue-builder.ts)
+    const completedACs = story.acceptanceCriteria.filter(ac => ac.completed).length;
+    const totalACs = story.acceptanceCriteria.length;
+    const storyTasks = incrementData.tasks.filter(t =>
+      t.userStories.includes(story.id) ||
+      t.userStories.some(us => us.toUpperCase() === story.id.toUpperCase())
+    );
+    const completedTasks = storyTasks.filter(t => t.completed).length;
+    const totalTasks = storyTasks.length;
+    const overallPercentage = (totalACs + totalTasks) > 0
+      ? Math.round(((completedACs + completedTasks) / (totalACs + totalTasks)) * 100)
+      : 0;
+
+    body += `## Progress\n\n`;
+    body += `**Acceptance Criteria**: ${completedACs}/${totalACs} (${totalACs > 0 ? Math.round((completedACs / totalACs) * 100) : 0}%)\n`;
+    body += `**Tasks**: ${completedTasks}/${totalTasks} (${totalTasks > 0 ? Math.round((completedTasks / totalTasks) * 100) : 0}%)\n`;
+    body += `**Overall**: ${overallPercentage}%\n\n`;
+
+    // Progress bar
+    const filledBlocks = Math.floor(overallPercentage / 5);
+    const emptyBlocks = 20 - filledBlocks;
+    body += `${'█'.repeat(filledBlocks)}${'░'.repeat(emptyBlocks)} ${overallPercentage}%\n\n`;
+    body += `---\n\n`;
 
     // User Story description
     body += `## User Story\n\n`;
@@ -324,12 +347,7 @@ export class IncrementIssueBuilder {
 
     body += `---\n\n`;
 
-    // Tasks for this user story
-    const storyTasks = incrementData.tasks.filter(t =>
-      t.userStories.includes(story.id) ||
-      t.userStories.some(us => us.toUpperCase() === story.id.toUpperCase())
-    );
-
+    // Tasks for this user story (already calculated above for Progress section)
     if (storyTasks.length > 0) {
       body += `## Tasks\n\n`;
       const completedTasks = storyTasks.filter(t => t.completed).length;

package/plugins/specweave-github/lib/user-story-content-builder.js

@@ -40,25 +40,28 @@ class UserStoryContentBuilder {
   async buildIssueBody(githubRepo) {
     const content = await this.parse();
     let body = "";
-    const priority = this.extractPriorityFromACs(content.acceptanceCriteria);
     const repo = githubRepo || await this.detectGitHubRepo();
-    if (repo) {
-      const pathMatch = this.userStoryPath.match(/specs\/([^/]+)\/FS-\d+\//);
-      const projectFolder = pathMatch ? pathMatch[1] : "default";
-      body += `**Feature**: [${content.featureId}](https://github.com/${repo}/tree/develop/.specweave/docs/internal/specs/${projectFolder}/${content.featureId})
+    const completedACs = content.acceptanceCriteria.filter((ac) => ac.completed).length;
+    const totalACs = content.acceptanceCriteria.length;
+    const completedTasks = content.tasks.filter((t) => t.status).length;
+    const totalTasks = content.tasks.length;
+    const overallPercentage = totalACs + totalTasks > 0 ? Math.round((completedACs + completedTasks) / (totalACs + totalTasks) * 100) : 0;
+    body += `## Progress
+
 `;
-    } else {
-      body += `**Feature**: ${content.featureId}
+    body += `**Acceptance Criteria**: ${completedACs}/${totalACs} (${totalACs > 0 ? Math.round(completedACs / totalACs * 100) : 0}%)
 `;
-    }
-    body += `**Status**: ${content.frontmatter.status}
+    body += `**Tasks**: ${completedTasks}/${totalTasks} (${totalTasks > 0 ? Math.round(completedTasks / totalTasks * 100) : 0}%)
 `;
-    if (priority) {
-      body += `**Priority**: ${priority}
+    body += `**Overall**: ${overallPercentage}%
+
 `;
-    }
-    body += `
----
+    const filledBlocks = Math.floor(overallPercentage / 5);
+    const emptyBlocks = 20 - filledBlocks;
+    body += `${"\u2588".repeat(filledBlocks)}${"\u2591".repeat(emptyBlocks)} ${overallPercentage}%
+
+`;
+    body += `---
 
 `;
     body += `## User Story
@@ -99,9 +102,9 @@ class UserStoryContentBuilder {
 `;
       for (const ac of content.acceptanceCriteria) {
         const checkbox = ac.completed ? "[x]" : "[ ]";
-        const priority2 = ac.priority ? ` (${ac.priority})` : "";
+        const priority = ac.priority ? ` (${ac.priority})` : "";
         const testable = ac.testable ? " [testable]" : "";
-        body += `- ${checkbox} **${ac.id}**: ${ac.description}${priority2}${testable}
+        body += `- ${checkbox} **${ac.id}**: ${ac.description}${priority}${testable}
 `;
       }
       body += "\n";

package/plugins/specweave-github/lib/user-story-content-builder.ts

@@ -116,28 +116,33 @@ export class UserStoryContentBuilder {
 
     let body = '';
 
-    // Extract priority from ACs (highest priority wins)
-    const priority = this.extractPriorityFromACs(content.acceptanceCriteria);
-
     // Detect GitHub repo from git remote if not provided
     const repo = githubRepo || await this.detectGitHubRepo();
 
-    // Header with metadata
-    // v5.0.0+: Features live in project folders, NOT _features
-    // Extract project from path: specs/{project}/FS-XXX/us-*.md
-    if (repo) {
-      const pathMatch = this.userStoryPath.match(/specs\/([^/]+)\/FS-\d+\//);
-      const projectFolder = pathMatch ? pathMatch[1] : 'default';
-      body += `**Feature**: [${content.featureId}](https://github.com/${repo}/tree/develop/.specweave/docs/internal/specs/${projectFolder}/${content.featureId})\n`;
-    } else {
-      body += `**Feature**: ${content.featureId}\n`;
-    }
-    body += `**Status**: ${content.frontmatter.status}\n`;
-    if (priority) {
-      body += `**Priority**: ${priority}\n`;
-    }
-
-    body += `\n---\n\n`;
+    // ❌ REMOVED: Metadata header (Feature, Status, Priority)
+    // WHY: GitHub has NATIVE fields for this (labels, milestones)
+    // Body should contain ONLY actual work content (ACs, tasks, user story)
+    // See: .specweave/docs/internal/troubleshooting/CRITICAL-remove-metadata-header-from-github-issues.md
+
+    // Progress section (consistency with user-story-issue-builder.ts)
+    const completedACs = content.acceptanceCriteria.filter(ac => ac.completed).length;
+    const totalACs = content.acceptanceCriteria.length;
+    const completedTasks = content.tasks.filter(t => t.status).length;
+    const totalTasks = content.tasks.length;
+    const overallPercentage = (totalACs + totalTasks) > 0
+      ? Math.round(((completedACs + completedTasks) / (totalACs + totalTasks)) * 100)
+      : 0;
+
+    body += `## Progress\n\n`;
+    body += `**Acceptance Criteria**: ${completedACs}/${totalACs} (${totalACs > 0 ? Math.round((completedACs / totalACs) * 100) : 0}%)\n`;
+    body += `**Tasks**: ${completedTasks}/${totalTasks} (${totalTasks > 0 ? Math.round((completedTasks / totalTasks) * 100) : 0}%)\n`;
+    body += `**Overall**: ${overallPercentage}%\n\n`;
+
+    // Progress bar
+    const filledBlocks = Math.floor(overallPercentage / 5);
+    const emptyBlocks = 20 - filledBlocks;
+    body += `${'█'.repeat(filledBlocks)}${'░'.repeat(emptyBlocks)} ${overallPercentage}%\n\n`;
+    body += `---\n\n`;
 
     // User Story description
     body += `## User Story\n\n`;

package/plugins/specweave-github/lib/user-story-issue-builder.js

@@ -12,10 +12,10 @@ This prevents incorrect issue titles like [undefined][US-XXX] or [SP-US-XXX].
 Provide the correct Feature ID (e.g., "FS-047") when constructing this builder.`
       );
     }
-    if (!/^FS-\d{3,}$/.test(featureId)) {
+    if (!/^FS-\d{3,}E?$/.test(featureId)) {
       throw new Error(
         `UserStoryIssueBuilder: Invalid featureId format "${featureId}".
-Expected format: FS-XXX (e.g., "FS-047", "FS-123", "FS-1000").
+Expected format: FS-XXX or FS-XXXE (e.g., "FS-047", "FS-123E", "FS-1000").
 This prevents incorrect issue titles like [SP-US-XXX] or [${featureId}][US-XXX].`
       );
     }
@@ -43,11 +43,11 @@ This prevents incorrect issue titles like [SP-US-XXX] or [${featureId}][US-XXX].
     const acceptanceCriteria = this.extractAcceptanceCriteria(bodyContent);
     const tasks = await this.extractTasks(bodyContent, frontmatter.id);
     const title = `[${this.featureId}][${frontmatter.id}] ${frontmatter.title}`;
-    const titlePattern = /^\[FS-\d{3,}\]\[US-\d{3,}\] .+$/;
+    const titlePattern = /^\[FS-\d{3,}E?\]\[US-\d{3,}E?\] .+$/;
     if (!titlePattern.test(title)) {
       throw new Error(
         `Generated issue title has incorrect format: "${title}"
-Expected: [FS-XXX][US-YYY] Title (3+ digits each)
+Expected: [FS-XXX][US-YYY] or [FS-XXXE][US-YYYE] Title (3+ digits each, E-suffix for external)
 This indicates a bug in UserStoryIssueBuilder or invalid frontmatter.
 Feature ID: ${this.featureId}
 User Story ID: ${frontmatter.id}`
@@ -235,13 +235,6 @@ User Story ID: ${frontmatter.id}`
       data.acceptanceCriteria,
       data.tasks
     );
-    sections.push(`**Feature**: ${this.featureId}`);
-    sections.push(`**Status**: ${this.capitalize(data.frontmatter.status)}`);
-    sections.push(`**Priority**: ${data.frontmatter.priority || "P2"}`);
-    if (data.frontmatter.project && data.frontmatter.project !== "default") {
-      sections.push(`**Project**: ${data.frontmatter.project}`);
-    }
-    sections.push("");
     sections.push(IssueStateManager.formatProgressMarkdown(progress));
     sections.push("");
     if (data.userStoryStatement) {
@@ -356,6 +349,9 @@ User Story ID: ${frontmatter.id}`
    *
    * CRITICAL: Label names must match repository labels exactly!
    * Repository uses: status:complete, status:active, status:not_started
+   *
+   * v0.35.0: Project derived from frontmatter.project in us-*.md files.
+   * Living docs sync transforms spec.md **Project**: → us-*.md frontmatter project:
    */
   buildLabels(frontmatter) {
     const labels = ["user-story", "specweave"];
@@ -382,8 +378,9 @@ User Story ID: ${frontmatter.id}`
     if (frontmatter.priority) {
       labels.push(frontmatter.priority.toLowerCase());
     }
-    if (frontmatter.project && frontmatter.project !== "default") {
-      labels.push(`project:${frontmatter.project}`);
+    const project = frontmatter.project?.toLowerCase();
+    if (project && project !== "default") {
+      labels.push(`project:${project}`);
     }
     return labels;
   }

package/plugins/specweave-github/lib/user-story-issue-builder.ts

@@ -65,11 +65,11 @@ export class UserStoryIssueBuilder {
       );
     }
 
-    // ✅ VALIDATION: Ensure featureId matches expected pattern (FS-XXX, 3+ digits)
-    if (!/^FS-\d{3,}$/.test(featureId)) {
+    // ✅ VALIDATION: Ensure featureId matches expected pattern (FS-XXX or FS-XXXE for external)
+    if (!/^FS-\d{3,}E?$/.test(featureId)) {
       throw new Error(
         `UserStoryIssueBuilder: Invalid featureId format "${featureId}".\n` +
-        `Expected format: FS-XXX (e.g., "FS-047", "FS-123", "FS-1000").\n` +
+        `Expected format: FS-XXX or FS-XXXE (e.g., "FS-047", "FS-123E", "FS-1000").\n` +
         `This prevents incorrect issue titles like [SP-US-XXX] or [${featureId}][US-XXX].`
       );
     }
@@ -115,11 +115,11 @@ export class UserStoryIssueBuilder {
     const title = `[${this.featureId}][${frontmatter.id}] ${frontmatter.title}`;
 
     // ✅ SAFETY CHECK: Ensure title matches expected pattern (3+ digits)
-    const titlePattern = /^\[FS-\d{3,}\]\[US-\d{3,}\] .+$/;
+    const titlePattern = /^\[FS-\d{3,}E?\]\[US-\d{3,}E?\] .+$/;
     if (!titlePattern.test(title)) {
       throw new Error(
         `Generated issue title has incorrect format: "${title}"\n` +
-        `Expected: [FS-XXX][US-YYY] Title (3+ digits each)\n` +
+        `Expected: [FS-XXX][US-YYY] or [FS-XXXE][US-YYYE] Title (3+ digits each, E-suffix for external)\n` +
         `This indicates a bug in UserStoryIssueBuilder or invalid frontmatter.\n` +
         `Feature ID: ${this.featureId}\n` +
         `User Story ID: ${frontmatter.id}`
@@ -135,7 +135,7 @@ export class UserStoryIssueBuilder {
       bodyContent
     });
 
-    // 5. Determine labels
+    // 5. Determine labels (v0.35.0: project from frontmatter, not body)
     const labels = this.buildLabels(frontmatter);
 
     return {
@@ -397,17 +397,12 @@ export class UserStoryIssueBuilder {
       data.tasks
     );
 
-    // Header with metadata
-    sections.push(`**Feature**: ${this.featureId}`);
-    sections.push(`**Status**: ${this.capitalize(data.frontmatter.status)}`);
-    sections.push(`**Priority**: ${data.frontmatter.priority || 'P2'}`);
-    // ✅ FIX: Only output Project if defined and not "default"
-    if (data.frontmatter.project && data.frontmatter.project !== 'default') {
-      sections.push(`**Project**: ${data.frontmatter.project}`);
-    }
-    sections.push('');
+    // ❌ REMOVED: Metadata header (Feature, Status, Priority, Project)
+    // WHY: GitHub has NATIVE fields for this (labels, milestones)
+    // Body should contain ONLY actual work content (ACs, tasks, user story)
+    // See: .specweave/docs/internal/troubleshooting/CRITICAL-remove-metadata-header-from-github-issues.md
 
-    // Progress section (NEW)
+    // Progress section
     sections.push(IssueStateManager.formatProgressMarkdown(progress));
     sections.push('');
 
@@ -568,6 +563,9 @@ export class UserStoryIssueBuilder {
    *
    * CRITICAL: Label names must match repository labels exactly!
    * Repository uses: status:complete, status:active, status:not_started
+   *
+   * v0.35.0: Project derived from frontmatter.project in us-*.md files.
+   * Living docs sync transforms spec.md **Project**: → us-*.md frontmatter project:
    */
   private buildLabels(frontmatter: UserStoryFrontmatter): string[] {
     const labels: string[] = ['user-story', 'specweave'];
@@ -607,9 +605,12 @@ export class UserStoryIssueBuilder {
       labels.push(frontmatter.priority.toLowerCase());
     }
 
-    // Add project label
-    if (frontmatter.project && frontmatter.project !== 'default') {
-      labels.push(`project:${frontmatter.project}`);
+    // Add project label (v0.35.0: extract from frontmatter.project in us-*.md files)
+    // Living docs sync transforms spec.md **Project**: → us-*.md frontmatter project:
+    // See CLAUDE.md "Two File Formats for Project Field" for architecture
+    const project = frontmatter.project?.toLowerCase();
+    if (project && project !== 'default') {
+      labels.push(`project:${project}`);
     }
 
     return labels;

package/plugins/specweave-github/reference/github-specweave-mapping.md

@@ -295,7 +295,7 @@ Body: We need OAuth2 authentication with Google and GitHub providers...
 
 ### Example 3: Close Increment → Close Issue
 
-**SpecWeave**: `/specweave:done 0004` (all 48 tasks complete)
+**SpecWeave**: `/sw:done 0004` (all 48 tasks complete)
 
 **GitHub**: Close issue #130 with comment:
 ```markdown

package/plugins/specweave-github/skills/github-issue-standard/SKILL.md

@@ -190,9 +190,9 @@ All GitHub issue content is generated by these builders:
 
 All GitHub sync commands use the Universal Hierarchy:
 
-- `/specweave-github:sync` - Sync increments via Feature/UserStory hierarchy
-- `/specweave-github:create-issue` - Create issue using standard format
-- `/specweave-github:update-user-story` - Update user story issue
+- `/sw-github:sync` - Sync increments via Feature/UserStory hierarchy
+- `/sw-github:create-issue` - Create issue using standard format
+- `/sw-github:update-user-story` - Update user story issue
 
 ## Validation Checklist
 

package/plugins/specweave-github/skills/github-issue-tracker/SKILL.md

@@ -14,7 +14,7 @@ description: Task-level GitHub issue tracking for SpecWeave increments. Provides
 - Blocking issue tracking
 - Task-level comments and discussions
 
-**Integration**: Works with `github-sync` skill and `/specweave:github:*` commands
+**Integration**: Works with `github-sync` skill and `/sw:github:*` commands
 
 ---
 
@@ -171,7 +171,7 @@ plugins:
 ### Check Task Status
 
 ```bash
-/specweave:github:status 0004
+/sw:github:status 0004
 ```
 
 Output:
@@ -196,7 +196,7 @@ Week 1: Foundation
 ### Sync Task Checklist
 
 ```bash
-/specweave:github:sync 0004 --tasks
+/sw:github:sync 0004 --tasks
 ```
 
 Updates GitHub issue checklist to match current increment progress.
@@ -204,7 +204,7 @@ Updates GitHub issue checklist to match current increment progress.
 ### Comment on Task
 
 ```bash
-/specweave:github:comment 0004 T-008 "Cursor adapter completed, moving to testing phase"
+/sw:github:comment 0004 T-008 "Cursor adapter completed, moving to testing phase"
 ```
 
 Posts custom comment to GitHub issue for specific task.
@@ -308,7 +308,7 @@ tasks:
 Generate time reports:
 
 ```bash
-/specweave:github:time-report 0004
+/sw:github:time-report 0004
 ```
 
 Output:
@@ -458,7 +458,7 @@ Warn when tasks are behind schedule:
 **Checklist not updating?**
 - Verify `update_checklist: true` in config
 - Check GitHub API permissions (repo write access)
-- Manually sync: `/specweave:github:sync 0004 --tasks`
+- Manually sync: `/sw:github:sync 0004 --tasks`
 
 **Comments not posting?**
 - Check `post_task_comments: true`
@@ -468,7 +468,7 @@ Warn when tasks are behind schedule:
 **Time tracking inaccurate?**
 - Verify task timestamps in `.metadata.yaml`
 - Check for manual edits to metadata
-- Re-sync: `/specweave:github:sync 0004 --force`
+- Re-sync: `/sw:github:sync 0004 --force`
 
 ---
 
@@ -488,7 +488,7 @@ Warn when tasks are behind schedule:
 
 - **github-sync**: High-level increment ↔ issue synchronization
 - **github-manager agent**: AI agent for GitHub operations
-- **Commands**: All `/specweave:github:*` commands
+- **Commands**: All `/sw:github:*` commands
 
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 name: github-sync
-description: Two-way synchronization between SpecWeave specs and GitHub Projects (push & pull by default). Activates ONLY when user asks questions about GitHub integration or needs help configuring GitHub sync. Does NOT activate for slash commands. For syncing, use /specweave-github:sync-spec command instead.
+description: Two-way synchronization between SpecWeave specs and GitHub Projects (push & pull by default). Activates ONLY when user asks questions about GitHub integration or needs help configuring GitHub sync. Does NOT activate for slash commands. For syncing, use /sw-github:sync-spec command instead.
 ---
 
 # GitHub Sync - Two-way Spec ↔ Project Synchronization
@@ -9,7 +9,7 @@ description: Two-way synchronization between SpecWeave specs and GitHub Projects
 
 **Default Behavior**: **Two-way sync** (push & pull) - Changes in either system are automatically synchronized
 
-**⚠️ IMPORTANT**: This skill provides HELP and GUIDANCE about GitHub sync. For actual syncing, users should use the `/specweave-github:sync-spec` command directly. This skill should NOT auto-activate when the command is being invoked.
+**⚠️ IMPORTANT**: This skill provides HELP and GUIDANCE about GitHub sync. For actual syncing, users should use the `/sw-github:sync-spec` command directly. This skill should NOT auto-activate when the command is being invoked.
 
 ## When to Activate
 
@@ -20,11 +20,11 @@ description: Two-way synchronization between SpecWeave specs and GitHub Projects
 - User needs help configuring GitHub integration
 
 ❌ **Do NOT activate when**:
-- User invokes `/specweave-github:sync-spec` command (command handles it)
+- User invokes `/sw-github:sync-spec` command (command handles it)
 - Command is already running (avoid duplicate invocation)
 - Task completion hook is syncing (automatic process)
 
-**Integration**: Works with `/specweave-github:sync-spec` command
+**Integration**: Works with `/sw-github:sync-spec` command
 
 ---
 
@@ -176,7 +176,7 @@ As a developer, I want to install SpecWeave via NPM so that I can use it in my p
 
 **Use Case**: Import existing GitHub Projects as SpecWeave specs
 
-**Command**: `/specweave-github:import-project <project-number>`
+**Command**: `/sw-github:import-project <project-number>`
 
 **Actions**:
 1. Fetch project via GitHub GraphQL API
@@ -238,7 +238,7 @@ gh auth status
 ### Sync Spec to GitHub
 
 ```bash
-/specweave-github:sync-spec spec-001
+/sw-github:sync-spec spec-001
 ```
 
 Creates or updates GitHub Project for spec-001.
@@ -246,7 +246,7 @@ Creates or updates GitHub Project for spec-001.
 ### Sync All Specs
 
 ```bash
-/specweave-github:sync-spec --all
+/sw-github:sync-spec --all
 ```
 
 Syncs all specs to GitHub Projects.
@@ -254,7 +254,7 @@ Syncs all specs to GitHub Projects.
 ### Import Project
 
 ```bash
-/specweave-github:import-project 123
+/sw-github:import-project 123
 ```
 
 Imports GitHub Project #123 as a SpecWeave spec.
@@ -262,7 +262,7 @@ Imports GitHub Project #123 as a SpecWeave spec.
 ### Check Status
 
 ```bash
-/specweave-github:status spec-001
+/sw-github:status spec-001
 ```
 
 Shows sync status (project ID, last sync time, progress %).
@@ -283,11 +283,11 @@ PM: Creates .specweave/docs/internal/specs/spec-005-user-auth.md
 → Issues created for each user story
 
 # 3. Implement increments
-/specweave:increment "Add login flow"
+/sw:increment "Add login flow"
 → Increment 0010 created (implements US-001, US-002)
 
 # 4. Work on tasks
-/specweave:do
+/sw:do
 → Task completed
 → Hook fires
 → Spec updated (AC marked complete)
@@ -328,7 +328,7 @@ The spec is always the source of truth. GitHub Projects are a mirror for visibil
 2. Manual edits to project/issue body/title
 
 **Resolution**:
-- Run `/specweave-github:sync-spec spec-001 --force` to overwrite project from spec
+- Run `/sw-github:sync-spec spec-001 --force` to overwrite project from spec
 - Or manually update spec metadata to match project
 
 ---
@@ -386,7 +386,7 @@ The spec is always the source of truth. GitHub Projects are a mirror for visibil
 **Progress not updating?**
 - Check `autoSyncSpecs: true` in config
 - Verify hook execution: `.specweave/logs/hooks-debug.log`
-- Manually sync: `/specweave-github:sync-spec spec-001`
+- Manually sync: `/sw-github:sync-spec spec-001`
 
 ---
 
@@ -462,7 +462,7 @@ For monorepos with multiple GitHub repositories:
 
 - **github-issue-tracker**: Track individual tasks as issue comments (DEPRECATED - use spec sync instead)
 - **github-manager agent**: AI agent for GitHub operations
-- **Commands**: `/specweave-github:sync-spec`, `/specweave-github:import-project`, `/specweave-github:status`
+- **Commands**: `/sw-github:sync-spec`, `/sw-github:import-project`, `/sw-github:status`
 
 ---
 

package/plugins/specweave-infrastructure/.claude-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
-  "name": "specweave-infrastructure",
+  "name": "sw-infra",
   "description": "Cloud infrastructure provisioning and monitoring. Includes Hetzner Cloud provisioning, Prometheus/Grafana setup, distributed tracing (Jaeger/Tempo), and SLO implementation. Focus on cost-effective, production-ready infrastructure.",
   "version": "0.24.0",
   "author": {

package/plugins/specweave-infrastructure/commands/{specweave-infrastructure-monitor-setup.md → monitor-setup.md}

@@ -1,5 +1,5 @@
 ---
-name: specweave-infrastructure:monitor-setup
+name: sw-infra:monitor-setup
 description: Set up comprehensive monitoring and observability with Prometheus, Grafana, distributed tracing, and log aggregation
 ---
 

package/plugins/specweave-infrastructure/commands/{specweave-infrastructure-slo-implement.md → slo-implement.md}

@@ -1,5 +1,5 @@
 ---
-name: specweave-infrastructure:slo-implement
+name: sw-infra:slo-implement
 description: Implement Service Level Objectives (SLOs) with reliability standards, SLIs, and error budget-based engineering practices
 ---
 

package/plugins/specweave-jira/.claude-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
-  "name": "specweave-jira",
+  "name": "sw-jira",
   "description": "JIRA integration for SpecWeave increments. Bidirectional sync between SpecWeave increments and JIRA epics/stories. Automatically creates JIRA issues from increments, tracks progress, and updates status.",
   "version": "0.24.0",
   "author": {

package/plugins/specweave-jira/agents/jira-sync-judge/AGENT.md

@@ -58,7 +58,7 @@ if (localStatus !== externalStatus) {
    - MUST be 100% complete to close
    - All tasks completed
    - All tests passing
-   - `/specweave:done` validates strictly
+   - `/sw:done` validates strictly
    - Can be deleted after completion
 
 2. **Spec Lifecycle** (Flexible):
@@ -85,7 +85,7 @@ Verify hooks fire correctly:
 
 ```bash
 # Check 1: Post-increment completion
-Event: /specweave:done completes
+Event: /sw:done completes
 Expected: Living docs updated → Sync triggered
 Validate:
   - Hook fires within 5 seconds
@@ -294,7 +294,7 @@ Timeline:
   Day 3:
     - All tasks complete
     - Tests passing
-    - /specweave:done executed
+    - /sw:done executed
     - Increment: closed
     - JIRA status: In Progress (from JIRA)
     - Spec status: in_progress (from JIRA)