dev-playbooks 1.2.7 → 1.2.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dev-playbooks",
-  "version": "1.2.7",
+  "version": "1.2.8",
   "description": "AI-powered spec-driven development workflow",
   "keywords": [
     "devbooks",

package/skills/_shared/references/universal-gating-protocol.md

@@ -39,9 +39,9 @@ From now on, each time you write files, restate the `<truth-root>` and `<change-
 | Spec deltas | `<change-root>/<change-id>/specs/` | `./specs/` |
 | Traceability doc | `<change-root>/<change-id>/verification.md` | `./verification.md` |
 
-### DevBooks 2.0 Default Paths
+### Dev-Playbooks Default Paths
 
-When using DevBooks 2.0 protocol:
+When using Dev-Playbooks protocol:
 - `<change-root>` = `dev-playbooks/changes`
 - `<truth-root>` = `dev-playbooks/specs`
 

package/skills/devbooks-archiver/SKILL.md

@@ -49,7 +49,7 @@ proposal → design → test-owner(P1) → coder → test-owner(P2) → code-rev
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use the mappings within
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 4. If still unable to determine → **Stop and ask the user**
 

package/skills/devbooks-brownfield-bootstrap/SKILL.md

@@ -20,7 +20,7 @@ allowed-tools:
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 5. If still unable to determine → **Create DevBooks directory structure and initialize basic configuration**
 

package/skills/devbooks-code-review/SKILL.md

@@ -45,7 +45,7 @@ proposal → design → test-owner(phase1) → coder → test-owner(phase2) →
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) -> Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) -> template protocol, use default mappings
 4. If still undetermined -> **Stop and ask user**
 

package/skills/devbooks-coder/SKILL.md

@@ -53,7 +53,7 @@ proposal → design → test-owner(phase1) → [Coder] → test-owner(phase2)
 
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) -> Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) -> template protocol, use default mappings
 5. If still unable to determine -> **Stop and ask the user**
 
@@ -161,7 +161,7 @@ GOOD: 3 tests failed, see <change-root>/<change-id>/evidence/green-final/test-ou
 
 **Correct path examples**:
 ```bash
-# DevBooks 2.0 default path
+# Dev-Playbooks default path
 dev-playbooks/changes/<change-id>/evidence/green-final/test-$(date +%Y%m%d-%H%M%S).log
 
 # Using the script

package/skills/devbooks-delivery-workflow/SKILL.md

@@ -19,7 +19,7 @@ allowed-tools:
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) -> Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) -> template protocol, use default mappings
 4. If still undetermined -> **Stop and ask the user**
 

package/skills/devbooks-delivery-workflow/scripts/change-check.sh

@@ -529,7 +529,7 @@ check_spec_deltas() {
 }
 
 # =============================================================================
-# Constitution Check (DevBooks 2.0)
+# Constitution Check (Dev-Playbooks)
 # Verify project constitution is present and valid
 # =============================================================================
 check_constitution() {
@@ -557,7 +557,7 @@ check_constitution() {
 }
 
 # =============================================================================
-# Fitness Check (DevBooks 2.0)
+# Fitness Check (Dev-Playbooks)
 # Verify architecture fitness rules
 # =============================================================================
 check_fitness() {
@@ -1037,9 +1037,9 @@ else
   check_verification
   check_no_tests_changed
   check_implicit_changes
-  # DevBooks 2.0: Constitution check
+  # Dev-Playbooks: Constitution check
   check_constitution               # Constitution validity check (strict mode)
-  # DevBooks 2.0: Fitness check
+  # Dev-Playbooks: Fitness check
   check_fitness                    # Architecture fitness check (apply/archive/strict)
   # New quality gates (harden-devbooks-quality-gates)
   check_evidence_closure       # AC-001: Green evidence required for archive

package/skills/devbooks-design-backport/SKILL.md

@@ -52,7 +52,7 @@ coder has deviations → archiver auto-detects and backports during archive →
 
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 4. If still undetermined → **Stop and ask the user**
 

package/skills/devbooks-design-doc/SKILL.md

@@ -40,7 +40,7 @@ proposal → [Design Doc] → spec-contract → implementation-plan → test-own
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 5. If still unable to determine → **Stop and ask user**
 

package/skills/devbooks-docs-sync/SKILL.md

@@ -16,7 +16,7 @@ allowed-tools:
 
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use the mappings within
-2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) -> Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) -> Template protocol, use default mappings
 4. If still undetermined -> **Stop and ask the user**
 

package/skills/devbooks-entropy-monitor/SKILL.md

@@ -19,7 +19,7 @@ allowed-tools:
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 5. If still unable to determine → **Stop and ask the user**
 

package/skills/devbooks-impact-analysis/SKILL.md

@@ -17,7 +17,7 @@ allowed-tools:
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use the mappings within
-2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) -> Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) -> template protocol, use default mappings
 5. If still unable to determine -> **Stop and ask the user**
 

package/skills/devbooks-implementation-plan/SKILL.md

@@ -54,7 +54,7 @@ proposal → design → [Implementation Plan] → test-owner(phase1) → coder
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 5. If still unable to determine → **Stop and ask the user**
 

package/skills/devbooks-proposal-author/SKILL.md

@@ -18,7 +18,7 @@ allowed-tools:
 
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) -> Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) -> Template protocol, use default mappings
 4. If still undetermined -> **Stop and ask the user**
 

package/skills/devbooks-proposal-challenger/SKILL.md

@@ -16,7 +16,7 @@ allowed-tools:
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 4. If still undetermined → **Stop and ask user**
 

package/skills/devbooks-proposal-judge/SKILL.md

@@ -18,7 +18,7 @@ allowed-tools:
 
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 5. If still unable to determine → **Stop and ask the user**
 

package/skills/devbooks-router/SKILL.md

@@ -32,7 +32,7 @@ allowed-tools:
 
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 4. If still undetermined → **Stop and ask user**
 

package/skills/devbooks-spec-contract/SKILL.md

@@ -21,7 +21,7 @@ allowed-tools:
 
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) -> Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) -> Template protocol, use default mappings
 5. If still unable to determine -> **Stop and ask the user**
 

package/skills/devbooks-test-owner/SKILL.md

@@ -59,7 +59,7 @@ When user says "Coder is done, please verify" or similar, Test Owner enters **Ph
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 5. If still unable to determine → **Stop and ask user**
 
@@ -205,7 +205,7 @@ Test Owner must produce a structured `verification.md` that serves as both test
 
 **Correct path examples**:
 ```bash
-# DevBooks 2.0 default path
+# Dev-Playbooks default path
 dev-playbooks/changes/<change-id>/evidence/red-baseline/test-$(date +%Y%m%d-%H%M%S).log
 
 # Using the script

package/skills/devbooks-test-reviewer/SKILL.md

@@ -14,7 +14,7 @@ allowed-tools:
 
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use the mappings within
-2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) -> Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) -> Template protocol, use default mappings
 4. If still undetermined -> **Stop and ask the user**