specdacular 0.2.5 → 0.5.1

package/commands/specd/help.md

@@ -20,24 +20,34 @@ Display available specdacular commands and usage guidance.
 
 | Command | Description |
 |---------|-------------|
-| `/specd:map-codebase` | Analyze codebase with parallel agents → produce AI-optimized docs |
+| `/specd:map-codebase` | Analyze codebase with parallel agents -> produce AI-optimized docs |
 
-### Feature Flow
+### Feature Commands
 
 | Command | Description |
 |---------|-------------|
-| `/specd:new-feature [name]` | Initialize a feature, start first discussion |
-| `/specd:discuss-feature [name]` | Continue/deepen feature discussion (can call many times) |
-| `/specd:research-feature [name]` | Research implementation with parallel agents |
-| `/specd:plan-feature [name]` | Create executable task plans for agents |
-| `/specd:discuss-phase [feature] [phase]` | Discuss a phase before execution |
-| `/specd:research-phase [feature] [phase]` | Research patterns for a phase |
-| `/specd:execute-plan [feature] [plan]` | Execute a plan with progress tracking |
+| `/specd:feature:new [name]` | Initialize a feature, start first discussion |
+| `/specd:feature:discuss [name]` | Continue/deepen feature discussion (can call many times) |
+| `/specd:feature:research [name]` | Research implementation with parallel agents |
+| `/specd:feature:plan [name]` | Create roadmap with phase overview |
 
-### Utilities
+### Phase Commands
 
 | Command | Description |
 |---------|-------------|
+| `/specd:phase:prepare [feature] [phase]` | Discuss gray areas + optionally research patterns |
+| `/specd:phase:research [feature] [phase]` | Research patterns for a phase (standalone) |
+| `/specd:phase:plan [feature] [phase]` | Create detailed PLAN.md files for one phase |
+| `/specd:phase:execute [feature] [plan]` | Execute a plan with progress tracking |
+| `/specd:phase:insert [feature] [after] [desc]` | Insert a new phase after an existing one |
+| `/specd:phase:renumber [feature]` | Renumber phases to clean integer sequence |
+
+### Other
+
+| Command | Description |
+|---------|-------------|
+| `/specd:status [--all]` | Show feature status dashboard |
+| `/specd:blueprint [name] [sub]` | Generate visual blueprint (wireframes, diagrams) |
 | `/specd:update` | Update Specdacular to the latest version |
 | `/specd:help` | Show this help |
 
@@ -48,23 +58,27 @@ Display available specdacular commands and usage guidance.
 The feature flow helps you plan features specific enough that an agent can implement without asking questions.
 
 ```
-new-feature → discuss-feature → plan-feature →
-  (discuss-phase? → research-phase? → execute-plan)* per phase
+feature:new -> feature:discuss -> feature:research -> feature:plan (roadmap) ->
+  [for each phase]
+    phase:prepare? -> phase:plan -> phase:execute
+  phase:insert? -> phase:renumber?   <- mid-flight adjustments
 ```
 
 **You control the rhythm:**
-- `new-feature` — Creates structure, asks initial questions, starts first discussion
-- `discuss-feature` — Can be called **many times** to refine understanding
-- `research-feature` — Can be called **many times** to investigate
-- `plan-feature` — When satisfied, creates executable plans for an agent
-- `discuss-phase` — Optional: dive deeper into phase specifics before execution
-- `research-phase` — Optional: research patterns for a specific phase
-- `execute-plan` — Execute plans with progress tracking and deviation logging
+- `feature:new` — Creates structure, asks initial questions, starts first discussion
+- `feature:discuss` — Can be called **many times** to refine understanding
+- `feature:research` — Can be called **many times** to investigate
+- `feature:plan` — Creates roadmap with phases (no detailed plans yet)
+- `phase:prepare` — Discuss gray areas + optionally research (per phase)
+- `phase:plan` — Create detailed PLAN.md files for one phase
+- `phase:execute` — Execute plans with progress tracking
+- `phase:insert` — Insert a new phase mid-flight with decimal numbering (e.g., Phase 3.1)
+- `phase:renumber` — Clean up decimal phases to sequential integers
 
 ### Quick Start
 
 ```
-/specd:new-feature user-dashboard
+/specd:feature:new user-dashboard
 ```
 
 This creates `.specd/features/user-dashboard/` with:
