@anhth2/spec-driven-dev-plugin 0.5.0 → 0.6.0

package/ARCHITECTURE.md

@@ -128,7 +128,7 @@ Available modules (modules/):
   dotnet, golang, php-laravel, context-engineering
 
 Usage:
-  npx @anhth2/spec-driven-dev --module java-spring
+  npx @anhth2/spec-driven-dev-plugin --module java-spring
     └─ copies modules/java-spring/ → consumer/.agent/modules/java-spring/
 
 At runtime, context-loader.md reads:

package/bin/index.js

@@ -25,7 +25,7 @@ const AVAILABLE_MODULES = [
 ];
 
 if (showHelp) {
-  console.log('Usage: npx @anhth2/spec-driven-dev [options]');
+  console.log('Usage: npx @anhth2/spec-driven-dev-plugin [options]');
   console.log('');
   console.log('Install modes:');
   console.log('  --init             NEW: Install framework to .agent/ + create shortcuts in .claude/commands/');
@@ -41,9 +41,9 @@ if (showHelp) {
   AVAILABLE_MODULES.forEach(m => console.log(`  ${m}`));
   console.log('');
   console.log('Examples:');
-  console.log('  npx @anhth2/spec-driven-dev --init                         # new project setup');
-  console.log('  npx @anhth2/spec-driven-dev --init --module java-spring    # with stack module');
-  console.log('  npx @anhth2/spec-driven-dev --project --hooks              # legacy project install');
+  console.log('  npx @anhth2/spec-driven-dev-plugin --init                         # new project setup');
+  console.log('  npx @anhth2/spec-driven-dev-plugin --init --module java-spring    # with stack module');
+  console.log('  npx @anhth2/spec-driven-dev-plugin --project --hooks              # legacy project install');
   process.exit(0);
 }
 
@@ -157,7 +157,7 @@ if (isInit) {
   console.log('  2. Commit .agent/ to git so your whole team has the framework');
   console.log('');
   console.log('To upgrade later:  bash scripts/upgrade.sh');
-  console.log('                   (or: npx @anhth2/spec-driven-dev@latest --init)');
+  console.log('                   (or: npx @anhth2/spec-driven-dev-plugin@latest --init)');
   console.log('');
   process.exit(0);
 }

package/commands/setup-ai-first.md

@@ -86,15 +86,17 @@ Wait for explicit "Y" or "N" from the user before continuing.
 - "N" → stop and ask what the user wants to change.
 
 
-*Note: For this command, there is no input file. Skip Step 1 file discovery. In Step 2, skip project-context.yaml loading (it does not exist yet). Ask: "Which project are you setting up? Give me the root path of the project."*
+*Note: For this command — **skip Gate Steps 1, 2, and 3** (there is no input file and no project context yet). Only run Step 0-B (model check). The project root is the **current working directory**. Proceed directly to the Precondition Check below.*
 
 ---
 
 ## Precondition Check
 
 Check if already set up:
-- If `.claude/commands/` exists with `.md` files → report "Already set up."
-- If `specs/` exists → offer to re-initialize or skip
+- If `CLAUDE.md` **and** `.agent/project-context.yaml` both exist → ask: "This project is already initialized. Re-run setup to regenerate config files? (Y/N)"
+  - N → stop
+  - Y → continue (existing files will be preserved — each step will offer merge/skip)
+- If only `specs/` exists or only partial setup detected → continue normally (safe to re-run)
 
 ## Step 1 — Create Directory Structure
 
@@ -171,7 +173,7 @@ commit_feature: "feat({{TICKET_PREFIX}}-{N}): {description}"
 
 ## Step 3 — Create project-context.yaml
 
-Create `.agent/project-context.yaml` using `templates/project-context.yaml` as the source template.
+Create `.agent/project-context.yaml` using `.agent/templates/project-context.yaml` as the source template.
 
 Copy the template and instruct: "Open `.agent/project-context.yaml` and fill in all `{{PLACEHOLDER}}` values. The `paths` section is pre-configured with sensible defaults — adjust if your project uses different directory names."
 
@@ -254,7 +256,21 @@ Create `specs/domain-knowledge/core-entities.md` if it does not exist:
 
 Instruct: "Open `specs/domain-knowledge/core-entities.md` and define your key domain entities. Start with aggregate roots. This file is loaded by every AI command — good definitions here save significant back-and-forth during code generation."
 
-## Step 6 — Verify
+## Step 6 — Install VS Code Extension (Recommended)
+
+Recommend the user install the **Spec Driven Dev** VS Code extension — it provides Review Board + Living Documentation panels that integrate with this workflow.
+
+```bash
+code --install-extension edupia-team.spec-driven-dev-team
+```
+
+Or: VS Code → `Ctrl+Shift+P` → **"Extensions: Install from Marketplace"** → search **Spec Driven Dev**.
+
+**What it does:**
+- 📋 **Review Board** — visual UI to review findings from `/refine-prd`, `/review-context`, `/review-tech-docs`
+- 📊 **Living Documentation** — traceability dashboard driven by `.trace/*.tsv`
+
+## Step 7 — Verify
 
 - [ ] `specs/` exists
 - [ ] `specs/domain-knowledge/` exists
@@ -274,5 +290,7 @@ Next:
   3. Fill specs/domain-knowledge/business-dictionary.md  ← terminology rules
   4. Fill specs/domain-knowledge/core-entities.md        ← entity glossary for code gen
   5. git add and commit those 4 files
-  6. /define-product to start your first feature
+  6. Install VS Code extension (if not yet installed):
+     code --install-extension edupia-team.spec-driven-dev-team
+  7. /define-product to start your first feature
 ```

package/commands/setup-ai-first.tmpl

@@ -5,15 +5,17 @@ Walk the user through a one-time setup that creates all required directories, in
 ## Gate
 {{include:steps/gate.md}}
 
-*Note: For this command, there is no input file. Skip Step 1 file discovery. In Step 2, skip project-context.yaml loading (it does not exist yet). Ask: "Which project are you setting up? Give me the root path of the project."*
+*Note: For this command — **skip Gate Steps 1, 2, and 3** (there is no input file and no project context yet). Only run Step 0-B (model check). The project root is the **current working directory**. Proceed directly to the Precondition Check below.*
 
 ---
 
 ## Precondition Check
 
 Check if already set up:
-- If `.claude/commands/` exists with `.md` files → report "Already set up."
-- If `specs/` exists → offer to re-initialize or skip
+- If `CLAUDE.md` **and** `.agent/project-context.yaml` both exist → ask: "This project is already initialized. Re-run setup to regenerate config files? (Y/N)"
+  - N → stop
+  - Y → continue (existing files will be preserved — each step will offer merge/skip)
+- If only `specs/` exists or only partial setup detected → continue normally (safe to re-run)
 
 ## Step 1 — Create Directory Structure
 
@@ -90,7 +92,7 @@ commit_feature: "feat({{TICKET_PREFIX}}-{N}): {description}"
 
 ## Step 3 — Create project-context.yaml
 
-Create `.agent/project-context.yaml` using `templates/project-context.yaml` as the source template.
+Create `.agent/project-context.yaml` using `.agent/templates/project-context.yaml` as the source template.
 
 Copy the template and instruct: "Open `.agent/project-context.yaml` and fill in all `{{PLACEHOLDER}}` values. The `paths` section is pre-configured with sensible defaults — adjust if your project uses different directory names."
 
@@ -173,7 +175,21 @@ Create `specs/domain-knowledge/core-entities.md` if it does not exist:
 
 Instruct: "Open `specs/domain-knowledge/core-entities.md` and define your key domain entities. Start with aggregate roots. This file is loaded by every AI command — good definitions here save significant back-and-forth during code generation."
 
-## Step 6 — Verify
+## Step 6 — Install VS Code Extension (Recommended)
+
+Recommend the user install the **Spec Driven Dev** VS Code extension — it provides Review Board + Living Documentation panels that integrate with this workflow.
+
+```bash
+code --install-extension edupia-team.spec-driven-dev-team
+```
+
+Or: VS Code → `Ctrl+Shift+P` → **"Extensions: Install from Marketplace"** → search **Spec Driven Dev**.
+
+**What it does:**
+- 📋 **Review Board** — visual UI to review findings from `/refine-prd`, `/review-context`, `/review-tech-docs`
+- 📊 **Living Documentation** — traceability dashboard driven by `.trace/*.tsv`
+
+## Step 7 — Verify
 
 - [ ] `specs/` exists
 - [ ] `specs/domain-knowledge/` exists
@@ -193,5 +209,7 @@ Next:
   3. Fill specs/domain-knowledge/business-dictionary.md  ← terminology rules
   4. Fill specs/domain-knowledge/core-entities.md        ← entity glossary for code gen
   5. git add and commit those 4 files
-  6. /define-product to start your first feature
+  6. Install VS Code extension (if not yet installed):
+     code --install-extension edupia-team.spec-driven-dev-team
+  7. /define-product to start your first feature
 ```

package/core/FRAMEWORK_VERSION

@@ -1 +1 @@
-0.5.0
+0.6.0

package/core/commands/setup-ai-first.md

@@ -86,15 +86,17 @@ Wait for explicit "Y" or "N" from the user before continuing.
 - "N" → stop and ask what the user wants to change.
 
 
-*Note: For this command, there is no input file. Skip Step 1 file discovery. In Step 2, skip project-context.yaml loading (it does not exist yet). Ask: "Which project are you setting up? Give me the root path of the project."*
+*Note: For this command — **skip Gate Steps 1, 2, and 3** (there is no input file and no project context yet). Only run Step 0-B (model check). The project root is the **current working directory**. Proceed directly to the Precondition Check below.*
 
 ---
 
 ## Precondition Check
 
 Check if already set up:
-- If `.claude/commands/` exists with `.md` files → report "Already set up."
-- If `specs/` exists → offer to re-initialize or skip
+- If `CLAUDE.md` **and** `.agent/project-context.yaml` both exist → ask: "This project is already initialized. Re-run setup to regenerate config files? (Y/N)"
+  - N → stop
+  - Y → continue (existing files will be preserved — each step will offer merge/skip)
+- If only `specs/` exists or only partial setup detected → continue normally (safe to re-run)
 
 ## Step 1 — Create Directory Structure
 
@@ -171,7 +173,7 @@ commit_feature: "feat({{TICKET_PREFIX}}-{N}): {description}"
 
 ## Step 3 — Create project-context.yaml
 
-Create `.agent/project-context.yaml` using `templates/project-context.yaml` as the source template.
+Create `.agent/project-context.yaml` using `.agent/templates/project-context.yaml` as the source template.
 
 Copy the template and instruct: "Open `.agent/project-context.yaml` and fill in all `{{PLACEHOLDER}}` values. The `paths` section is pre-configured with sensible defaults — adjust if your project uses different directory names."
 
@@ -254,7 +256,21 @@ Create `specs/domain-knowledge/core-entities.md` if it does not exist:
 
 Instruct: "Open `specs/domain-knowledge/core-entities.md` and define your key domain entities. Start with aggregate roots. This file is loaded by every AI command — good definitions here save significant back-and-forth during code generation."
 
-## Step 6 — Verify
+## Step 6 — Install VS Code Extension (Recommended)
+
+Recommend the user install the **Spec Driven Dev** VS Code extension — it provides Review Board + Living Documentation panels that integrate with this workflow.
+
+```bash
+code --install-extension edupia-team.spec-driven-dev-team
+```
+
+Or: VS Code → `Ctrl+Shift+P` → **"Extensions: Install from Marketplace"** → search **Spec Driven Dev**.
+
+**What it does:**
+- 📋 **Review Board** — visual UI to review findings from `/refine-prd`, `/review-context`, `/review-tech-docs`
+- 📊 **Living Documentation** — traceability dashboard driven by `.trace/*.tsv`
+
+## Step 7 — Verify
 
 - [ ] `specs/` exists
 - [ ] `specs/domain-knowledge/` exists
@@ -274,5 +290,7 @@ Next:
   3. Fill specs/domain-knowledge/business-dictionary.md  ← terminology rules
   4. Fill specs/domain-knowledge/core-entities.md        ← entity glossary for code gen
   5. git add and commit those 4 files
-  6. /define-product to start your first feature
+  6. Install VS Code extension (if not yet installed):
+     code --install-extension edupia-team.spec-driven-dev-team
+  7. /define-product to start your first feature
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anhth2/spec-driven-dev-plugin",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "description": "AI-First Spec-Driven Development workflow plugin for Claude Code",
   "bin": {
     "spec-driven-dev": "./bin/index.js"

package/scripts/init.sh

@@ -33,10 +33,10 @@ fi
 
 # ── Run installer via npx ─────────────────────────────────────────────────────
 
-echo "Running: npx @anhth2/spec-driven-dev --init $*"
+echo "Running: npx @anhth2/spec-driven-dev-plugin --init $*"
 echo ""
 
-npx -y @anhth2/spec-driven-dev --init "$@"
+npx -y @anhth2/spec-driven-dev-plugin --init "$@"
 
 echo ""
 echo "✅ Init complete!"

package/scripts/upgrade.sh

@@ -8,7 +8,7 @@
 # What it does:
 #   1. Reads current installed version from .agent/FRAMEWORK_VERSION
 #   2. Checks npm registry for the latest published version
-#   3. If newer: runs npx @anhth2/spec-driven-dev@latest --init to update .agent/
+#   3. If newer: runs npx @anhth2/spec-driven-dev-plugin@latest --init to update .agent/
 #   4. Reports what changed so you can review before committing
 #
 # Requirements:
@@ -46,7 +46,7 @@ if [ ! -f "$VERSION_FILE" ]; then
   echo ""
   echo "     bash scripts/init.sh"
   echo "   or:"
-  echo "     npx @anhth2/spec-driven-dev --init"
+  echo "     npx @anhth2/spec-driven-dev-plugin --init"
   echo ""
   exit 1
 fi
@@ -56,7 +56,7 @@ fi
 CURRENT=$(cat "$VERSION_FILE" | tr -d '[:space:]')
 echo "Checking npm registry ..."
 
-LATEST=$(npm view @anhth2/spec-driven-dev version 2>/dev/null || echo "unknown")
+LATEST=$(npm view @anhth2/spec-driven-dev-plugin version 2>/dev/null || echo "unknown")
 
 echo ""
 echo "  Installed : v${CURRENT}"
@@ -79,7 +79,7 @@ fi
 echo "Upgrading v${CURRENT} → v${LATEST} ..."
 echo ""
 
-npx -y @anhth2/spec-driven-dev@latest --init "$@"
+npx -y @anhth2/spec-driven-dev-plugin@latest --init "$@"
 
 # ── Post-upgrade guidance ─────────────────────────────────────────────────────