specweave 0.33.4 → 0.33.6

package/plugins/specweave/skills/SKILLS-INDEX.md

@@ -31,7 +31,7 @@
 
 | Skill | Triggers | Location |
 |-------|----------|----------|
-| **increment-quality-judge-v2** | quality check, assess spec, risk assessment, qa check, quality gate, /specweave:qa, validate quality, evaluate increment | `skills/increment-quality-judge-v2/SKILL.md` |
+| **increment-quality-judge-v2** | quality check, assess spec, risk assessment, qa check, quality gate, /sw:qa, validate quality, evaluate increment | `skills/increment-quality-judge-v2/SKILL.md` |
 | **pm-closure-validation** | /done, close increment, validate increment, completion check, quality gate, PM approval, ready to close, scope creep | `skills/pm-closure-validation/SKILL.md` |
 | **code-reviewer** | code review, security vulnerabilities, performance optimization, static analysis, code quality, pull request review | `skills/code-reviewer/SKILL.md` |
 | **code-standards-analyzer** | coding standards, conventions, code style, naming conventions, linting rules, best practices, standards audit, anti-patterns | `skills/code-standards-analyzer/SKILL.md` |
@@ -42,15 +42,15 @@
 | Skill | Triggers | Location |
 |-------|----------|----------|
 | **external-sync-wizard** | GitHub sync, Jira integration, Azure DevOps, ADO, issue tracking sync, bidirectional sync, import issues, export increments | `skills/external-sync-wizard/SKILL.md` |
-| **progress-sync** | sync progress, update progress, sync everything, sync all systems, sync to GitHub, sync to JIRA, /specweave:sync-progress | `skills/progress-sync/SKILL.md` |
+| **progress-sync** | sync progress, update progress, sync everything, sync all systems, sync to GitHub, sync to JIRA, /sw:sync-progress | `skills/progress-sync/SKILL.md` |
 | **multi-project-spec-mapper** | multi-project, project mapping, spec splitting, JIRA projects, multiple projects, microservices, FE/BE/MOBILE split | `skills/multi-project-spec-mapper/SKILL.md` |
 
 ### Framework & Context
 
 | Skill | Triggers | Location |
 |-------|----------|----------|
-| **specweave-detector** | slash commands, /specweave:increment, /specweave:do, /specweave:progress, /specweave:done, specweave commands, workflow help | `skills/specweave-detector/SKILL.md` |
-| **specweave-framework** | specweave rules, how does specweave work, framework structure, increment lifecycle, source of truth, tasks.md format | `skills/specweave-framework/SKILL.md` |
+| **detector** | slash commands, /sw:increment, /sw:do, /sw:progress, /sw:done, specweave commands, workflow help | `skills/detector/SKILL.md` |
+| **framework** | specweave rules, how does specweave work, framework structure, increment lifecycle, source of truth, tasks.md format | `skills/framework/SKILL.md` |
 | **context-loader** | context loading, progressive disclosure, token efficiency, sub-agents, context management, how SpecWeave scales | `skills/context-loader/SKILL.md` |
 | **context-optimizer** | optimize context, reduce tokens, clean context, smart context, precision loading, 80% reduction | `skills/context-optimizer/SKILL.md` |
 | **plugin-validator** | plugin validation, validate plugins, check plugins, specweave init, fresh setup, marketplace registration | `skills/plugin-validator/SKILL.md` |

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

@@ -52,31 +52,31 @@ Expert at keeping the `.specweave/increments/` folder clean and organized throug
 ### Keep Workspace Clean
 ```bash
 # Interactive archiving - prompts for confirmation
-/specweave:archive-increments
+/sw:archive-increments
 
 # Keep only last 5 increments
-/specweave:archive-increments --keep-last 5
+/sw:archive-increments --keep-last 5
 
 # Archive all completed increments
-/specweave:archive-increments --archive-completed
+/sw:archive-increments --archive-completed
 ```
 
 ### Prepare for Release
 ```bash
 # Archive all pre-release increments
-/specweave:archive-increments --pattern "v0.7"
+/sw:archive-increments --pattern "v0.7"
 
 # Archive by date range
-/specweave:archive-increments --older-than 30d
+/sw:archive-increments --older-than 30d
 ```
 
 ### Restore from Archive
 ```bash
 # List archived increments
-/specweave:archive-increments --list-archived
+/sw:archive-increments --list-archived
 
 # Restore specific increment
-/specweave:archive-increments --restore 0015
+/sw:archive-increments --restore 0015
 ```
 
 ## Configuration