@@ -74,12 +88,20 @@ This creates `.specd/features/user-dashboard/` with:
 - `CHANGELOG.md` — Auto-captured implementation decisions during execution
 - `STATE.md` — Progress tracking
 
-After initialization, refine with discussion and research, then create plans:
+After initialization, refine and plan:
+
+```
+/specd:feature:discuss user-dashboard    # Clarify gray areas
+/specd:feature:research user-dashboard   # Research implementation
+/specd:feature:plan user-dashboard       # Create roadmap
+```
+
+Then for each phase:
 
 ```
-/specd:discuss-feature user-dashboard    # Clarify gray areas
-/specd:research-feature user-dashboard   # Research implementation
-/specd:plan-feature user-dashboard       # Create executable plans
+/specd:phase:prepare user-dashboard 1    # Discuss + optionally research
+/specd:phase:plan user-dashboard 1       # Create detailed plans
+/specd:phase:execute user-dashboard      # Execute with progress tracking
 ```
 
 ---
@@ -104,10 +126,10 @@ Spawns 4 parallel agents to analyze your codebase and creates `.specd/codebase/`
 These docs are **for Claude, not humans**.
 
 Each document answers a question Claude can't get from reading code:
-- MAP.md → "Where is X? What functions exist?"
-- PATTERNS.md → "How do I write code that fits?"
-- STRUCTURE.md → "Where do I put new code?"
-- CONCERNS.md → "What will bite me?"
+- MAP.md -> "Where is X? What functions exist?"
+- PATTERNS.md -> "How do I write code that fits?"
+- STRUCTURE.md -> "Where do I put new code?"
+- CONCERNS.md -> "What will bite me?"
 
 **Principle:** Don't document what Claude can grep. Document tribal knowledge, gotchas, and patterns.
 
@@ -115,7 +137,7 @@ Each document answers a question Claude can't get from reading code:
 
 ## Updating
 
-When an update is available, you'll see `⬆ /specd:update` in your statusline. Run:
+When an update is available, you'll see `update available` in your statusline. Run:
 ```
 /specd:update
 ```

package/commands/specd/{execute-plan.md → phase/execute.md}

@@ -1,5 +1,5 @@
 ---
-name: specd:execute-plan
+name: specd:phase:execute
 description: Execute a feature plan with progress tracking
 argument-hint: "[feature-name] [plan-path]"
 allowed-tools:
@@ -19,10 +19,10 @@ Execute a plan from a feature, tracking progress and logging deviations.
 1. Load context — STATE.md, DECISIONS.md, RESEARCH.md, codebase patterns
 2. Find next plan — First incomplete plan, or accept path as argument
 3. Execute tasks with:
-   - Auto-fix blockers/bugs → log to CHANGELOG.md
-   - Ask about architectural changes → wait for user
+   - Auto-fix blockers/bugs -> log to CHANGELOG.md
+   - Ask about architectural changes -> wait for user
    - Run verification after each task
-   - Stop on verification failure → ask user (retry/skip/stop)
+   - Stop on verification failure -> ask user (retry/skip/stop)
    - Commit after each task
 4. Update progress — STATE.md with completed tasks
 5. Suggest next — Next plan to execute

package/commands/specd/phase/insert.md

