universal-dev-standards 4.2.0 → 5.0.0-beta.10

package/bundled/skills/{claude-code/refactoring-assistant/SKILL.md → refactoring-assistant/guide.md}

@@ -1,5 +1,5 @@
 ---
-name: refactoring-assistant
+scope: universal
 description: |
   Guide refactoring decisions and large-scale code improvements.
   Use when: refactoring code, legacy modernization, technical debt, rewrite decisions.
@@ -8,7 +8,7 @@ description: |
 
 # Refactoring Assistant
 
-> **Language**: English | [繁體中文](../../../locales/zh-TW/skills/claude-code/refactoring-assistant/SKILL.md)
+> **Language**: English | [繁體中文](../../locales/zh-TW/skills/refactoring-assistant/SKILL.md)
 
 **Version**: 2.0.0
 **Last Updated**: 2026-01-21
@@ -273,16 +273,16 @@ selection_guide:
 ## Detailed Guidelines
 
 For complete standards, see:
-- [Refactoring Standards](../../../core/refactoring-standards.md)
+- [Refactoring Standards](../../core/refactoring-standards.md)
 
 ---
 
 ## Related Standards
 
-- [Refactoring Standards](../../../core/refactoring-standards.md) - Core standard
-- [Test-Driven Development](../../../core/test-driven-development.md) - TDD refactor phase
-- [Code Review Checklist](../../../core/code-review-checklist.md) - Refactoring PR review
-- [Checkin Standards](../../../core/checkin-standards.md) - Pre-commit requirements
+- [Refactoring Standards](../../core/refactoring-standards.md) - Core standard
+- [Test-Driven Development](../../core/test-driven-development.md) - TDD refactor phase
+- [Code Review Checklist](../../core/code-review-checklist.md) - Refactoring PR review
+- [Checkin Standards](../../core/checkin-standards.md) - Pre-commit requirements
 - [TDD Assistant](../tdd-assistant/SKILL.md) - TDD workflow
 
 ---

package/bundled/skills/release-standards/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: release
+scope: universal
+description: "[UDS] Guide release process and changelogs"
+allowed-tools: Read, Write, Grep, Bash(git:*), Bash(npm version:*)
+argument-hint: "[version]"
+disable-model-invocation: true
+---
+
+# Release Assistant | 發布助手
+
+Guide the release process following Semantic Versioning and changelog best practices.
+
+引導遵循語義化版本和變更日誌最佳實踐的發布流程。
+
+## Subcommands | 子命令
+
+| Subcommand | Description | 說明 |
+|------------|-------------|------|
+| `start` | Start a release branch/process | 開始發布流程 |
+| `finish` | Finalize release (tag, merge) | 完成發布（標籤、合併） |
+| `changelog` | Generate or update CHANGELOG.md | 產生或更新變更日誌 |
+| `check` | Run pre-release verification | 執行發布前檢查 |
+
+## Version Types | 版本類型
+
+| Type | Pattern | npm Tag | 用途 |
+|------|---------|---------|------|
+| Stable | `X.Y.Z` | `@latest` | Production release | 正式版 |
+| Beta | `X.Y.Z-beta.N` | `@beta` | Public testing | 公開測試 |
+| Alpha | `X.Y.Z-alpha.N` | `@alpha` | Internal testing | 內部測試 |
+| RC | `X.Y.Z-rc.N` | `@rc` | Release candidate | 候選版本 |
+
+## Workflow | 工作流程
+
+1. **Determine version** - Decide version type based on changes (MAJOR/MINOR/PATCH)
+2. **Update version files** - Update package.json and related version references
+3. **Update CHANGELOG** - Move [Unreleased] entries to new version section
+4. **Run pre-release checks** - Verify tests, lint, and standards compliance
+5. **Create git tag** - Tag with `vX.Y.Z` format
+6. **Commit and push** - Commit version bump and push tags
+
+### Version Increment Rules | 版本遞增規則
+
+| Change Type | Increment | Example |
+|-------------|-----------|---------|
+| Breaking changes | MAJOR | 1.9.5 → 2.0.0 |
+| New features (backward-compatible) | MINOR | 2.3.5 → 2.4.0 |
+| Bug fixes (backward-compatible) | PATCH | 3.1.2 → 3.1.3 |
+
+## Usage | 使用方式
+
+- `/release start 1.2.0` - Start release process for v1.2.0
+- `/release changelog 1.2.0` - Update CHANGELOG for v1.2.0
+- `/release finish 1.2.0` - Finalize and tag v1.2.0
+- `/release check` - Run pre-release verification
+
+## Reference | 參考
+
+- Detailed guide: [guide.md](./guide.md)
+- Core standard: [versioning.md](../../core/versioning.md)