@@ -161,9 +161,9 @@ Based on analysis, I suggest:
 - Suggests archiving when appropriate
 
 ### Increment Commands
-- `/specweave:done` can trigger auto-archive
-- `/specweave:status` shows archive statistics
-- `/specweave:next` considers archived increments
+- `/sw:done` can trigger auto-archive
+- `/sw:status` shows archive statistics
+- `/sw:next` considers archived increments
 
 ### Living Docs
 - Archive preserves living docs references
@@ -182,17 +182,17 @@ Based on analysis, I suggest:
 
 ```bash
 # Archive old increments
-/specweave:archive-increments --older-than 30d
+/sw:archive-increments --older-than 30d
 
 # Keep workspace minimal
-/specweave:archive-increments --keep-last 5
+/sw:archive-increments --keep-last 5
 
 # Archive after release
-/specweave:archive-increments --pattern "pre-release"
+/sw:archive-increments --pattern "pre-release"
 
 # Restore for reference
-/specweave:archive-increments --restore 0015
+/sw:archive-increments --restore 0015
 
 # Check archive stats
-/specweave:archive-increments --stats
+/sw:archive-increments --stats
 ```

package/plugins/specweave/skills/brownfield-analyzer/SKILL.md

@@ -166,7 +166,7 @@ grep -rh "^import" src/ | sort | uniq -c | sort -rn | head -10
 ## Phase 2: First Increment (1-3 days)
 - [ ] Select first feature to modify
 - [ ] Document module before touching
-- [ ] Create increment with /specweave:increment
+- [ ] Create increment with /sw:increment
 - [ ] Implement changes
 - [ ] Update docs
 
@@ -273,7 +273,7 @@ grep -r "jira" . --include="*.md" | head -5
 **3. Sync strategy**:
 ```bash
 # Option 1: Import existing Jira items
-/specweave-jira:sync --import
+/sw-jira:sync --import
 
 # Option 2: Start fresh, sync new work only
 # (Use SpecWeave as source of truth)
@@ -288,7 +288,7 @@ grep -r "jira" . --include="*.md" | head -5
 
 **Sync**:
 ```bash
-/specweave-ado:sync --import
+/sw-ado:sync --import
 ```
 
 ### GitHub Issues → SpecWeave
@@ -300,7 +300,7 @@ grep -r "jira" . --include="*.md" | head -5
 
 **Sync**:
 ```bash
-/specweave-github:sync --import
+/sw-github:sync --import
 ```
 
 ---
@@ -342,7 +342,7 @@ Week 1: Setup (2 hours)
 Week 1-2: First Increment
 - Select first feature: "Add rate limiting"
 - Document rate-limiting module
-- Create increment with /specweave:increment
+- Create increment with /sw:increment
 - Implement with TDD
 - Update docs
 

package/plugins/specweave/skills/code-standards-analyzer/SKILL.md

@@ -208,7 +208,7 @@ Coding Standards: .specweave/docs/internal/governance/coding-standards.md
 **Optional**: Re-analyze on increment done
 
 ```bash
-/specweave:done 0046 --update-standards
+/sw:done 0046 --update-standards
 ```
 
 ---
@@ -310,13 +310,13 @@ Full standards: .specweave/docs/internal/governance/coding-standards.md"
 
 ```bash
 # Full analysis
-/specweave:analyze-standards
+/sw:analyze-standards
 
 # Drift detection only
-/specweave:analyze-standards --drift
+/sw:analyze-standards --drift
 
 # Update existing standards
-/specweave:analyze-standards --update
+/sw:analyze-standards --update
 ```
 
 ---

package/plugins/specweave/skills/context-loader/SKILL.md

@@ -232,7 +232,7 @@ SpecWeave's **role-orchestrator** skill automatically:
 **Example:**
 
 ```
-User: "/specweave:inc 'Full-stack SaaS with Stripe payments'"
+User: "/sw:inc 'Full-stack SaaS with Stripe payments'"
     ↓
 role-orchestrator activates
     ↓

