chore(release): bump to v5.3.0

Critical bug fixes (mapfile, agent registration, verify.sh, task detection)
and comprehensive documentation overhaul across 32 files.

Author: Habib0x0

.claude-plugin/marketplace.json

@@ -8,7 +8,7 @@
     {
       "name": "spec-driven",
       "description": "Structured workflow for spec-driven development with EARS notation, guiding features through Requirements, Design, and Tasks phases",
-      "version": "5.2.0",
+      "version": "5.3.0",
       "author": {
         "name": "habib0x"
       },

.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "spec-driven",
-  "version": "5.2.0",
+  "version": "5.3.0",
   "description": "Spec-driven development workflow with structured requirements, design, and task phases",
   "author": {
     "name": "habib0x"

.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "spec-driven",
-  "version": "5.2.0",
+  "version": "5.3.0",
   "description": "Spec-driven development workflow with structured requirements, design, tasks, and autonomous execution.",
   "author": {
     "name": "habib0x",

CHANGELOG.md

@@ -2,7 +2,7 @@
 
 All notable changes to the spec-driven plugin are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/) and this project adheres to [Semantic Versioning](https://semver.org/).
 
-## [5.2.0] - 2026-04-29
+## [5.3.0] - 2026-04-29
 
 ### Fixed
 
@@ -35,6 +35,13 @@ All notable changes to the spec-driven plugin are documented here. The format fo
 - Updated `skills/spec-workflow/SKILL.md` to version 5.2.0.
 - Synced `.codex-plugin/plugin.json` to version 5.2.0.
 
+## [5.2.0] - 2026-04-28
+
+### Added
+
+- **`/zoom-out` command.** Maps modules, interfaces, and callers for unfamiliar sections of a codebase. Useful for getting oriented before starting a spec.
+- **`/ubiquitous-language` command.** Extracts domain terms from the codebase into a canonical glossary and flags ambiguous or inconsistent naming.
+
 ## [5.1.1] - 2026-04-26
 
 ### Fixed

skills/spec-workflow/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: spec-workflow
 description: This skill should be used when the user asks to "create a spec", "write requirements", "design a feature", "plan implementation", "use EARS notation", "create user stories", "break down tasks", "write a PRD", "technical specification", or mentions "spec-driven development", "feature spec", "requirements phase", "design phase", or "tasks phase". Provides structured 3-phase workflow for feature development.
-version: 5.2.0
+version: 5.3.0
 ---
 
 # Spec-Driven Development Workflow