package/bundled/skills/{claude-code/release-standards → release-standards}/changelog-format.md

@@ -1,6 +1,6 @@
 # Changelog Format Guide
 
-> **Language**: English | [繁體中文](../../../locales/zh-TW/skills/claude-code/release-standards/changelog-format.md)
+> **Language**: English | [繁體中文](../../locales/zh-TW/skills/release-standards/changelog-format.md)
 
 **Version**: 1.0.0
 **Last Updated**: 2025-12-24
@@ -219,7 +219,7 @@ conventional-changelog -p angular -i CHANGELOG.md -s
 
 ## Related Standards
 
-- [Changelog Standards](../../../core/changelog-standards.md)
+- [Changelog Standards](../../core/changelog-standards.md)
 - [Semantic Versioning Guide](./semantic-versioning.md)
 
 ---

package/bundled/skills/{claude-code/release-standards/SKILL.md → release-standards/guide.md}

@@ -1,5 +1,5 @@
 ---
-name: release-standards
+scope: universal
 description: |
   Semantic versioning and changelog formatting for software releases.
   Use when: preparing releases, updating version numbers, writing changelogs.
@@ -8,7 +8,7 @@ description: |
 
 # Release Standards
 
-> **Language**: English | [繁體中文](../../../locales/zh-TW/skills/claude-code/release-standards/SKILL.md)
+> **Language**: English | [繁體中文](../../locales/zh-TW/skills/release-standards/SKILL.md)
 
 **Version**: 1.1.0
 **Last Updated**: 2026-01-02
@@ -16,6 +16,8 @@ description: |
 
 ---
 
+> **Core Standard**: This skill implements [Versioning](../../core/versioning.md). For comprehensive methodology documentation, refer to the core standard.
+
 ## Purpose
 
 This skill provides semantic versioning and changelog formatting standards.
@@ -169,9 +171,9 @@ This project follows **Keep a Changelog** format.
 
 ## Related Standards
 
-- [Versioning](../../core/versioning.md)
-- [Changelog Standards](../../core/changelog-standards.md)
-- [Git Workflow](../../core/git-workflow.md)
+- [Versioning](../../core/versioning.md) - Core semantic versioning standard
+- [Changelog Standards](../../core/changelog-standards.md) - Keep a Changelog format
+- [Git Workflow](../../core/git-workflow.md) - Git tagging and release branches
 
 ---
 

package/bundled/skills/{claude-code/release-standards → release-standards}/release-workflow.md

@@ -1,9 +1,9 @@
 # Release Workflow Guide
 
-> **Language**: English | [繁體中文](../../../locales/zh-TW/skills/claude-code/release-standards/release-workflow.md)
+> **Language**: English | [繁體中文](../../locales/zh-TW/skills/release-standards/release-workflow.md)
 
-**Version**: 2.0.0
-**Last Updated**: 2026-01-14
+**Version**: 2.2.0
+**Last Updated**: 2026-01-26
 **Applicability**: All software projects using semantic versioning
 
 ---
@@ -70,31 +70,28 @@ This document provides a universal release workflow guide applicable to any soft
 
 ## Standard Release Workflow
 
-### Step 1: Pre-release Checks
+> **Workflow Philosophy**: Version first, then validate. Update version before testing to ensure validation runs against the exact release version.
+
+### Step 1: Prepare Release Branch
 
 ```bash
 # Ensure you're on the main branch and up to date
 git checkout main
 git pull origin main
 
-# Run tests
-npm test  # or your project's test command
-
-# Run linting
-npm run lint  # or your project's lint command
-
-# Check git status
-git status  # Should be clean
+# Check git status (should be clean)
+git status
 ```
 
 ### Step 2: Update Version
 
 ```bash
 # For npm projects
-npm version X.Y.Z        # Stable
-npm version X.Y.Z-beta.N # Beta
+npm version X.Y.Z --no-git-tag-version        # Stable
+npm version X.Y.Z-beta.N --no-git-tag-version # Beta
 
 # For other projects, update version file manually
+# Update all project-specific version files (see CLAUDE.md)
 ```
 
 ### Step 3: Update CHANGELOG