package/plugins/specweave/skills/{specweave-detector → detector}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: specweave-detector
-description: Detects SpecWeave context (.specweave/ directory exists) and provides workflow documentation. Explains available slash commands and workflow. Keywords slash commands, /specweave:increment, /increment, /specweave:do, /specweave:progress, /specweave:validate, /specweave:done, specweave commands, workflow help, specweave folder.
+name: detector
+description: Detects SpecWeave context (.specweave/ directory exists) and provides workflow documentation. Explains available slash commands and workflow. Keywords slash commands, /sw:increment, /increment, /sw:do, /sw:progress, /sw:validate, /sw:done, specweave commands, workflow help, specweave folder.
 ---
 
 # SpecWeave - Smart Workflow Documentation
@@ -36,7 +36,7 @@ SpecWeave provides explicit slash commands for reliable workflow execution.
 | Command | Description | Example |
 |---------|-------------|---------|
 | `/list-increments` | List all increments with status | `/list-increments` |
-| `/specweave:sync-docs` | Review strategic docs vs code | `/specweave:sync-docs --increment=003` |
+| `/sw:sync-docs` | Review strategic docs vs code | `/sw:sync-docs --increment=003` |
 | `/sync-github` | Sync increment to GitHub issues | `/sync-github` |
 
 ## Why Only ONE Alias?
@@ -82,7 +82,7 @@ npx specweave init my-saas
 /do
 # Auto-finds active increment 0002
 
-# Repeat: /specweave:increment → /specweave:do → /specweave:progress → /specweave:increment (auto-closes) → /specweave:do...
+# Repeat: /sw:increment → /sw:do → /sw:progress → /sw:increment (auto-closes) → /sw:do...
 ```
 
 ## Command Details
@@ -325,7 +325,7 @@ User: "What SpecWeave commands are available?"
 **Command syntax**:
 ```
 User: "How do I create a new increment?"
-→ Claude explains /specweave:increment command with examples
+→ Claude explains /sw:increment command with examples
 ```
 
 ## Documentation

package/plugins/specweave/skills/discrepancy-viewer.md

@@ -117,8 +117,8 @@ DISC-0003   knowledge-gap   🟡 medium    legacy-adapter      Single contributo
 DISC-0004   missing-adr     🟢 low       cache               No ADR for caching strategy
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-Use '/specweave:discrepancies show <ID>' for details
-Use '/specweave:discrepancy-to-increment <ID> <ID>...' to create an increment
+Use '/sw:discrepancies show <ID>' for details
+Use '/sw:discrepancy-to-increment <ID> <ID>...' to create an increment
 ```
 
 ### Statistics
@@ -149,6 +149,6 @@ By Priority:
 
 ## Related
 
-- `/specweave:discrepancy-to-increment` - Convert discrepancies to increments
-- `/specweave:jobs` - Monitor brownfield analysis jobs
+- `/sw:discrepancy-to-increment` - Convert discrepancies to increments
+- `/sw:jobs` - Monitor brownfield analysis jobs
 - `brownfield-analyzer` skill - Run new analysis

package/plugins/specweave/skills/external-sync-wizard/SKILL.md

@@ -121,7 +121,7 @@ Best for: Migrating from GitHub-first workflow to SpecWeave
 
 **4. Manual sync only**
 ```
-Use /specweave-github:sync command when needed
+Use /sw-github:sync command when needed
 
 Features:
 - No automatic sync via hooks
@@ -148,7 +148,7 @@ GitHub ↔ Jira
 
 **1. Yes, auto-create (Recommended)**
 ```
-Every /specweave:increment creates a GitHub issue automatically
+Every /sw:increment creates a GitHub issue automatically
 
 Benefits:
 - Immediate team visibility
@@ -161,7 +161,7 @@ Best for: Teams that want automatic GitHub integration
 
 **2. No, manual creation**
 ```
-Use /specweave-github:create-issue manually when needed
+Use /sw-github:create-issue manually when needed
 
 Benefits:
 - Create issues only for important increments
@@ -237,7 +237,7 @@ Best for: Migrating from Jira-first workflow to SpecWeave
 
 **4. Manual sync only**
 ```
-Use /specweave-jira:sync command when needed
+Use /sw-jira:sync command when needed
 
 Features:
 - No automatic sync via hooks