@@ -0,0 +1,62 @@
+---
+name: specd:phase:insert
+description: Insert a new phase after an existing one (decimal numbering)
+argument-hint: "[feature-name] [after-phase] [description...]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+---
+
+<objective>
+Insert a new phase after an existing one using decimal numbering (e.g., Phase 03.1 after Phase 03).
+
+**What it does:**
+1. Parse arguments — feature name, target phase number, description
+2. Validate — Feature exists, ROADMAP.md exists, target phase exists
+3. Find next decimal — Scan existing decimals, calculate next (03.1, 03.2, etc.)
+4. Create phase directory — `plans/phase-{NN.M}/`
+5. Update ROADMAP.md — Insert new phase section with `(INSERTED)` marker
+6. Update STATE.md — Add roadmap evolution note, add unchecked phase checkbox
+7. Update config.json — Increment `phases_count`
+8. Show next steps
+</objective>
+
+<execution_context>
+@~/.claude/specdacular/workflows/insert-phase.md
+</execution_context>
+
+<context>
+Arguments: $ARGUMENTS (expects: feature-name after-phase description...)
+
+**Load feature context:**
+@.specd/features/{name}/ROADMAP.md
+@.specd/features/{name}/STATE.md
+@.specd/features/{name}/config.json
+</context>
+
+<process>
+1. **Parse Arguments** — Extract feature-name, after-phase (integer), description
+2. **Validate** — Feature exists, ROADMAP.md exists, target phase exists
+3. **Find Next Decimal** — Scan for existing decimal directories, calculate next
+4. **Create Phase Directory** — `plans/phase-{NN.M}/`
+5. **Update ROADMAP.md** — Insert after target phase with `(INSERTED)` marker
+6. **Update STATE.md** — Add evolution note and unchecked checkbox
+7. **Update config.json** — Increment `phases_count`
+8. **Completion** — Show summary with next steps
+</process>
+
+<success_criteria>
+- [ ] Arguments parsed correctly (feature, phase number, description)
+- [ ] Feature and target phase validated
+- [ ] Decimal number calculated correctly (based on existing decimals)
+- [ ] Phase directory created: `plans/phase-{NN.M}/`
+- [ ] ROADMAP.md updated with new phase entry (includes `(INSERTED)` marker)
+- [ ] Phase inserted in correct position (after target phase, before next phase)
+- [ ] STATE.md updated with roadmap evolution note and unchecked checkbox
+- [ ] config.json `phases_count` incremented
+- [ ] User informed of next steps
+</success_criteria>

package/commands/specd/phase/plan.md

@@ -0,0 +1,73 @@
+---
+name: specd:phase:plan
+description: Create detailed PLAN.md files for one phase
+argument-hint: "[feature-name] [phase-number]"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - AskUserQuestion
+---
+
+<objective>
+Create detailed, executable PLAN.md files for a single phase. Each plan is a prompt for an implementing agent.
+
+**Creates:**
+- `.specd/features/{name}/plans/phase-{NN}/{NN}-PLAN.md` — Executable task plans
+
+**Each PLAN.md is a prompt** for an implementing agent with:
+- Files to create/modify with specific paths
+- Code patterns to follow (from codebase)
+- Verification commands
+- Clear completion criteria
+
+**Prerequisite:** Phase should exist in ROADMAP.md. Phase preparation (`/specd:phase:prepare`) recommended but optional.
+</objective>
+
+<execution_context>
+@~/.claude/specdacular/workflows/plan-phase.md
+</execution_context>
+
+<context>
+Arguments: $ARGUMENTS (expects: feature-name phase-number)
+
+**Load feature context:**
+@.specd/features/{name}/FEATURE.md — Technical requirements
+@.specd/features/{name}/CONTEXT.md — Resolved gray areas
+@.specd/features/{name}/DECISIONS.md — Implementation decisions
+@.specd/features/{name}/RESEARCH.md — Research findings (if exists)
+@.specd/features/{name}/ROADMAP.md — Phase overview
+
+**Load phase context:**
+@.specd/features/{name}/plans/phase-{NN}/CONTEXT.md (if exists, from phase:prepare)
+@.specd/features/{name}/plans/phase-{NN}/RESEARCH.md (if exists, from phase:research)
+
+**Load codebase context:**
+@.specd/codebase/PATTERNS.md — Code patterns to follow
+@.specd/codebase/STRUCTURE.md — Where files go
+@.specd/codebase/MAP.md — System overview
+</context>
+
+<process>
+1. **Validate** — Feature exists, phase exists, phase not already executed
+2. **Load Context** — Read ALL feature, phase, and codebase docs
+3. **Check Existing Plans** — If plans exist, show them and confirm replace
+4. **Break Into Tasks** — 2-3 tasks per plan, sized for agent execution
+5. **Write PLAN Files** — As prompts for implementing agent
+6. **Update ROADMAP** — Mark this phase as planned
+7. **Update STATE.md** — Record planning for this phase
+8. **Commit and Present** — Points to `/specd:phase:execute`
+</process>
+
+<success_criteria>
+- [ ] Feature and phase validated
+- [ ] Phase not already executed
+- [ ] All context loaded (feature, phase, codebase)
+- [ ] Tasks are specific (files, actions, verification)
+- [ ] PLAN.md files are self-contained prompts
+- [ ] ROADMAP.md updated for this phase
+- [ ] Committed to git
+- [ ] User knows next step: `/specd:phase:execute`
+</success_criteria>

