mddd-cli 4.2.2 → 4.2.3

package/bin/cli.js

@@ -17,7 +17,7 @@ const program = new Command();
 program
   .name('md')
   .description('Manager for co-located specifications for Mermaid Diagram Driven Development (MDDD)')
-  .version('4.2.2');
+  .version('4.2.3');
 
 // ==========================================
 // COMMAND: md init

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mddd-cli",
-  "version": "4.2.2",
+  "version": "4.2.3",
   "description": "Official CLI for modular, co-located, and versioned Mermaid Diagram Driven Development (MDDD).",
   "type": "module",
   "exports": "./bin/cli.js",

package/readme.md

@@ -216,12 +216,12 @@ Visual specifications are not centralized in distant folders. They live in the *
 ```
 src/
 └── home/
-    ├── home.spec.md          # 🌎 Global module map (stateDiagram-v2 connecting nodes)
+    ├── home.spec.md          # 🌎 Global module map
     ├── guest/
-    │   ├── guest.spec.md     # 🔬 Screen flow (graph LR) + Decision Matrix
+    │   ├── guest.spec.md     # 🔬 Screen flow with Decision Matrix
     │   └── guest_page.dart   # 💻 Production code generated by AI
     └── consumer/
-        └── consumer.spec.md  # 🔬 Screen flow (graph LR) + Decision Matrix
+        └── consumer.spec.md  # 🔬 Screen flow with Decision Matrix
 
 ```
 
@@ -476,12 +476,12 @@ As especificações visuais não ficam centralizadas em pastas distantes. Elas v
 ```
 src/
 └── home/
-    ├── home.spec.md          # 🌎 Mapa global do módulo (stateDiagram-v2 conectando nós)
+    ├── home.spec.md          # 🌎 Mapa global do módulo
     ├── guest/
-    │   ├── guest.spec.md     # 🔬 Fluxo de tela (graph LR) + Matriz de Decisão
+    │   ├── guest.spec.md     # 🔬 Fluxo de tela com Matriz de Decisão
     │   └── guest_page.dart   # 💻 Código produtivo gerado pela IA
     └── consumer/
-        └── consumer.spec.md  # 🔬 Fluxo de tela (graph LR) + Matriz de Decisão
+        └── consumer.spec.md  # 🔬 Fluxo de tela com Matriz de Decisão
 
 ```
 

package/src/templates/spec-template.md

@@ -1,8 +1,3 @@
-%% @spec-version 1.0.0
-%% @domain {{domain_name}}
-%% @feature {{feature_name}}
-%% @author {{author_name}}
-
 # {{Feature Title}} — Specification
 
 **SPEC_VERSION:** v1.0.0 — draft
@@ -28,12 +23,9 @@ Describe **what** this spec governs and **why** it exists.
 
 ## 2. Behavioral Flow (Mermaid)
 
-> Pick the diagram type that best fits the topology:
-> `stateDiagram-v2` for lifecycles, `graph TD/LR` for procedural flows,
-> `sequenceDiagram` for multi-actor protocols, `flowchart` for branching logic.
+> Pick the diagram type that best fits the topology using mermaid-diagrams skill.
 
 ```mermaid
-%% @spec-version 1.0.0
 stateDiagram-v2
     [*] --> Idle: initial entry point
 
@@ -104,15 +96,7 @@ When a `HaltWithConflict` is triggered, document the resolution path here:
 
 ---
 
-## 6. Change History
-
-| Version | Date | Author | Change Description | Change Type |
-| :---: | :--- | :--- | :--- | :---: |
-| 1.0.0 | {{YYYY-MM-DD}} | {{author_name}} | Initial spec creation via `md-new` | MAJOR |
-
----
-
-## 7. Audit History
+## 6. Audit History
 
 <details>
 <summary>Click to expand</summary>

package/system_prompt.md

@@ -88,7 +88,7 @@ Brief description of the purpose and scope of this specification.
 
 src/
 └── [domain_name]/
-    ├── [domain_name].spec.md                   # 🌎 Macro Module Domain (stateDiagram-v2)
+    ├── [domain_name].spec.md                   # 🌎 Macro Module Domain
     ├── [feature_name]/
     │   ├── [feature_name].spec.md              # 🔬 Micro Flow Contract + Decision Matrix
     │   └── [feature_name].[extension]          # 💻 Target Production Code File (Any Extension)
@@ -218,7 +218,7 @@ The UNIVERSAL RULE is now integrated into the main processing diagram at the top
 
 **Before ANY action, the system MUST verify that a `.spec.md` file exists for the target domain/feature.** If no spec exists, only `md-new` and `md-audit` skills are allowed to proceed (to create or propose a spec). All other skills (`md-impl`, `md-edit`, etc.) are DENIED without an existing specification.
 
-Diagrams: Always use mmdc -i <path/to/diagram.md> --checkSyntax to validate diagram syntax (Mandatory)
+Diagrams: Always use "npx md validate <path/to/diagram.md>" to validate diagram syntax (Mandatory)
 
 ```mermaid
 %% @spec-version v2.0.0