@@ -312,7 +312,7 @@ Best for: Migrating from ADO-first workflow to SpecWeave
 
 **4. Manual sync only**
 ```
-Use /specweave-ado:sync command when needed
+Use /sw-ado:sync command when needed
 
 Features:
 - No automatic sync via hooks
@@ -424,7 +424,7 @@ ADO_PAT=xxx
 **Trigger**: Explicit command
 
 **Flow**:
-1. User runs `/specweave-github:sync [increment-id]`
+1. User runs `/sw-github:sync [increment-id]`
 2. Choose direction: pull, push, or bidirectional
 3. Execute sync operation
 4. Report results to user
@@ -470,7 +470,7 @@ GitHub and Jira do NOT sync with each other. SpecWeave is the hub.
 
 **A**:
 1. Set sync direction: **Import-only**
-2. Run: `/specweave-github:import-all`
+2. Run: `/sw-github:import-all`
 3. SpecWeave creates increments from GitHub issues
 4. Review and adjust as needed
 5. Switch to **Bidirectional** when ready
@@ -479,7 +479,7 @@ GitHub and Jira do NOT sync with each other. SpecWeave is the hub.
 
 **A**: Yes! Use manual sync:
 ```bash
-/specweave-github:sync 0042-auth-feature  # Sync specific increment
+/sw-github:sync 0042-auth-feature  # Sync specific increment
 ```
 
 Auto-sync only affects **active** increments (not completed/abandoned).
@@ -488,7 +488,7 @@ Auto-sync only affects **active** increments (not completed/abandoned).
 
 ## Troubleshooting
 
-### Issue: GitHub issue not created after `/specweave:increment`
+### Issue: GitHub issue not created after `/sw:increment`
 
 **Diagnosis**:
 1. Check GitHub CLI: `gh auth status`
@@ -498,7 +498,7 @@ Auto-sync only affects **active** increments (not completed/abandoned).
 **Fix**:
 ```bash
 # Manual creation
-/specweave-github:create-issue 0042-auth-feature
+/sw-github:create-issue 0042-auth-feature
 ```
 
 ### Issue: Jira epic not updating
@@ -512,7 +512,7 @@ Auto-sync only affects **active** increments (not completed/abandoned).
 **Fix**:
 ```bash
 # Manual sync
-/specweave-jira:sync 0042-auth-feature --force
+/sw-jira:sync 0042-auth-feature --force
 ```
 
 ### Issue: Conflict during bidirectional sync
@@ -587,23 +587,23 @@ When experimenting or testing:
 ## Related Slash Commands
 
 ### GitHub
-- `/specweave-github:sync [increment-id]` - Manual sync
-- `/specweave-github:create-issue [increment-id]` - Create issue
-- `/specweave-github:close-issue [increment-id]` - Close issue
-- `/specweave-github:import-all` - Import all GitHub issues
-- `/specweave-github:status [increment-id]` - Check sync status
+- `/sw-github:sync [increment-id]` - Manual sync
+- `/sw-github:create-issue [increment-id]` - Create issue
+- `/sw-github:close-issue [increment-id]` - Close issue
+- `/sw-github:import-all` - Import all GitHub issues
+- `/sw-github:status [increment-id]` - Check sync status
 
 ### Jira
-- `/specweave-jira:sync [increment-id]` - Manual sync
-- `/specweave-jira:create-epic [increment-id]` - Create epic
-- `/specweave-jira:import-all` - Import all Jira epics
-- `/specweave-jira:status [increment-id]` - Check sync status
+- `/sw-jira:sync [increment-id]` - Manual sync
+- `/sw-jira:create-epic [increment-id]` - Create epic
+- `/sw-jira:import-all` - Import all Jira epics
+- `/sw-jira:status [increment-id]` - Check sync status
 
 ### Azure DevOps
-- `/specweave-ado:sync [increment-id]` - Manual sync
-- `/specweave-ado:create-workitem [increment-id]` - Create work item
-- `/specweave-ado:import-all` - Import all ADO work items
-- `/specweave-ado:status [increment-id]` - Check sync status
+- `/sw-ado:sync [increment-id]` - Manual sync
+- `/sw-ado:create-workitem [increment-id]` - Create work item
+- `/sw-ado:import-all` - Import all ADO work items
+- `/sw-ado:status [increment-id]` - Check sync status
 
 ---
 

package/plugins/specweave/skills/{specweave-framework → framework}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: specweave-framework
+name: framework
 description: Expert knowledge of SpecWeave framework structure, rules, conventions, and increment lifecycle. Deep understanding of source-of-truth discipline, increment naming, living docs sync. Covers SpecWeave-specific hooks (post-task-completion), and increment discipline. Activates for specweave rules, increment lifecycle, source of truth, increment naming, tasks.md format, spec.md structure, living docs sync, specweave hooks, where do files go, how to use specweave, specweave best practices, specweave conventions.
 allowed-tools: Read, Grep, Glob
 ---
@@ -80,16 +80,16 @@ board: digital-operations    # REQUIRED for 2-level
 ### Increment Lifecycle
 
 ```