package/commands/specd/{discuss-phase.md → phase/prepare.md}

@@ -1,28 +1,33 @@
 ---
-name: specd:discuss-phase
-description: Discuss a specific phase before execution
+name: specd:phase:prepare
+description: Discuss gray areas and optionally research patterns for a phase
 argument-hint: "[feature-name] [phase-number]"
 allowed-tools:
   - Read
   - Write
   - Edit
+  - Bash
   - Glob
   - Grep
+  - Task
   - AskUserQuestion
 ---
 
 <objective>
-Discuss a specific phase before executing it. Enables just-in-time clarification focused on the phase's scope rather than the entire feature.
+Prepare a phase for execution by discussing gray areas and optionally researching implementation patterns. Combines discussion and research into a single flow.
+
+**Discussion always happens.** Research is offered as an optional step at the end.
 
 **Updates:**
 - `.specd/features/{name}/plans/phase-{NN}/CONTEXT.md` — Phase-specific discussion resolutions
 - `.specd/features/{name}/DECISIONS.md` — Accumulates decisions with dates/rationale
+- `.specd/features/{name}/plans/phase-{NN}/RESEARCH.md` — Phase research (if opted in)
 
-**Why phase-level discussion?** Instead of researching/discussing the entire feature upfront, dive deeper into each phase's specifics right before executing it. Smaller context, more focused.
+**Why merged?** Discussing a phase often reveals what needs researching. Single command, natural flow.
 </objective>
 
 <execution_context>
-@~/.claude/specdacular/workflows/discuss-phase.md
+@~/.claude/specdacular/workflows/prepare-phase.md
 </execution_context>
 
 <context>
@@ -46,10 +51,15 @@ Arguments: $ARGUMENTS (expects: feature-name phase-number)
 <process>
 1. **Validate** — Feature exists, phase exists in ROADMAP.md
 2. **Load Context** — Phase details from ROADMAP.md, plans in phase, feature DECISIONS.md
-3. **Identify Gray Areas** — Phase-type-specific concerns
-4. **Probe Gray Areas** — 4 questions per area, then move on
-5. **Record** — Save to `plans/phase-{NN}/CONTEXT.md`, update DECISIONS.md
-6. **Commit**
+3. **Show Phase State** — Present phase overview and existing context
+4. **Identify Gray Areas** — Phase-type-specific concerns
+5. **Probe Gray Areas** — 4 questions per area, then move on
+6. **Record Discussion** — Save to phase CONTEXT.md, update DECISIONS.md
+7. **Offer Research** — "Would you like to research implementation patterns?"
+8. If yes: **Spawn Research Agents** — 3 parallel agents for phase-specific research
+9. If yes: **Synthesize Research** — Combine into phase RESEARCH.md
+10. If yes: **Record Research Decisions** — Technology choices to DECISIONS.md
+11. **Commit and Complete** — Points to `/specd:phase:plan` or `/specd:phase:execute`
 </process>
 
 <success_criteria>
@@ -59,5 +69,7 @@ Arguments: $ARGUMENTS (expects: feature-name phase-number)
 - [ ] User-selected areas discussed
 - [ ] Decisions recorded with date, context, rationale
 - [ ] Phase CONTEXT.md created/updated with resolved questions
+- [ ] Research completed (if user opted in)
 - [ ] Committed to git
+- [ ] User knows next steps: `/specd:phase:plan` or `/specd:phase:execute`
 </success_criteria>

package/commands/specd/phase/renumber.md