@@ -102,8 +99,6 @@ npm version X.Y.Z-beta.N # Beta
 Update `CHANGELOG.md` following [Keep a Changelog](https://keepachangelog.com/) format:
 
 ```markdown
-## [Unreleased]
-
 ## [X.Y.Z] - YYYY-MM-DD
 
 ### Added
@@ -116,7 +111,39 @@ Update `CHANGELOG.md` following [Keep a Changelog](https://keepachangelog.com/)
 - Bug fix descriptions
 ```
 
-### Step 4: Commit and Tag
+For beta releases, add a warning:
+
+```markdown
+## [X.Y.Z-beta.N] - YYYY-MM-DD
+
+> ⚠️ **Beta Release**: For testing. Install with `npm install <package>@beta`
+```
+
+### Step 4: Run All Tests
+
+```bash
+# Run automated tests
+npm test  # or your project's test command
+
+# Run linting
+npm run lint  # or your project's lint command
+
+# Run pre-release checks (if available)
+./scripts/pre-release-check.sh  # or .\scripts\pre-release-check.ps1
+```
+
+### Step 5: Manual Verification
+
+Before proceeding, manually verify:
+
+- [ ] **Build verification**: Application builds successfully
+- [ ] **Smoke test**: Core functionality works as expected
+- [ ] **Version display**: Version number is displayed correctly
+- [ ] **For beta**: Known issues documented in CHANGELOG
+
+> ⚠️ **Stop here if any verification fails.** Fix issues before proceeding.
+
+### Step 6: Commit and Tag
 
 ```bash
 # Commit changes
@@ -128,7 +155,7 @@ git tag vX.Y.Z
 git push origin main --tags
 ```
 
-### Step 5: Create Release
+### Step 7: Create Release
 
 Create a GitHub/GitLab release:
 - Tag: `vX.Y.Z`
@@ -136,7 +163,7 @@ Create a GitHub/GitLab release:
 - Mark as pre-release if beta/alpha/rc
 - Add release notes from CHANGELOG
 
-### Step 6: Verify Publication
+### Step 8: Verify Publication
 
 ```bash
 # For npm packages
@@ -144,6 +171,9 @@ npm view <package-name> dist-tags
 
 # Test installation
 npm install -g <package-name>@<version>
+
+# Verify version
+<command> --version  # Should show X.Y.Z
 ```
 
 ---
@@ -252,18 +282,21 @@ npm version patch
 
 ## Pre-release Checklist
 
-### Universal Checks
+### Universal Checks (All Releases)
 
+- [ ] On correct branch (main for stable)
+- [ ] Git working directory clean
+- [ ] Version updated in all required files
+- [ ] CHANGELOG updated with release notes
 - [ ] All tests passing
 - [ ] Linting passing
-- [ ] Git working directory clean
-- [ ] CHANGELOG updated
-- [ ] On correct branch (main for stable)
+- [ ] Build successful
+- [ ] Core functionality works (smoke test)
 
 ### Before Beta Release
 
 - [ ] Universal checks completed
-- [ ] Known issues documented
+- [ ] Known issues documented in CHANGELOG
 
 ### Before Stable Release
 
@@ -327,6 +360,8 @@ When helping with releases:
 
 | Version | Date | Changes |
 |---------|------|---------|
+| 2.2.0 | 2026-01-26 | Simplify to universal Beta→Stable workflow; Alpha→Beta→Stable moved to project-specific |
+| 2.1.0 | 2026-01-26 | Adopt "version first" workflow: update version → test → verify → release |
 | 2.0.0 | 2026-01-14 | Refactor to universal guide, move project-specific content to CLAUDE.md |
 | 1.0.0 | 2026-01-02 | Initial release workflow guide |
 

package/bundled/skills/{claude-code/release-standards → release-standards}/semantic-versioning.md

@@ -1,6 +1,6 @@
 # Semantic Versioning Guide
 
-> **Language**: English | [繁體中文](../../../locales/zh-TW/skills/claude-code/release-standards/semantic-versioning.md)
+> **Language**: English | [繁體中文](../../locales/zh-TW/skills/release-standards/semantic-versioning.md)
 
 **Version**: 1.0.0
 **Last Updated**: 2025-12-24
@@ -222,7 +222,7 @@ version-1.0.0   ❌ Avoid (too verbose)
 
 ## Related Standards
 
-- [Versioning Standards](../../../core/versioning.md)
+- [Versioning Standards](../../core/versioning.md)
 - [Changelog Format Guide](./changelog-format.md)
 
 ---

package/bundled/skills/requirement-assistant/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: requirement
+scope: universal
+description: "[UDS] Write user stories and requirements following INVEST criteria"
+allowed-tools: Read, Write, Grep
+argument-hint: "[feature description | 功能描述]"
+---
+
+# Requirement Assistant | 需求助手
+
+Write well-structured user stories and requirements following INVEST criteria.
+
+撰寫結構良好的使用者故事和需求文件，遵循 INVEST 準則。
+
+## Workflow | 工作流程
+
+1. **Understand context** - Gather feature information | 蒐集功能資訊
+2. **Identify stakeholders** - Who benefits from this feature? | 誰受益？
+3. **Write user story** - Follow the standard format | 遵循標準格式
+4. **Define acceptance criteria** - Specific, testable conditions | 定義可測試條件
+5. **Validate with INVEST** - Check quality criteria | 用 INVEST 驗證品質
+
+## User Story Format | 使用者故事格式
+
+```markdown
+As a [role],
+I want [feature],
+So that [benefit].
+
+### Acceptance Criteria
+
+- [ ] Given [context], when [action], then [result]
+- [ ] Given [context], when [action], then [result]
+```
+
+## INVEST Criteria | INVEST 準則
+
+| Criterion | Description | 說明 |
+|-----------|-------------|------|
+| **I**ndependent | Can be developed separately | 可獨立開發 |
+| **N**egotiable | Details can be discussed | 可協商細節 |
+| **V**aluable | Delivers value to user | 提供使用者價值 |
+| **E**stimable | Can estimate effort | 可估算工作量 |
+| **S**mall | Fits in one sprint | 適合單一迭代 |
+| **T**estable | Has clear test criteria | 有明確測試標準 |
+
+## Quality Checklist | 品質檢查清單
+
+- [ ] User story follows "As a / I want / So that" format
+- [ ] At least 2 acceptance criteria defined
+- [ ] All 6 INVEST criteria satisfied
+- [ ] Edge cases and error scenarios considered
+- [ ] Out of scope items documented
+
+## Usage | 使用方式
+
+```
+/requirement                         - Interactive requirement wizard | 互動式需求精靈
+/requirement user login              - Write requirement for feature | 為功能撰寫需求
+/requirement "users can export data" - Based on description | 根據描述撰寫
+```
+
+## Reference | 參考
+
+- Detailed guide: [guide.md](./guide.md)
+- Core standard: [requirement-engineering.md](../../core/requirement-engineering.md)

package/bundled/skills/{claude-code/requirement-assistant/SKILL.md → requirement-assistant/guide.md}

@@ -1,5 +1,5 @@
 ---
-name: requirement-assistant
+scope: universal
 description: |
   Guide requirement writing, user story creation, and feature specification.
   Use when: writing requirements, user stories, issues, feature planning.
@@ -8,11 +8,12 @@ description: |
 
 # Requirement Assistant
 
-> **Language**: English | [繁體中文](../../../../locales/zh-TW/skills/claude-code/requirement-assistant/SKILL.md)
+> **Language**: English | [繁體中文](../../locales/zh-TW/skills/requirement-assistant/SKILL.md)
 
-**Version**: 1.0.0
-**Last Updated**: 2025-12-24
+**Version**: 1.1.0
+**Last Updated**: 2026-01-28
 **Applicability**: Claude Code Skills
+**Core Standard**: [Requirement Engineering Standards](../../core/requirement-engineering.md)
 
 ---
 
@@ -202,8 +203,14 @@ This project uses **English** for requirements and issues.
 
 ## Related Standards
 
-- [Spec-Driven Development](../../core/spec-driven-development.md)
-- [Checkin Standards](../../core/checkin-standards.md)
+**Core Standard (Theory & Deep Reference)**:
+- [Requirement Engineering Standards](../../core/requirement-engineering.md) - Complete theoretical foundation including IEEE 830, SWEBOK v4.0, ISO 25010
+
+**Related Standards**:
+- [Spec-Driven Development](../../core/spec-driven-development.md) - Specification workflow
+- [Behavior-Driven Development](../../core/behavior-driven-development.md) - Given-When-Then scenarios
+- [Acceptance Test-Driven Development](../../core/acceptance-test-driven-development.md) - ATDD workshops
+- [Checkin Standards](../../core/checkin-standards.md) - Code check-in requirements
 
 ---
 
@@ -211,6 +218,7 @@ This project uses **English** for requirements and issues.
 
 | Version | Date | Changes |
 |---------|------|---------|
+| 1.1.0 | 2026-01-28 | Added: Core Standard reference to requirement-engineering.md, expanded Related Standards section |
 | 1.0.0 | 2025-12-24 | Added: Standard sections (Purpose, Related Standards, Version History, License) |
 
 ---

package/bundled/skills/{claude-code/requirement-assistant → requirement-assistant}/requirement-checklist.md

@@ -1,6 +1,6 @@
 # Requirement Completeness Checklist
 
-> **Language**: English | [繁體中文](../../../../locales/zh-TW/skills/claude-code/requirement-assistant/requirement-checklist.md)
+> **Language**: English | [繁體中文](../../locales/zh-TW/skills/requirement-assistant/requirement-checklist.md)
 
 **Version**: 1.0.0
 **Last Updated**: 2025-12-24
@@ -298,7 +298,7 @@ Before submitting for development:
 ## Related Standards
 
 - [Requirement Writing Guide](./requirement-writing.md)
-- [Spec-Driven Development](../../../core/spec-driven-development.md)
+- [Spec-Driven Development](../../core/spec-driven-development.md)
 
 ---
 

package/bundled/skills/{claude-code/requirement-assistant → requirement-assistant}/requirement-writing.md

@@ -1,6 +1,6 @@
 # Requirement Writing Guide
 
-> **Language**: English | [繁體中文](../../../../locales/zh-TW/skills/claude-code/requirement-assistant/requirement-writing.md)
+> **Language**: English | [繁體中文](../../locales/zh-TW/skills/requirement-assistant/requirement-writing.md)
 
 **Version**: 1.0.0
 **Last Updated**: 2025-12-24
@@ -372,7 +372,7 @@ Before submitting a requirement:
 ## Related Standards
 
 - [Requirement Completeness Checklist](./requirement-checklist.md)
-- [Spec-Driven Development](../../../core/spec-driven-development.md)
+- [Spec-Driven Development](../../core/spec-driven-development.md)
 
 ---
 

package/bundled/skills/reverse-engineer/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: reverse
+scope: partial
+description: "[UDS] Reverse engineer code to Specs, BDD, or TDD coverage"
+allowed-tools: Read, Grep, Glob
+argument-hint: "[spec|bdd|tdd] <input>"
+disable-model-invocation: true
+---
+
+# Reverse Engineering Assistant | 反向工程助手
+
+Reverse engineer existing code into specifications, BDD scenarios, or TDD coverage reports.
+
+將現有程式碼反向工程為規格文件、BDD 場景或 TDD 覆蓋率報告。
+
+## Subcommands | 子命令
+
+| Subcommand | Input | Output | Description | 說明 |
+|------------|-------|--------|-------------|------|
+| `spec` | Code files/dirs | `SPEC-XXX.md` | Extract spec from code | 從程式碼提取規格 |
+| `bdd` | `SPEC-XXX.md` | `.feature` | Convert ACs to Gherkin | 將 AC 轉為 Gherkin |
+| `tdd` | `.feature` | Coverage Report | Analyze test coverage | 分析測試覆蓋率 |
+
+## Workflow | 工作流程
+
+### spec: Code to Specification
+
+1. **Scan** - Read source files and identify public APIs, data flows, and business logic
+2. **Classify** - Tag each finding as `[Confirmed]`, `[Inferred]`, or `[Unknown]`
+3. **Structure** - Organize into SDD spec format with Acceptance Criteria
+4. **Attribute** - Cite every reversed item with `file:line` source reference
+
+### bdd: Specification to Gherkin
+
+1. **Parse** - Read SPEC-XXX.md and extract Acceptance Criteria
+2. **Convert** - Map each AC to a Gherkin Scenario (1:1 mapping)
+3. **Tag** - Add `@SPEC-XXX` and `@AC-N` tags for traceability
+4. **Write** - Output `.feature` file with `# [Source: path:AC-N]` comments
+
+### tdd: Feature to Coverage Report
+
+1. **Parse** - Read `.feature` file scenarios
+2. **Search** - Find corresponding test files using Grep/Glob
+3. **Map** - Match scenarios to existing unit tests
+4. **Report** - Output coverage matrix (covered / missing / partial)
+
+## Anti-Hallucination Rules | 防幻覺規則
+
+| Rule | Requirement | 要求 |
+|------|-------------|------|
+| **Certainty Tags** | Use `[Confirmed]`, `[Inferred]`, `[Unknown]` for all findings | 所有發現須標注確定性 |
+| **Source Attribution** | Cite `file:line` for every reversed item | 每項反向結果須引用來源 |
+| **No Fabrication** | Never invent APIs or behaviors not found in code | 不得捏造程式碼中不存在的 API 或行為 |
+
+## Usage | 使用方式
+
+- `/reverse spec src/auth/` - Extract specification from auth module
+- `/reverse bdd specs/SPEC-AUTH.md` - Convert spec ACs to Gherkin scenarios
+- `/reverse tdd features/auth.feature` - Analyze test coverage for feature file
+
+## Reference | 參考
+
+- Detailed guide: [guide.md](./guide.md)
+- Core standard: [reverse-engineering-standards.md](../../core/reverse-engineering-standards.md)

package/bundled/skills/{claude-code/reverse-engineer → reverse-engineer}/bdd-extraction.md

@@ -3,7 +3,7 @@
 **Version**: 1.0.0
 **Last Updated**: 2026-01-19
 
-> **Language**: English | [繁體中文](../../../locales/zh-TW/skills/claude-code/reverse-engineer/bdd-extraction.md)
+> **Language**: English | [繁體中文](../../locales/zh-TW/skills/reverse-engineer/bdd-extraction.md)
 
 This guide provides detailed workflows for extracting BDD (Behavior-Driven Development) scenarios from SDD specifications.
 

package/bundled/skills/{claude-code/reverse-engineer/SKILL.md → reverse-engineer/guide.md}

@@ -1,5 +1,5 @@
 ---
-name: reverse-engineer
+scope: partial
 description: |
   Reverse engineer existing code into SDD specification documents.
   Use when: analyzing legacy code, documenting undocumented systems, creating specs from existing implementations.
@@ -8,13 +8,13 @@ description: |
 
 # Reverse Engineering to SDD Specification Guide
 
-> **Language**: English | [繁體中文](../../../locales/zh-TW/skills/claude-code/reverse-engineer/SKILL.md)
+> **Language**: English | [繁體中文](../../locales/zh-TW/skills/reverse-engineer/SKILL.md)
 
-**Version**: 1.1.0
-**Last Updated**: 2026-01-19
+**Version**: 1.2.0
+**Last Updated**: 2026-01-25
 **Applicability**: Claude Code Skills
 
-> **Core Standard**: This skill implements [Reverse Engineering Standards](../../../core/reverse-engineering-standards.md). For comprehensive methodology documentation accessible by any AI tool, refer to the core standard.
+> **Core Standard**: This skill implements [Reverse Engineering Standards](../../core/reverse-engineering-standards.md). For comprehensive methodology documentation accessible by any AI tool, refer to the core standard.
 
 ---
 
@@ -67,9 +67,11 @@ This skill guides you through reverse engineering existing code into SDD (Spec-D
 
 ### 1. Anti-Hallucination Compliance
 
-**CRITICAL**: This skill MUST strictly follow [Anti-Hallucination Standards](../../../core/anti-hallucination.md).
+**CRITICAL**: This skill MUST strictly follow [Anti-Hallucination Standards](../../core/anti-hallucination.md).
 
-#### Certainty Labels
+#### Certainty Labels (from Unified Tag System)
+
+This skill uses **Certainty Tags** for analyzing existing code. See [Anti-Hallucination Standards](../../core/anti-hallucination.md#certainty-classification-tags) for the complete tag reference.
 
 | Tag | Use When | Example |
 |-----|----------|---------|
@@ -168,7 +170,7 @@ Becomes:
 **Input**: All analysis results
 **Output**: Draft specification document
 
-**Template**: Use [reverse-spec-template.md](../../../templates/reverse-spec-template.md)
+**Template**: Use [reverse-spec-template.md](../../templates/reverse-spec-template.md)
 
 ### Stage 5: Human Review
 
@@ -245,11 +247,11 @@ describe('Shopping Cart', () => {
 
 ## Integration with Other Skills
 
-### With /spec (Spec-Driven Development)
+### With /sdd (Spec-Driven Development)
 
-1. Generate reverse-engineered spec using `/reverse-spec`
+1. Generate reverse-engineered spec using `/reverse-sdd`
 2. Review and fill in `[Unknown]` sections
-3. Use `/spec review` to validate completeness
+3. Use `/sdd review` to validate completeness
 4. Proceed with normal SDD workflow for enhancements
 
 ### With /tdd (Test-Driven Development)
@@ -277,7 +279,7 @@ The reverse engineering skill supports a complete SDD → BDD → TDD pipeline:
 │   Code + Tests                                                          │
 │        │                                                                │
 │        ▼                                                                │
-│   /reverse-spec                                                         │
+│   /reverse-sdd                                                         │
 │        │                                                                │
 │        └─→ Generate SPEC-XXX with Acceptance Criteria                   │
 │                │                                                        │
@@ -301,7 +303,7 @@ The reverse engineering skill supports a complete SDD → BDD → TDD pipeline:
 
 | Command | Input | Output | Purpose |
 |---------|-------|--------|---------|
-| `/reverse-spec` | Code directory | SPEC-XXX.md | Extract requirements from code |
+| `/reverse-sdd` | Code directory | SPEC-XXX.md | Extract requirements from code |
 | `/reverse-bdd` | SPEC file | .feature files | Convert AC to Gherkin scenarios |
 | `/reverse-tdd` | .feature files | Coverage report | Map scenarios to unit tests |
 
@@ -309,7 +311,7 @@ The reverse engineering skill supports a complete SDD → BDD → TDD pipeline:
 
 ```bash
 # Step 1: Reverse engineer code to SDD specification
-/reverse-spec src/auth/
+/reverse-sdd src/auth/
 
 # Step 2: Transform acceptance criteria to BDD scenarios
 /reverse-bdd specs/SPEC-AUTH.md
@@ -376,10 +378,10 @@ This skill auto-detects project configuration:
 
 ## Related Standards
 
-- [Reverse Engineering Standards](../../../core/reverse-engineering-standards.md) - **Core methodology standard (primary reference)**
-- [Spec-Driven Development](../../../core/spec-driven-development.md) - Output format and review process
-- [Anti-Hallucination Guidelines](../../../core/anti-hallucination.md) - Evidence-based analysis requirements
-- [Code Review Checklist](../../../core/code-review-checklist.md) - Review guidelines
+- [Reverse Engineering Standards](../../core/reverse-engineering-standards.md) - **Core methodology standard (primary reference)**
+- [Spec-Driven Development](../../core/spec-driven-development.md) - Output format and review process
+- [Anti-Hallucination Guidelines](../../core/anti-hallucination.md) - Evidence-based analysis requirements
+- [Code Review Checklist](../../core/code-review-checklist.md) - Review guidelines
 
 ---
 
@@ -387,6 +389,7 @@ This skill auto-detects project configuration:
 
 | Version | Date | Changes |
 |---------|------|---------|
+| 1.2.0 | 2026-01-25 | Added: Reference to Unified Tag System |
 | 1.1.0 | 2026-01-19 | Add BDD/TDD pipeline integration; Add core standard reference |
 | 1.0.0 | 2026-01-19 | Initial release |