-1. Plan    → /specweave:inc "feature-name"
+1. Plan    → /sw:inc "feature-name"
             ↓ PM agent creates spec.md, plan.md, tasks.md, tests.md
 
-2. Execute → /specweave:do
+2. Execute → /sw:do
             ↓ Selects next task, executes, marks complete
 
-3. Validate → /specweave:validate 0001
+3. Validate → /sw:validate 0001
             ↓ Checks spec compliance, test coverage
 
-4. Close   → /specweave:done 0001
+4. Close   → /sw:done 0001
             ↓ Creates COMPLETION-SUMMARY.md, archives
 ```
 
@@ -98,15 +98,15 @@ board: digital-operations    # REQUIRED for 2-level
 **THE IRON RULE**: Cannot start increment N+1 until increment N is DONE!
 
 **Enforcement**:
-- `/specweave:inc` **blocks** if previous increments incomplete
-- Use `/specweave:status` to check all increments
-- Use `/specweave:close` to close incomplete work
+- `/sw:inc` **blocks** if previous increments incomplete
+- Use `/sw:status` to check all increments
+- Use `/sw:close` to close incomplete work
 - `--force` flag for emergencies (logged, should be rare)
 
 **What "DONE" Means**:
 1. All tasks in `tasks.md` marked `[x] Completed`, OR
 2. `COMPLETION-SUMMARY.md` exists with "✅ COMPLETE" status, OR
-3. Explicit closure via `/specweave:close`
+3. Explicit closure via `/sw:close`
 
 **Three Options for Closing**:
 1. **Adjust Scope** - Remove features from spec.md, regenerate tasks
@@ -116,19 +116,19 @@ board: digital-operations    # REQUIRED for 2-level
 **Example**:
 ```bash
 # Check status
-/specweave:status
+/sw:status
 # Shows: 0002 (73% complete), 0003 (50% complete)
 
 # Try to start new increment
-/specweave:inc "0004-new-feature"
+/sw:inc "0004-new-feature"
 # ❌ Blocked! "Close 0002 and 0003 first"
 
 # Close previous work
-/specweave:close
+/sw:close
 # Interactive: Choose force-complete, move tasks, or reduce scope
 
 # Now can proceed
