mddd-cli 4.2.3 → 4.2.4

package/.agents/skills/mermaid-diagrams/README.md

@@ -64,13 +64,6 @@ diagramType
 - **Notes and comments** - Add context and explanations
 - **Alt/loop/opt blocks** - Complex flow control in sequences
 
-### Integration Support
-
-- **GitHub/GitLab** - Automatic rendering in Markdown files
-- **VS Code** - Preview with Markdown Mermaid extension
-- **Notion, Obsidian, Confluence** - Built-in support
-- **Export** - PNG, SVG, PDF via Mermaid Live or CLI
-
 ## Usage Examples
 
 ### Example 1: Document a Domain Model
@@ -233,7 +226,6 @@ For comprehensive syntax and advanced features, see:
 - **[Mermaid Live Editor](https://mermaid.live)** - Interactive editor with instant preview and export
 - **[Official Documentation](https://mermaid.js.org)** - Comprehensive syntax reference
 - **Mermaid CLI** - `npm install -g @mermaid-js/mermaid-cli` for batch exports
-- **VS Code Extension** - "Markdown Preview Mermaid Support" for live preview
 - **GitHub** - Native rendering in all `.md` files
 
 ## Support

package/.agents/skills/mermaid-diagrams/SKILL.md

@@ -184,7 +184,6 @@ flowchart LR
 
 **Native support in:**
 - GitHub/GitLab - Automatically renders in Markdown
-- VS Code - With Markdown Mermaid extension
 - Notion, Obsidian, Confluence - Built-in support
 
 **Export options:**

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.3');
+  .version('4.2.4');
 
 // ==========================================
 // COMMAND: md init

package/package.json

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

package/readme.md

@@ -67,8 +67,6 @@ Unlike traditional specification frameworks that generate dozens of text files a
 
 ## ✅ Mermaid Diagram Preview
 
-To preview Mermaid diagrams directly in your editor during the MDDD workflow, you can use extensions that render ````mermaid```` blocks in Markdown files:
-
 ### Architectural Diagram Example
 
 ```mermaid
@@ -130,26 +128,6 @@ sequenceDiagram
 
 ---
 
-### VS Code and derivated
-
-* **Markdown Preview Mermaid Support** — Adds Mermaid diagram support to the native Markdown preview.
-* **Mermaid Editor** — Visual editor with side-by-side preview and export.
-* **bierner.markdown-mermaid** — Official extension that extends the Markdown preview to render Mermaid.
-
-### JetBrains (IntelliJ, WebStorm, GoLand, etc.)
-
-* Native Mermaid support starting from **2024.1** — Just open the `.spec.md` file and use the built-in Markdown preview.
-
-### Other Editors
-
-* **Neovim/Vim:** Use plugins like `iamcco/markdown-preview.nvim` (with `markdown-preview` configured for Mermaid).
-* **Sublime Text:** `Mermaid` package from Package Control that adds preview and snippets.
-* **Markdown Editors:** Tools like [Typora](https://typora.io), [Obsidian](https://obsidian.md), and [Notion](https://notion.so) already have native Mermaid support — just paste the `.spec.md` file and the diagram will render automatically.
-
-> 💡 **Tip:** The better you can visualize the diagrams, the easier it is to validate business flows before implementation.
-
----
-
 ## 📥 Installation
 
 Since the package is published on NPM, installation is global and simple:
@@ -391,26 +369,6 @@ sequenceDiagram
 
 ---
 
-### VS Code e derivados
-
-* **Markdown Preview Mermaid Support** — Adiciona suporte a diagramas Mermaid no preview nativo do Markdown.
-* **Mermaid Editor** — Editor visual com preview lado a lado e exportação.
-* **bierner.markdown-mermaid** — Extensão oficial que estende o preview de Markdown para renderizar Mermaid.
-
-### JetBrains (IntelliJ, WebStorm, GoLand, etc.)
-
-* Suporte nativo a Mermaid a partir do **2024.1** — Basta abrir o arquivo `.spec.md` e usar o preview de Markdown integrado.
-
-### Outros Editores
-
-* **Neovim/Vim:** Utilize plugins como `iamcco/markdown-preview.nvim` (com `markdown-preview` configurado para Mermaid).
-* **Sublime Text:** Pacote `Mermaid` no Package Control que adiciona preview e snippets.
-* **Markdown Editors:** Ferramentas como [Typora](https://typora.io), [Obsidian](https://obsidian.md) e [Notion](https://notion.so) já possuem suporte nativo a Mermaid — basta colar o arquivo `.spec.md` e o diagrama será renderizado automaticamente.
-
-> 💡 **Dica:** Quanto melhor você conseguir visualizar os diagramas, mais fácil será validar os fluxos de negócio antes da implementação.
-
----
-
 ## 📥 Instalação
 
 Como o pacote está publicado no NPM, a instalação é global e simples:

package/system_prompt.md

@@ -3,9 +3,9 @@
 You are a Mermaid Diagram processing system. Your cognitive processing is guided by visual topologies and truth tables, eliminating text-based specification ambiguity.
 Consume the mermaid-diagrams skill to learn how to produce it.
 
+Spec template path: node_modules/seu-pacote/src/templates/spec-template.md
+
 ```mermaid
-%% @spec-version v2.0.0
-%% @protocol-version 1.0.0
 stateDiagram-v2
     [*] --> CheckSpec: UNIVERSAL RULE — Check specification file
 
@@ -17,14 +17,14 @@ stateDiagram-v2
     state SkillCheck {
         MdNew --> ReadSpecification: Request Allowed.
         MdAudit --> ReadSpecification: Request Allowed.
-        MdEdit --> ReadSpecification: Request Allowed.
         Other --> Denied: Specification file required.
     }
 
     Denied --> ConflictResolution: Explain missing spec
 
     state ReadSpecification {
-        [*] --> ParseMermaidDiagrams: Extract all %% @spec-version diagrams
+        [*] --> CreateSpec: Create file from template
+        CreateSpec --> ParseMermaidDiagrams: Extract all diagrams
         ParseMermaidDiagrams --> ExtractDecisionMatrices: Map topology nodes/edges
         ExtractDecisionMatrices --> ValidatePrimitiveFactors: Check factor columns
         ValidatePrimitiveFactors --> [*]: Spec loaded into context
@@ -50,71 +50,13 @@ stateDiagram-v2
     UpdateDetailsFooter --> [*]
 ```
 
-## 0. Spec File Format (.spec.md)
-
-Every `.spec.md` file MUST follow this structure:
-
-```
-%% @spec-version 1.0.0
-%% @domain [domain_name]
-%% @feature [feature_name] (optional for domain-level specs)
-%% @author [author_name] (optional)
-
-# [Feature/Domain Name] Specification
-
-## Context
-Brief description of the purpose and scope of this specification.
-
-## Flow Diagram
-```mermaid
-[One or more Mermaid diagrams defining the topology/flow]
-```
-
-## Decision Matrix
-| Primitive Factor 1 | Primitive Factor 2 | ... | Proposed Action | Decision |
-| --- | --- | --- | --- | --- |
-| ✅ YES / ❌ NO | ✅ YES / ❌ NO | ... | `ACTION_NAME` | ✅ ALLOW / ❌ DENY |
-
-## Tasks
-- [ ] Task extracted from spec
-
-## Change History
-| Version | Date | Author | Change Description |
-| --- | --- | --- | --- |
-| 1.0.0 | YYYY-MM-DD | ... | Initial spec creation |
-```
-
-## 1. Co-location Architecture Tree
-
-src/
-└── [domain_name]/
-    ├── [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)
-    └── ...                                     # Additional features per domain
-
-> **Note:** `[domain_name]` and `[feature_name]` are placeholders for your actual project names.
-> A single domain can contain multiple features, each in its own subdirectory.
-
-## 2. Parent Interaction Logic
-
-```mermaid
-graph TD
-    A[Create/Change Sub-Feature] --> B[Open Indicated Parent File]
-    B --> C[Locate Bifurcation Node in Parent Mermaid]
-    C --> D[Modify Parent Graph: Point Arrow to New State]
-    D --> E[Child File: Inherit Parent Context in Entry Node]
-    E --> F[Update Parent @spec-version: Increment PATCH]
-```
-
-### 2.1 Reverse Consistency (Parent → Child)
+### 2 Reverse Consistency (Parent → Child)
 
 When a parent domain spec is modified, the following MUST be verified:
 
-1. **Orphan Detection:** Check if any child feature references a state/transition in the parent that no longer exists.
-2. **Cascade Update:** If a parent state is renamed or removed, all child specs referencing it MUST be updated.
-3. **Version Bump:** Parent changes increment MINOR version. Child specs affected by the change increment PATCH version.
+2.1. **Orphan Detection:** Check if any child feature references a state/transition in the parent that no longer exists.
+2.2. **Cascade Update:** If a parent state is renamed or removed, all child specs referencing it MUST be updated.
+2.3. **Version Bump:** Parent changes increment MINOR version. Child specs affected by the change increment PATCH version.
 
 ## 3. Decision Matrix & Primitive Factors
 
@@ -162,23 +104,11 @@ Every `.spec.md` file carries a `%% @spec-version` header. Use **Semantic Versio
 | **MINOR** | Adding: new states/transitions, new factor columns, new features without breaking existing rows. | `1.2.3` → `1.3.0` |
 | **PATCH** | Fixing: typos, clarifying descriptions, reformatting, updating child references. | `1.2.3` → `1.2.4` |
 
-### 4.2 Version Header Format
-
-The `%% @spec-version` comment MUST be the **first line** of the `.spec.md` file:
-
-```markdown
-%% @spec-version 1.0.0
-%% @domain payment
-%% @feature refund-flow
-```
-
-### 4.3 Audit History (Change Log)
+### 4.2 Audit History (Change Log)
 
 Each change MUST append a row to the **Change History** table at the bottom of the `.spec.md` file:
 
 ```
-%% @spec-version 1.1.0
-
 ## Change History
 | Version | Date | Author | Change Description | Change Type |
 | --- | --- | --- | --- | --- |