@@ -0,0 +1,66 @@
+---
+name: specd:phase:renumber
+description: Renumber phases to clean integer sequence
+argument-hint: "[feature-name]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - AskUserQuestion
+---
+
+<objective>
+Renumber all phases to a clean integer sequence after decimal phases have been inserted.
+
+**What it does:**
+1. Validate — Feature exists with plans and ROADMAP.md
+2. Collect phases — List all phase directories, build old->new mapping
+3. Preview — Show renumbering plan, ask user to confirm
+4. Rename directories — Process highest-to-lowest to avoid collisions
+5. Update plan frontmatter — Fix phase references in plan files
+6. Update ROADMAP.md — Rewrite phase headers, remove `(INSERTED)` markers
+7. Update STATE.md — Rewrite phase references everywhere
+8. Update config.json — Set `phases_count` to new total
+9. Show summary
+</objective>
+
+<execution_context>
+@~/.claude/specdacular/workflows/renumber-phases.md
+</execution_context>
+
+<context>
+Arguments: $ARGUMENTS (expects: feature-name)
+
+**Load feature context:**
+@.specd/features/{name}/ROADMAP.md
+@.specd/features/{name}/STATE.md
+@.specd/features/{name}/config.json
+@.specd/features/{name}/plans/ (all phase directories and plan files)
+</context>
+
+<process>
+1. **Validate** — Feature exists with plans directory and ROADMAP.md
+2. **Collect Phases** — Build sorted list and renumbering mapping
+3. **Preview** — Show mapping, confirm with user
+4. **Rename Directories** — Highest target number down to avoid collisions
+5. **Update Plan Frontmatter** — Fix phase/depends_on in plan YAML
+6. **Update ROADMAP.md** — Rewrite headers, remove `(INSERTED)` markers
+7. **Update STATE.md** — Rewrite all phase references
+8. **Update config.json** — Set `phases_count` to integer count
+9. **Completion** — Show summary of changes
+</process>
+
+<success_criteria>
+- [ ] Feature validated with plans and ROADMAP.md
+- [ ] All phase directories collected and sorted correctly
+- [ ] Renumbering mapping shown to user and confirmed
+- [ ] Directories renamed without collisions (highest-to-lowest)
+- [ ] Plan file frontmatter updated (phase, depends_on)
+- [ ] ROADMAP.md headers and references updated, `(INSERTED)` markers removed
+- [ ] STATE.md phase references updated everywhere
+- [ ] config.json `phases_count` updated
+- [ ] Summary shown to user
+</success_criteria>

package/commands/specd/{research-phase.md → phase/research.md}

@@ -1,5 +1,5 @@
 ---
-name: specd:research-phase
+name: specd:phase:research
 description: Research implementation patterns for a phase
 argument-hint: "[feature-name] [phase-number]"
 allowed-tools:
@@ -19,6 +19,8 @@ Research implementation patterns for a specific phase before executing it. Spawn
 **Output:** `.specd/features/{name}/plans/phase-{NN}/RESEARCH.md` with phase-specific guidance.
 
 **Why phase-level research?** Instead of researching the entire feature upfront, investigate each phase's specifics right before executing it. Smaller scope, more focused, fresher context.
+
+**Note:** This is also available as part of `/specd:phase:prepare`. Use this standalone command when you want to research without discussing first.
 </objective>
 
 <execution_context>

package/commands/specd/status.md