-/specweave:inc "0004-new-feature"
+/sw:inc "0004-new-feature"
 # ✅ Works! Clean slate
 ```
 
@@ -235,7 +235,7 @@ vim src/skills/increment-planner/SKILL.md
 npm run install:skills
 
 # Test (skill activates from .claude/)
-/specweave:inc "test feature"
+/sw:inc "test feature"
 
 # WRONG: Edit installed file
 vim .claude/skills/increment-planner/SKILL.md  # ❌ Gets overwritten!
@@ -345,7 +345,7 @@ Until hooks are fully automated, **YOU MUST**:
 **Core Framework** (always loaded):
 - 8 core skills (increment-planner, spec-generator, context-loader, etc.)
 - 3 core agents (PM, Architect, Tech Lead)
-- 7 core commands (/specweave:inc, /specweave:do, etc.)
+- 7 core commands (/sw:inc, /sw:do, etc.)
 
 **Plugins** (opt-in):
 - `specweave-github` - GitHub integration (issue sync, PR creation)
@@ -372,7 +372,7 @@ Until hooks are fully automated, **YOU MUST**:
    - Scans package.json, directories, env vars
    - Suggests plugins: "Found React. Enable frontend-stack? (Y/n)"
 
-2. **First Increment** (during `/specweave:inc`):
+2. **First Increment** (during `/sw:inc`):
    - Analyzes increment description for keywords
    - Suggests before creating spec: "This needs kubernetes plugin. Enable? (Y/n)"
 
@@ -437,29 +437,29 @@ SpecWeave works with multiple AI coding assistants:
 ## Key Commands
 
 ### Increment Lifecycle
-- `/specweave:inc "feature-name"` - Plan new increment (PM-led process)
-- `/specweave:do` - Execute next task (smart resume)
-- `/specweave:progress` - Show progress, PM gate status, next action
-- `/specweave:validate 0001` - Validate spec, tests, quality
-- `/specweave:done 0001` - Close increment (PM validation)
-- `/specweave:next` - Auto-close if ready, suggest next work
+- `/sw:inc "feature-name"` - Plan new increment (PM-led process)
+- `/sw:do` - Execute next task (smart resume)
+- `/sw:progress` - Show progress, PM gate status, next action
+- `/sw:validate 0001` - Validate spec, tests, quality
+- `/sw:done 0001` - Close increment (PM validation)
+- `/sw:next` - Auto-close if ready, suggest next work
 
 ### Increment Discipline
-- `/specweave:status` - Show all increments and completion status
-- `/specweave:close` - Interactive closure of incomplete increments
+- `/sw:status` - Show all increments and completion status
+- `/sw:close` - Interactive closure of incomplete increments
 
 ### Documentation Sync
-- `/specweave:sync-docs review` - Review strategic docs before implementation
-- `/specweave:sync-docs update` - Update living docs from completed increments
+- `/sw:sync-docs review` - Review strategic docs before implementation
+- `/sw:sync-docs update` - Update living docs from completed increments
 
 ### External Platform Sync
-- `/specweave:sync-github` - Bidirectional GitHub sync
-- `/specweave:sync-jira` - Bidirectional Jira sync
+- `/sw:sync-github` - Bidirectional GitHub sync
+- `/sw:sync-jira` - Bidirectional Jira sync
 
 ## Common Questions
 
 ### Q: Where do I create a new increment?
-**A**: Use `/specweave:inc "####-descriptive-name"`. It creates:
+**A**: Use `/sw:inc "####-descriptive-name"`. It creates:
 ```
 .specweave/increments/####-descriptive-name/
 ├── spec.md
@@ -476,10 +476,10 @@ SpecWeave works with multiple AI coding assistants:
 ```
 
 ### Q: How do I know what tasks are left?
-**A**: Use `/specweave:progress` or read `.specweave/increments/####/tasks.md`
+**A**: Use `/sw:progress` or read `.specweave/increments/####/tasks.md`
 
 ### Q: Can I start a new increment before finishing the current one?
-**A**: NO! (v0.6.0+) The framework **blocks** you. Use `/specweave:status` to check, `/specweave:close` to close.
+**A**: NO! (v0.6.0+) The framework **blocks** you. Use `/sw:status` to check, `/sw:close` to close.
 
 ### Q: Where do I edit skills/agents/commands?
 **A**: Edit in `src/` (source of truth), then run `npm run install:all` to sync to `.claude/`
@@ -510,8 +510,8 @@ I activate when you ask about:
 
 ## When to Use Other Skills/Agents
 
-- **increment-planner** - Planning NEW increments (/specweave:inc)
-- **PM agent** - Leading increment creation (auto-invoked by /specweave:inc)
+- **increment-planner** - Planning NEW increments (/sw:inc)
+- **PM agent** - Leading increment creation (auto-invoked by /sw:inc)
 - **Architect agent** - Designing system architecture
 - **Tech Lead agent** - Code review, best practices
 - **spec-generator** - Creating detailed technical RFCs

package/plugins/specweave/skills/increment-planner/SKILL.md

@@ -243,7 +243,7 @@ For each US you will generate:
 
 ❌ FORBIDDEN: Skipping this step and generating spec.md directly
 ❌ FORBIDDEN: Inventing project names not in the API output
-❌ FORBIDDEN: Using folder names as project (e.g., "sw-olysense")
+❌ FORBIDDEN: Using folder names as project (e.g., "my-project-folder")
 ❌ FORBIDDEN: Using {{PROJECT_ID}} or {{BOARD_ID}} placeholders
 ❌ FORBIDDEN: Creating spec.md for 2-level without board: field
 ❌ FORBIDDEN: Generating spec.md without running context API first
