@lbruton/specflow 3.3.0 → 3.4.1

package/CHANGELOG.md

@@ -7,6 +7,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 SpecFlow is a fork of [Pimzino/spec-workflow-mcp](https://github.com/Pimzino/spec-workflow-mcp). Upstream releases (≤ 2.2.3) are preserved below. SpecFlow releases begin at 3.0.0.
 
+## [Unreleased]
+
+### Changed
+
+- Renamed `.spec-workflow` directory to `.specflow` across all projects and configuration
+- Added backward compatibility fallback for legacy `.spec-workflow/` directories
+
 ## [3.1.0] - 2026-03-31
 
 ### Added

package/README.ar.md

@@ -1,7 +1,7 @@
 # Spec Workflow MCP
 
 [![npm version](https://img.shields.io/npm/v/@pimzino/spec-workflow-mcp)](https://www.npmjs.com/package/@pimzino/spec-workflow-mcp)
-[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.spec-workflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp)
+[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.specflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp)
 
 خادم Model Context Protocol (MCP) للتطوير المنظم القائم على المواصفات مع لوحة تحكم فورية وإضافة VSCode.
 
@@ -70,7 +70,7 @@ npx -y @pimzino/spec-workflow-mcp@latest --dashboard
 
 **الخيار ب: إضافة VSCode** (موصى بها لمستخدمي VSCode)
 
-قم بتثبيت [Spec Workflow MCP Extension](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp) من سوق VSCode.
+قم بتثبيت [Spec Workflow MCP Extension](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp) من سوق VSCode.
 
 ## 📝 كيفية الاستخدام
 
@@ -225,7 +225,7 @@ claude mcp add spec-workflow cmd.exe /c "npx @pimzino/spec-workflow-mcp@latest /
 
 أضف إلى ملف التكوين `~/.codex/config.toml`:
 ```toml
-[mcp_servers.spec-workflow]
+[mcp_servers.specflow]
 command = "npx"
 args = ["-y", "@pimzino/spec-workflow-mcp@latest", "/path/to/your/project"]
 ```
@@ -242,7 +242,7 @@ docker-compose up --build
 
 # أو استخدام Docker CLI
 docker build -f containers/Dockerfile -t spec-workflow-mcp .
-docker run -p 5000:5000 -v "./workspace/.spec-workflow:/workspace/.spec-workflow:rw" spec-workflow-mcp
+docker run -p 5000:5000 -v "./workspace/.specflow:/workspace/.specflow:rw" spec-workflow-mcp
 ```
 
 ستكون لوحة التحكم متاحة على: http://localhost:5000
@@ -254,7 +254,7 @@ docker run -p 5000:5000 -v "./workspace/.spec-workflow:/workspace/.spec-workflow
 للبيئات المعزولة (مثل Codex CLI مع `sandbox_mode=workspace-write`) حيث يكون `$HOME` للقراءة فقط، استخدم متغير البيئة `SPEC_WORKFLOW_HOME` لإعادة توجيه ملفات الحالة العامة إلى موقع قابل للكتابة:
 
 ```bash
-SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
+SPEC_WORKFLOW_HOME=/workspace/.specflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
 ```
 
 [راجع دليل التكوين →](docs/CONFIGURATION.md#environment-variables)
@@ -274,7 +274,7 @@ SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-m
 
 ```
 your-project/
-  .spec-workflow/
+  .specflow/
     approvals/
     archive/
     specs/

package/README.de.md

@@ -1,7 +1,7 @@
 # Spec Workflow MCP
 
 [![npm version](https://img.shields.io/npm/v/@pimzino/spec-workflow-mcp)](https://www.npmjs.com/package/@pimzino/spec-workflow-mcp)
-[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.spec-workflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp)
+[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.specflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp)
 
 Ein Model Context Protocol (MCP) Server für strukturierte, spezifikationsgetriebene Entwicklung mit Echtzeit-Dashboard und VSCode Extension.
 
@@ -70,7 +70,7 @@ Das Dashboard ist erreichbar unter: http://localhost:5000
 
 **Option B: VSCode Extension** (Empfohlen für VSCode-Benutzer)
 
-Installieren Sie die [Spec Workflow MCP Extension](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp) aus dem VSCode-Marketplace.
+Installieren Sie die [Spec Workflow MCP Extension](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp) aus dem VSCode-Marketplace.
 
 ## 📝 Verwendung
 
@@ -225,7 +225,7 @@ Fügen Sie zu Ihrer `~/.codeium/windsurf/mcp_config.json` Konfigurationsdatei hi
 
 Fügen Sie zu Ihrer `~/.codex/config.toml` Konfigurationsdatei hinzu:
 ```toml
-[mcp_servers.spec-workflow]
+[mcp_servers.specflow]
 command = "npx"
 args = ["-y", "@pimzino/spec-workflow-mcp@latest", "/pfad/zu/ihrem/projekt"]
 ```
@@ -242,7 +242,7 @@ docker-compose up --build
 
 # Oder mit Docker CLI
 docker build -f containers/Dockerfile -t spec-workflow-mcp .
-docker run -p 5000:5000 -v "./workspace/.spec-workflow:/workspace/.spec-workflow:rw" spec-workflow-mcp
+docker run -p 5000:5000 -v "./workspace/.specflow:/workspace/.specflow:rw" spec-workflow-mcp
 ```
 
 Das Dashboard ist verfügbar unter: http://localhost:5000
@@ -254,7 +254,7 @@ Das Dashboard ist verfügbar unter: http://localhost:5000
 Für Sandbox-Umgebungen (z.B. Codex CLI mit `sandbox_mode=workspace-write`), in denen `$HOME` schreibgeschützt ist, verwenden Sie die Umgebungsvariable `SPEC_WORKFLOW_HOME`, um globale Zustandsdateien an einen beschreibbaren Ort umzuleiten:
 
 ```bash
-SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
+SPEC_WORKFLOW_HOME=/workspace/.specflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
 ```
 
 [Siehe Konfigurationsanleitung →](docs/CONFIGURATION.de.md#umgebungsvariablen)
@@ -274,7 +274,7 @@ SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-m
 
 ```
 ihr-projekt/
-  .spec-workflow/
+  .specflow/
     approvals/
     archive/
     specs/

package/README.es.md

@@ -1,7 +1,7 @@
 # Spec Workflow MCP
 
 [![npm version](https://img.shields.io/npm/v/@pimzino/spec-workflow-mcp)](https://www.npmjs.com/package/@pimzino/spec-workflow-mcp)
-[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.spec-workflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp)
+[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.specflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp)
 
 Un servidor Model Context Protocol (MCP) para desarrollo estructurado basado en especificaciones con panel de control en tiempo real y extensión para VSCode.
 
@@ -70,7 +70,7 @@ El panel de control estará accesible en: http://localhost:5000
 
 **Opción B: Extensión para VSCode** (Recomendado para usuarios de VSCode)
 
-Instala [Spec Workflow MCP Extension](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp) desde el marketplace de VSCode.
+Instala [Spec Workflow MCP Extension](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp) desde el marketplace de VSCode.
 
 ## 📝 Cómo Usar
 
@@ -225,7 +225,7 @@ Agrega a tu archivo de configuración `~/.codeium/windsurf/mcp_config.json`:
 
 Agrega a tu archivo de configuración `~/.codex/config.toml`:
 ```toml
-[mcp_servers.spec-workflow]
+[mcp_servers.specflow]
 command = "npx"
 args = ["-y", "@pimzino/spec-workflow-mcp@latest", "/ruta/a/tu/proyecto"]
 ```
@@ -242,7 +242,7 @@ docker-compose up --build
 
 # O usando Docker CLI
 docker build -f containers/Dockerfile -t spec-workflow-mcp .
-docker run -p 5000:5000 -v "./workspace/.spec-workflow:/workspace/.spec-workflow:rw" spec-workflow-mcp
+docker run -p 5000:5000 -v "./workspace/.specflow:/workspace/.specflow:rw" spec-workflow-mcp
 ```
 
 El panel de control estará disponible en: http://localhost:5000
@@ -254,7 +254,7 @@ El panel de control estará disponible en: http://localhost:5000
 Para entornos en sandbox (por ejemplo, Codex CLI con `sandbox_mode=workspace-write`) donde `$HOME` es de solo lectura, usa la variable de entorno `SPEC_WORKFLOW_HOME` para redirigir los archivos de estado global a una ubicación con permisos de escritura:
 
 ```bash
-SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
+SPEC_WORKFLOW_HOME=/workspace/.specflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
 ```
 
 [Ver Guía de Configuración →](docs/CONFIGURATION.es.md#environment-variables)
@@ -274,7 +274,7 @@ SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-m
 
 ```
 tu-proyecto/
-  .spec-workflow/
+  .specflow/
     approvals/
     archive/
     specs/

package/README.fr.md

@@ -1,7 +1,7 @@
 # Spec Workflow MCP
 
 [![npm version](https://img.shields.io/npm/v/@pimzino/spec-workflow-mcp)](https://www.npmjs.com/package/@pimzino/spec-workflow-mcp)
-[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.spec-workflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp)
+[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.specflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp)
 
 Un serveur Model Context Protocol (MCP) pour le développement structuré basé sur les spécifications avec tableau de bord en temps réel et extension VSCode.
 
@@ -70,7 +70,7 @@ Le tableau de bord sera accessible à : http://localhost:5000
 
 **Option B : Extension VSCode** (Recommandée pour les utilisateurs de VSCode)
 
-Installez l'[Extension Spec Workflow MCP](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp) depuis le marketplace VSCode.
+Installez l'[Extension Spec Workflow MCP](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp) depuis le marketplace VSCode.
 
 ## 📝 Comment utiliser
 
@@ -225,7 +225,7 @@ Ajoutez à votre fichier de configuration `~/.codeium/windsurf/mcp_config.json`
 
 Ajoutez à votre fichier de configuration `~/.codex/config.toml` :
 ```toml
-[mcp_servers.spec-workflow]
+[mcp_servers.specflow]
 command = "npx"
 args = ["-y", "@pimzino/spec-workflow-mcp@latest", "/chemin/vers/votre/projet"]
 ```
@@ -242,7 +242,7 @@ docker-compose up --build
 
 # Ou utilisation de Docker CLI
 docker build -f containers/Dockerfile -t spec-workflow-mcp .
-docker run -p 5000:5000 -v "./workspace/.spec-workflow:/workspace/.spec-workflow:rw" spec-workflow-mcp
+docker run -p 5000:5000 -v "./workspace/.specflow:/workspace/.specflow:rw" spec-workflow-mcp
 ```
 
 Le tableau de bord sera disponible à : http://localhost:5000
@@ -254,7 +254,7 @@ Le tableau de bord sera disponible à : http://localhost:5000
 Pour les environnements isolés (par exemple, Codex CLI avec `sandbox_mode=workspace-write`) où `$HOME` est en lecture seule, utilisez la variable d'environnement `SPEC_WORKFLOW_HOME` pour rediriger les fichiers d'état globaux vers un emplacement accessible en écriture :
 
 ```bash
-SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
+SPEC_WORKFLOW_HOME=/workspace/.specflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
 ```
 
 [Voir le guide de configuration →](docs/CONFIGURATION.fr.md#environment-variables)
@@ -274,7 +274,7 @@ SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-m
 
 ```
 votre-projet/
-  .spec-workflow/
+  .specflow/
     approvals/
     archive/
     specs/

package/README.it.md

@@ -1,7 +1,7 @@
 # Spec Workflow MCP
 
 [![npm version](https://img.shields.io/npm/v/@pimzino/spec-workflow-mcp)](https://www.npmjs.com/package/@pimzino/spec-workflow-mcp)
-[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.spec-workflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp)
+[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.specflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp)
 
 Un server Model Context Protocol (MCP) per lo sviluppo strutturato basato su specifiche con dashboard in tempo reale ed estensione VSCode.
 
@@ -70,7 +70,7 @@ La dashboard sarà accessibile a: http://localhost:5000
 
 **Opzione B: Estensione VSCode** (Consigliata per utenti VSCode)
 
-Installa [Spec Workflow MCP Extension](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp) dal marketplace VSCode.
+Installa [Spec Workflow MCP Extension](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp) dal marketplace VSCode.
 
 ## 📝 Come Utilizzare
 
@@ -225,7 +225,7 @@ Aggiungi al file di configurazione `~/.codeium/windsurf/mcp_config.json`:
 
 Aggiungi al file di configurazione `~/.codex/config.toml`:
 ```toml
-[mcp_servers.spec-workflow]
+[mcp_servers.specflow]
 command = "npx"
 args = ["-y", "@pimzino/spec-workflow-mcp@latest", "/path/to/your/project"]
 ```
@@ -242,7 +242,7 @@ docker-compose up --build
 
 # Oppure usando Docker CLI
 docker build -f containers/Dockerfile -t spec-workflow-mcp .
-docker run -p 5000:5000 -v "./workspace/.spec-workflow:/workspace/.spec-workflow:rw" spec-workflow-mcp
+docker run -p 5000:5000 -v "./workspace/.specflow:/workspace/.specflow:rw" spec-workflow-mcp
 ```
 
 La dashboard sarà disponibile a: http://localhost:5000
@@ -254,7 +254,7 @@ La dashboard sarà disponibile a: http://localhost:5000
 Per ambienti sandboxed (es. Codex CLI con `sandbox_mode=workspace-write`) dove `$HOME` è in sola lettura, usa la variabile d'ambiente `SPEC_WORKFLOW_HOME` per reindirizzare i file di stato globale in una posizione scrivibile:
 
 ```bash
-SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
+SPEC_WORKFLOW_HOME=/workspace/.specflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
 ```
 
 [Vedi Guida alla Configurazione →](docs/CONFIGURATION.it.md#variabili-dambiente)
@@ -274,7 +274,7 @@ SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-m
 
 ```
 your-project/
-  .spec-workflow/
+  .specflow/
     approvals/
     archive/
     specs/

package/README.ja.md

@@ -1,7 +1,7 @@
 # Spec Workflow MCP
 
 [![npm version](https://img.shields.io/npm/v/@pimzino/spec-workflow-mcp)](https://www.npmjs.com/package/@pimzino/spec-workflow-mcp)
-[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.spec-workflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp)
+[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.specflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp)
 
 リアルタイムダッシュボードとVSCode拡張機能を備えた、構造化された仕様駆動開発のためのModel Context Protocol (MCP) サーバーです。
 
@@ -72,7 +72,7 @@ npx -y @pimzino/spec-workflow-mcp@latest --dashboard
 
 **オプションB: VSCode拡張機能**（VSCodeユーザーに推奨）
 
-VSCodeマーケットプレイスから[Spec Workflow MCP Extension](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp)をインストールします。
+VSCodeマーケットプレイスから[Spec Workflow MCP Extension](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp)をインストールします。
 
 ## 📝 使い方
 
@@ -227,7 +227,7 @@ Cursor設定（`settings.json`）に追加します：
 
 `~/.codex/config.toml`設定ファイルに追加します：
 ```toml
-[mcp_servers.spec-workflow]
+[mcp_servers.specflow]
 command = "npx"
 args = ["-y", "@pimzino/spec-workflow-mcp@latest", "/path/to/your/project"]
 ```
@@ -244,7 +244,7 @@ docker-compose up --build
 
 # またはDocker CLIを使用
 docker build -f containers/Dockerfile -t spec-workflow-mcp .
-docker run -p 5000:5000 -v "./workspace/.spec-workflow:/workspace/.spec-workflow:rw" spec-workflow-mcp
+docker run -p 5000:5000 -v "./workspace/.specflow:/workspace/.specflow:rw" spec-workflow-mcp
 ```
 
 ダッシュボードは以下のURLで利用可能になります：http://localhost:5000
@@ -256,7 +256,7 @@ docker run -p 5000:5000 -v "./workspace/.spec-workflow:/workspace/.spec-workflow
 `$HOME`が読み取り専用のサンドボックス環境（例：Codex CLIの`sandbox_mode=workspace-write`）の場合、`SPEC_WORKFLOW_HOME`環境変数を使用してグローバル状態ファイルを書き込み可能な場所にリダイレクトします：
 
 ```bash
-SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
+SPEC_WORKFLOW_HOME=/workspace/.specflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
 ```
 
 [設定ガイドを見る →](docs/CONFIGURATION.ja.md#environment-variables)
@@ -276,7 +276,7 @@ SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-m
 
 ```
 your-project/
-  .spec-workflow/
+  .specflow/
     approvals/
     archive/
     specs/

package/README.ko.md

@@ -1,7 +1,7 @@
 # Spec Workflow MCP
 
 [![npm version](https://img.shields.io/npm/v/@pimzino/spec-workflow-mcp)](https://www.npmjs.com/package/@pimzino/spec-workflow-mcp)
-[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.spec-workflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp)
+[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.specflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp)
 
 실시간 대시보드와 VSCode 확장 프로그램을 갖춘 구조화된 스펙 기반 개발을 위한 Model Context Protocol(MCP) 서버입니다.
 
@@ -70,7 +70,7 @@ npx -y @pimzino/spec-workflow-mcp@latest --dashboard
 
 **옵션 B: VSCode 확장 프로그램** (VSCode 사용자 권장)
 
-VSCode 마켓플레이스에서 [Spec Workflow MCP Extension](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp)을 설치하세요.
+VSCode 마켓플레이스에서 [Spec Workflow MCP Extension](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp)을 설치하세요.
 
 ## 📝 사용 방법
 
@@ -225,7 +225,7 @@ Cursor 설정(`settings.json`)에 추가:
 
 `~/.codex/config.toml` 구성 파일에 추가:
 ```toml
-[mcp_servers.spec-workflow]
+[mcp_servers.specflow]
 command = "npx"
 args = ["-y", "@pimzino/spec-workflow-mcp@latest", "/path/to/your/project"]
 ```
@@ -242,7 +242,7 @@ docker-compose up --build
 
 # 또는 Docker CLI 사용
 docker build -f containers/Dockerfile -t spec-workflow-mcp .
-docker run -p 5000:5000 -v "./workspace/.spec-workflow:/workspace/.spec-workflow:rw" spec-workflow-mcp
+docker run -p 5000:5000 -v "./workspace/.specflow:/workspace/.specflow:rw" spec-workflow-mcp
 ```
 
 대시보드는 http://localhost:5000 에서 사용 가능합니다.
@@ -254,7 +254,7 @@ docker run -p 5000:5000 -v "./workspace/.spec-workflow:/workspace/.spec-workflow
 `$HOME`이 읽기 전용인 샌드박스 환경(예: `sandbox_mode=workspace-write`가 있는 Codex CLI)의 경우 `SPEC_WORKFLOW_HOME` 환경 변수를 사용하여 전역 상태 파일을 쓰기 가능한 위치로 리디렉션하세요:
 
 ```bash
-SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
+SPEC_WORKFLOW_HOME=/workspace/.specflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
 ```
 
 [구성 가이드 보기 →](docs/CONFIGURATION.md#environment-variables)
@@ -274,7 +274,7 @@ SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-m
 
 ```
 your-project/
-  .spec-workflow/
+  .specflow/
     approvals/
     archive/
     specs/

package/README.md

@@ -117,20 +117,109 @@ Code Context is a [hardened fork](https://github.com/lbruton/claude-context) of
 | Self-hosted | Files | Files | Files | Files | Files | Node.js | **Milvus, Neo4j + cloud optional** |
 | Best for | Quick adoption | Enterprise teams | Solo context eng. | PRD pipelines | Per-repo memory | Structured workflow | **Multi-project governance** |
 
+## Multi-Agent Support
+
+SpecFlow works as an MCP server, which means any agent that speaks the MCP protocol can use it. Verified with all three major coding agents:
+
+| Agent | MCP Loading | Spec Lifecycle | Skills |
+|-------|------------|----------------|--------|
+| **Claude Code** | MCP via npm, plugin via git clone | Full | 60+ skills via SKILL.md |
+| **Gemini CLI** | Manual MCP config | Full | Via GEMINI.md instructions |
+| **Codex CLI** | Manual MCP config | Full | Via CODEX.md instructions |
+
+All three agents share the same MCP tools, DocVault knowledge base, and spec workflow. Agent-specific instruction files (CLAUDE.md, GEMINI.md, CODEX.md) tailor behavior to each agent's capabilities.
+
+### Cross-Agent Spec Handoff
+
+Spec state lives on disk in `.specflow/specs/` — not in any agent's memory. This means you can start a spec in one agent and continue in another:
+
+```
+Claude Code                    Codex CLI                      Gemini CLI
+────────────                   ─────────                      ──────────
+/issue create                  @spec resume                   @spec resume
+  → creates SWF-65               → reads spec from disk         → reads spec from disk
+/discover SWF-65                 → runs Phase 3 (Tasks)          → runs Phase 4 (Implement)
+  → discovery brief               → generates task list            → implements tasks
+/spec SWF-65                     → writes tasks.md                → commits code
+  → Phase 1 (Requirements)      → awaits approval                → logs implementation
+  → Phase 2 (Design)
+  → awaits approval
+```
+
+Each agent reads the current spec state, advances the workflow, and writes the result back to disk. The dashboard shows progress regardless of which agent is driving. Use whichever agent is best suited for each phase — Claude for discovery and design, Codex for implementation, Gemini for review.
+
 ## Quick Start
 
-### As a Claude Code Plugin (recommended)
+### Claude Code
+
+**Step 1 — Install the MCP server** (provides tools and prompts):
+
+Add to your user-level settings (`~/.claude/settings.json`):
+
+```json
+{
+  "mcpServers": {
+    "specflow": {
+      "command": "npx",
+      "args": ["-y", "@lbruton/specflow@latest", "."]
+    }
+  }
+}
+```
+
+**Step 2 — Install the plugin** (optional — provides skills and slash commands):
+
+```bash
+git clone https://github.com/lbruton/specflow.git
+cp -r specflow/plugin/ ~/.claude/plugins/marketplaces/specflow-marketplace/
+```
+
+Skills like `/prime`, `/wrap`, `/spec` are available immediately after restarting Claude Code.
+
+> **Note:** The plugin provides skills and commands only — it does not start the MCP server. The MCP server must be installed separately via Step 1.
+
+### Gemini CLI — Manual Install
 
 ```bash
 git clone https://github.com/lbruton/specflow.git
 cd specflow
 npm install && npm run build
+```
+
+Add to your Gemini MCP config (`~/.gemini/settings.json` or project-level):
 
-# Symlink into Claude Code plugins
-ln -s "$(pwd)" ~/.claude/plugins/marketplaces/specflow-marketplace
+```json
+{
+  "mcpServers": {
+    "spec-workflow": {
+      "command": "node",
+      "args": ["/path/to/specflow/dist/index.js", "/path/to/your/project"]
+    }
+  }
+}
 ```
 
-### As an MCP Server
+Copy `GEMINI.md` from the specflow repo root into your project root for agent-specific instructions.
+
+### Codex CLI — Manual Install
+
+```bash
+git clone https://github.com/lbruton/specflow.git
+cd specflow
+npm install && npm run build
+```
+
+Add to your Codex MCP config (`.codex/config.toml` or user-level):
+
+```toml
+[mcp.specflow]
+command = "node"
+args = ["/path/to/specflow/dist/index.js", "/path/to/your/project"]
+```
+
+Copy `CODEX.md` from the specflow repo root into your project root for agent-specific instructions.
+
+### Any MCP-Compatible Agent — Via npx
 
 ```json
 {

package/README.pt.md

@@ -1,7 +1,7 @@
 # Spec Workflow MCP
 
 [![npm version](https://img.shields.io/npm/v/@pimzino/spec-workflow-mcp)](https://www.npmjs.com/package/@pimzino/spec-workflow-mcp)
-[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.spec-workflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp)
+[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.specflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp)
 
 Um servidor Model Context Protocol (MCP) para desenvolvimento estruturado orientado por especificações com dashboard em tempo real e extensão VSCode.
 
@@ -70,7 +70,7 @@ O dashboard estará acessível em: http://localhost:5000
 
 **Opção B: Extensão VSCode** (Recomendado para usuários do VSCode)
 
-Instale a [Extensão Spec Workflow MCP](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp) do marketplace do VSCode.
+Instale a [Extensão Spec Workflow MCP](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp) do marketplace do VSCode.
 
 ## 📝 Como Usar
 
@@ -225,7 +225,7 @@ Adicione ao arquivo de configuração `~/.codeium/windsurf/mcp_config.json`:
 
 Adicione ao arquivo de configuração `~/.codex/config.toml`:
 ```toml
-[mcp_servers.spec-workflow]
+[mcp_servers.specflow]
 command = "npx"
 args = ["-y", "@pimzino/spec-workflow-mcp@latest", "/path/to/your/project"]
 ```
@@ -242,7 +242,7 @@ docker-compose up --build
 
 # Ou usando Docker CLI
 docker build -f containers/Dockerfile -t spec-workflow-mcp .
-docker run -p 5000:5000 -v "./workspace/.spec-workflow:/workspace/.spec-workflow:rw" spec-workflow-mcp
+docker run -p 5000:5000 -v "./workspace/.specflow:/workspace/.specflow:rw" spec-workflow-mcp
 ```
 
 O dashboard estará disponível em: http://localhost:5000
@@ -254,7 +254,7 @@ O dashboard estará disponível em: http://localhost:5000
 Para ambientes isolados (por exemplo, Codex CLI com `sandbox_mode=workspace-write`) onde `$HOME` é somente leitura, use a variável de ambiente `SPEC_WORKFLOW_HOME` para redirecionar arquivos de estado global para um local gravável:
 
 ```bash
-SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
+SPEC_WORKFLOW_HOME=/workspace/.specflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
 ```
 
 [Veja Guia de Configuração →](docs/CONFIGURATION.pt.md#environment-variables)
@@ -274,7 +274,7 @@ SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-m
 
 ```
 your-project/
-  .spec-workflow/
+  .specflow/
     approvals/
     archive/
     specs/

package/README.ru.md

@@ -1,7 +1,7 @@
 # Spec Workflow MCP
 
 [![npm version](https://img.shields.io/npm/v/@pimzino/spec-workflow-mcp)](https://www.npmjs.com/package/@pimzino/spec-workflow-mcp)
-[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.spec-workflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp)
+[![VSCode Extension](https://vsmarketplacebadges.dev/version-short/Pimzino.specflow-mcp.svg)](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp)
 
 Сервер Model Context Protocol (MCP) для структурированной разработки на основе спецификаций с панелью управления в реальном времени и расширением для VSCode.
 
@@ -70,7 +70,7 @@ npx -y @pimzino/spec-workflow-mcp@latest --dashboard
 
 **Вариант B: Расширение для VSCode** (Рекомендуется для пользователей VSCode)
 
-Установите [Spec Workflow MCP Extension](https://marketplace.visualstudio.com/items?itemName=Pimzino.spec-workflow-mcp) из магазина VSCode.
+Установите [Spec Workflow MCP Extension](https://marketplace.visualstudio.com/items?itemName=Pimzino.specflow-mcp) из магазина VSCode.
 
 ## 📝 Как использовать
 
@@ -225,7 +225,7 @@ claude mcp add spec-workflow cmd.exe /c "npx @pimzino/spec-workflow-mcp@latest /
 
 Добавьте в файл конфигурации `~/.codex/config.toml`:
 ```toml
-[mcp_servers.spec-workflow]
+[mcp_servers.specflow]
 command = "npx"
 args = ["-y", "@pimzino/spec-workflow-mcp@latest", "/path/to/your/project"]
 ```
@@ -242,7 +242,7 @@ docker-compose up --build
 
 # Или использование Docker CLI
 docker build -f containers/Dockerfile -t spec-workflow-mcp .
-docker run -p 5000:5000 -v "./workspace/.spec-workflow:/workspace/.spec-workflow:rw" spec-workflow-mcp
+docker run -p 5000:5000 -v "./workspace/.specflow:/workspace/.specflow:rw" spec-workflow-mcp
 ```
 
 Панель управления будет доступна по адресу: http://localhost:5000
@@ -254,7 +254,7 @@ docker run -p 5000:5000 -v "./workspace/.spec-workflow:/workspace/.spec-workflow
 Для изолированных сред (например, Codex CLI с `sandbox_mode=workspace-write`), где `$HOME` доступен только для чтения, используйте переменную окружения `SPEC_WORKFLOW_HOME` для перенаправления глобальных файлов состояния в доступную для записи папку:
 
 ```bash
-SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
+SPEC_WORKFLOW_HOME=/workspace/.specflow-mcp npx -y @pimzino/spec-workflow-mcp@latest /workspace
 ```
 
 [См. руководство по конфигурации →](docs/CONFIGURATION.ru.md#environment-variables)
@@ -274,7 +274,7 @@ SPEC_WORKFLOW_HOME=/workspace/.spec-workflow-mcp npx -y @pimzino/spec-workflow-m
 
 ```
 your-project/
-  .spec-workflow/
+  .specflow/
     approvals/
     archive/
     specs/