@@ -0,0 +1,20 @@
+---
+name: specd:status
+description: Show feature status dashboard
+argument-hint: "[--all]"
+allowed-tools:
+  - Read
+  - Glob
+  - Bash
+---
+
+<objective>
+Display a dashboard showing all features and their current status, stage, plan progress, and recommended next action.
+
+- By default, hide completed features
+- With `--all` flag, show completed features in a separate section
+</objective>
+
+<execution_context>
+@~/.claude/specdacular/workflows/status.md
+</execution_context>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specdacular",
-  "version": "0.2.5",
+  "version": "0.5.1",
   "description": "Feature planning system for existing codebases. Map, understand, and plan features in large projects.",
   "bin": {
     "specdacular": "bin/install.js"

package/specdacular/agents/feature-researcher.md

@@ -1,6 +1,6 @@
 ---
 name: feature-researcher
-description: Researches implementation patterns, libraries, and pitfalls for features. Spawned by /specd:research-feature.
+description: Researches implementation patterns, libraries, and pitfalls for features. Spawned by /specd:feature:research and /specd:phase:prepare.
 tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch
 ---
 
@@ -8,7 +8,9 @@ tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch
 You are a feature researcher. You investigate how to implement a specific feature well, producing findings that directly inform planning.
 
 You are spawned by:
-- `/specd:research-feature` orchestrator (parallel research)
+- `/specd:feature:research` orchestrator (parallel research)
+- `/specd:phase:prepare` (when user opts into research)
+- `/specd:phase:research` (standalone phase research)
 
 Your job: Answer "What do I need to know to IMPLEMENT this feature well?" Produce structured findings that the synthesizer combines into RESEARCH.md.
 

package/specdacular/templates/blueprint/index.html

@@ -0,0 +1,110 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+  <meta charset="UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate">
+  <title>{feature-name} Blueprint</title>
+  <style>
+{styles}
+  </style>
+</head>
+<body>
+  <div class="blueprint-container">
+    <nav class="blueprint-sidebar">
+      <div class="sidebar-header">
+        <h2>{feature-name}</h2>
+        <span class="subtitle">Blueprint</span>
+      </div>
+      <ul class="nav-tabs">
+        <li><a href="#overview" class="tab-link active" data-tab="overview">Overview</a></li>
+        <li><a href="#decisions" class="tab-link" data-tab="decisions">Decisions</a></li>
+        <li><a href="#context" class="tab-link" data-tab="context">Context</a></li>
+        <li><a href="#plans" class="tab-link" data-tab="plans">Plans</a></li>
+        <li><a href="#wireframes" class="tab-link {wireframes-disabled}" data-tab="wireframes">Wireframes</a></li>
+        <li><a href="#diagrams" class="tab-link {diagrams-disabled}" data-tab="diagrams">Diagrams</a></li>
+      </ul>
+      <div class="sidebar-footer">
+        <span class="generated">Generated: {date}</span>
+      </div>
+    </nav>
+
+    <main class="blueprint-content">
+      <section id="overview" class="tab-content active">
+        <h1>Overview</h1>
+        <div class="overview-description">
+          {feature-description}
+        </div>
+        <div class="overview-stats">
+          <div class="stat">
+            <span class="stat-value">{decisions-count}</span>
+            <span class="stat-label">Decisions</span>
+          </div>
+          <div class="stat">
+            <span class="stat-value">{sessions-count}</span>
+            <span class="stat-label">Discussion Sessions</span>
+          </div>
+          <div class="stat">
+            <span class="stat-value">{plans-count}</span>
+            <span class="stat-label">Plans</span>
+          </div>
+        </div>
+        <div class="overview-timeline">
+          <h2>Activity Timeline</h2>
+          {timeline-content}
+        </div>
+      </section>
+
+      <section id="decisions" class="tab-content">
+        <h1>Decisions</h1>
+        <p class="section-intro">Click any decision to expand details.</p>
+        <div class="phase-tabs">
+          {decisions-phase-tabs}
+        </div>
+        <div class="decisions-list">
+{decisions-content}
+        </div>
+      </section>
+
+      <section id="context" class="tab-content">
+        <h1>Discussion Context</h1>
+        <div class="phase-tabs">
+          {context-phase-tabs}
+        </div>
+        <div class="context-content">
+{context-content}
+        </div>
+      </section>
+
+      <section id="plans" class="tab-content">
+        <h1>Plans</h1>
+        <div class="phase-tabs">
+          {plans-phase-tabs}
+        </div>
+        <div class="plans-content">
+{plans-content}
+        </div>
+      </section>
+
+      <section id="wireframes" class="tab-content">
+        <h1>Wireframes</h1>
+        <div class="wireframes-content">
+{wireframes-content}
+        </div>
+      </section>
+
+      <section id="diagrams" class="tab-content">
+        <h1>Diagrams</h1>
+        <div class="diagrams-content">
+{diagrams-content}
+        </div>
+      </section>
+    </main>
+  </div>
+
+  <script src="https://cdn.jsdelivr.net/npm/mermaid@10.6.1/dist/mermaid.min.js"></script>
+  <script>
+{scripts}
+  </script>
+</body>
+</html>