@@ -694,27 +694,28 @@ Replace placeholders:
 - **`{{BOARD_ID}}`** ← MANDATORY for 2-level (from STEP 0B)
 - `{{PROJECT_FE_ID}}`, `{{PROJECT_BE_ID}}`, `{{PROJECT_SHARED_ID}}` (for multi-repo)
 
-**Key Rules for spec.md:**
-1. **`project:` field MUST be set in YAML frontmatter** (1-level and 2-level)
-2. **`board:` field MUST be set in YAML frontmatter** (2-level only)
-3. **User stories grouped by project** if multi-project (Frontend, Backend, Shared, etc.)
-4. **User story IDs have project prefix**: `US-FE-001`, `US-BE-001` (multi-project)
-5. **AC-IDs have project prefix**: `AC-FE-US1-01`, `AC-BE-US1-01` (multi-project)
+**Key Rules for spec.md (ADR-0140: v0.35.0+):**
+1. **`project:` field REMOVED from YAML frontmatter** - now resolved from per-US fields
+2. **`board:` field REMOVED from YAML frontmatter** (2-level) - now in per-US fields
+3. **Each User Story MUST have `**Project**:` field** - source of truth for project
+4. **Each User Story (2-level) MUST have `**Board**:` field** - source of truth for board
+5. **User story IDs have project prefix**: `US-FE-001`, `US-BE-001` (multi-project)
+6. **AC-IDs have project prefix**: `AC-FE-US1-01`, `AC-BE-US1-01` (multi-project)
 
-**VALIDATION (spec.md frontmatter):**
-```yaml
-# 1-level structure (REQUIRED):
-project: digital-operations    # ← MUST be set
+**VALIDATION (per-US fields - v0.35.0+):**
+```markdown
+### US-001: Feature Name
+**Project**: digital-operations    # ← REQUIRED (resolved from config)
 
-# 2-level structure (BOTH REQUIRED):
-project: acme-corp             # ← MUST be set
-board: digital-operations      # ← MUST be set
+### US-001: Feature Name (2-level)
+**Project**: acme-corp             # ← REQUIRED
+**Board**: digital-operations      # ← REQUIRED for 2-level
 ```
 
 **⚠️ FORBIDDEN:**
-- Creating spec.md with `project: {{PROJECT_ID}}` (unresolved placeholder)
-- Creating spec.md for 2-level with `board: {{BOARD_ID}}` (unresolved placeholder)
-- Leaving project/board fields empty or undefined
+- User stories without `**Project**:` field
+- User stories (2-level) without `**Board**:` field
+- Using unresolved placeholders like `{{PROJECT_ID}}`
 
 ### STEP 5: Create plan.md Template
 
@@ -846,7 +847,7 @@ This step uses the existing sync infrastructure to:
 **Run the sync-specs command:**
 
 ```bash
-/specweave:sync-specs {increment-id}
+/sw:sync-specs {increment-id}
 ```
 
 **Expected output:**
@@ -874,7 +875,7 @@ If `canUpsertInternalItems: false` in config:
 External tool sync failures are NON-BLOCKING:
 ```
 ⚠️ External sync failed: Rate limit exceeded
-💡 Run /specweave:sync-specs {increment-id} to retry
+💡 Run /sw:sync-specs {increment-id} to retry
 ```
 
 **Output after sync:**
@@ -884,8 +885,8 @@ External tool sync failures are NON-BLOCKING:
 
 Next steps:
 1. Review the increment plan and docs
-2. Start implementation: /specweave:do {increment-id}
-3. Monitor status: /specweave:status {increment-id}
+2. Start implementation: /sw:do {increment-id}
+3. Monitor status: /sw:status {increment-id}
 ```
 
 ---
@@ -1042,17 +1043,17 @@ node plugins/specweave/skills/increment-planner/scripts/generate-short-name.js "
 
 **GitHub Issues**: After increment creation, optionally sync to GitHub:
 ```bash
-/specweave-github:create-issue 0021
+/sw-github:create-issue 0021
 ```
 
 **Jira Epics**: Sync to Jira:
 ```bash
-/specweave-jira:sync 0021
+/sw-jira:sync 0021
 ```
 
 **Azure DevOps**: Sync to ADO work items:
 ```bash
-/specweave-ado:create-workitem 0021
+/sw-ado:create-workitem 0021
 ```
 
 ---