@jakkrichm/create-nexus-devflow 2.11.0 → 2.12.0

package/template/.claude/skills/report-html/SKILL.md

@@ -30,16 +30,36 @@ When invoked:
    - Archived History: `devflow/history/{features|fixes|rollbacks}/{xxx-slug}.md`
 2. Parse spec sections, checklist steps, QA evidence, and verification logs.
 
-### 2. Render Interactive HTML Dashboard
+### 2. Diagram Pre-Check & Skill Auto-Install (Optional)
+If the spec involves architectural design, system topology, sequence flows, or if the user requests diagrams:
+1. **Inspect Existing Diagrams**:
+   Check `devflow/context/{xxx-slug}/diagrams/`. Any `.svg`, `.html`, or image files will be automatically embedded into the **System & Architecture Diagrams** showcase.
+2. **Auto-Detect & Install Diagram Skills**:
+   If diagrams are requested but not yet generated:
+   - Check if `.agents/skills/archify/` or `.agents/skills/diagram-design/` exists.
+   - If not installed, run CLI installation:
+     ```bash
+     # For technical architecture, dataflows, sequence traces, interactive motion
+     npx create-nexus-devflow skill add archify
+
+     # For editorial, business, quadrant, timeline, or radar diagrams
+     npx create-nexus-devflow skill add diagram-design
+     ```
+3. **Generate Diagram**:
+   Use the installed skill to create the diagram artifact in `devflow/context/{xxx-slug}/diagrams/{name}.html` (or `.svg`).
+4. **Native Mermaid Support**:
+   Any ` ```mermaid ` code block inside the document is automatically rendered visually via the dashboard's built-in theme-aware Mermaid.js engine.
+
+### 3. Render Interactive HTML Dashboard
 Execute the HTML generation engine or script:
 ```bash
 npm run report:html -- {RUNNING_ID}
 ```
 Or transform Markdown into a styled, standalone HTML document:
-- Output: `devflow/reports/{RUNNING_ID}-report.html` (or adjacent `{xxx-slug}.html`)
+- Output: `devflow/context/{xxx-slug}/report.html` (or adjacent `{xxx-slug}.html`)
 
-### 3. Output
+### 4. Output
 Provide:
-- Generated HTML file path: `file:///devflow/reports/{RUNNING_ID}-report.html`
-- Summary of sections rendered (Spec, Plan, Progress, QA Evidence, Release Notes)
+- Generated HTML file path: `file:///devflow/context/{xxx-slug}/report.html`
+- Summary of sections rendered (Spec, Plan, Progress, QA Evidence, Diagrams Showcase, Release Notes)
 - Instructions to open the file in any browser

package/template/.claude/skills/status/SKILL.md

@@ -5,38 +5,32 @@ description: "[devflow] Show where the project stands: build-plan progress, the
 
 # status - where the project stands right now
 
+**Context reuse:** Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.
+
 Where this sits in the workflow:
 
     any time  ->  [status]  ->  reads build-plan + current-feature + git
                   (read-only)   prints a short "you are here"
 
-This skill answers one question: *where am I?* It reads the files that already
-track progress and prints a short orientation. It is the fast way back in after a
-break, a context clear, or a day away. It never changes anything: no edits, no
-commits, no installs, no builds, no branch changes.
-
-Progress in this workflow lives in files, not the chat, so everything this skill
-reports comes from disk and git. That is the point: a fresh session can run
-`/status` and know exactly as much as the last one did.
+`/status` is orientation: where the project stands right now, what's done,
+what's in flight, whether there's drift between plans and reality, and what
+single action makes the most sense next. It is purely read-only: it reads files
+and git, prints a summary, and exits.
 
-For setup problems, missing files, placeholder plans, adapter drift, or questions
-about whether the Blueprint is installed correctly, run `/doctor` instead.
+Use `/doctor` instead when the user wants a full setup-and-health check.
 
 ## Input
 
 None. `/status` takes no argument.
 
-## What it reads
+## What it gathers
 
-Gather these, then summarize. Don't dump file contents; report the distilled
-state.
+Read these, distill them into a few lines, then stop. Do not dump file contents.
 
-1. **Build plan** - `devflow/build-plan.md`. Count checked vs unchecked leaf
-   items. Name the next unchecked leaf, the same target `/feature` would pick,
-   and note if a parent item was split into sub-items (`4a`, `4b`, ...).
-2. **Current work & Spec Queue** - scan `devflow/context/{xxx-slug}/`. Is something in
-   progress? If a feature, fix, or rollback spec is
-   present, report its type, name, running ID, which build steps are checked, and the
+1. **Build plan progress** - `devflow/build-plan.md`. How many features total, how
+   many are checked off (`- [x]`), what's the next unchecked item.
+2. **Current work** - `devflow/context/{xxx-slug}/spec.md` (Pure Multi-Run support). If active, how
+   many build steps total, how many are checked off, what is the description of the
    first unchecked step where `/implement` resumes. If multiple tasks are queued, list the active spec queue.
 3. **Findings** - `devflow/context/{xxx-slug}/findings.md`. Count findings by status and
    report open and fixed counts next to build-plan progress. Call out any P0 or
@@ -54,7 +48,8 @@ state.
 7. **Dashboard activity** - read `devflow/.state/run.json` when it exists.
    Report the command, mode, status, progress, boundary, and safe resume command.
    A missing file simply means no activity has been recorded. Invalid activity
-   state is a warning, not a blocker for the underlying workflow.
+   state is a warning, not a blocker for the underlying workflow; point to
+   `/doctor` to inspect and offer the approved generated-state reset.
 8. **Onboarding check** - Before recommending `/overview`, check whether `AGENTS.md`
    still contains the `<!-- devflow:onboarding-required -->` marker or standard template commands.
    When it does, onboarding is incomplete and `/onboard` is the next action.
@@ -84,6 +79,8 @@ A short, scannable summary, not a wall of text. Aim for something like:
 
 End with a single suggested next action, chosen in this order:
 
+- The project configuration is invalid -> `/doctor`.
+- Dashboard activity is malformed -> `/doctor`.
 - The overview is missing or stale and no feature is in progress -> `/overview`.
 - A spec is in progress with unchecked steps -> `/implement [id]` and name the step.
 - A spec is in progress and all implementation steps are checked -> `/check [id]` if

package/template/AGENTS.md

@@ -40,10 +40,10 @@ Unused adapter families can be removed. Codex, Antigravity, GitHub Copilot, and
 
 ### Universal Invocation & Agent Directives:
 
-1. **Canonical Command Names & AI Provider Invocation**: Each workflow stage and companion tool has exactly **one Canonical Name** (e.g. `feature`, `fix`, `implement`, `check`, `complete`, `continuous`, `discovery`, `idea`, `grill`, `brainstorm`, `devflow`, `doctor`, `overview`, `debug`, `onboard`, `adopt`, `try`, `rollback`, `ci`, `test`, `setup-tests`, `browser-tests`, `autopilot`, `prototype`, `report-html`, `brief`, `audit`, `release`, `convert-any-to-md`, `publish-devflow`). The way you invoke commands depends on your AI Provider / Tool:
-   - **Canonical Name (Plain text)**: Directly invoke or prompt the command by its standard name (e.g., `feature`, `implement`, `continuous`, `devflow`, `discovery`).
-   - **Slash Prefix (`/`)**: For tools supporting slash commands (Claude Code, Google Antigravity, Gemini CLI), e.g., `/feature`, `/fix`, `/implement`, `/continuous`, `/devflow`, `/discovery`.
-   - **Dollar Prefix (`$`)**: For OpenAI Codex CLI or skill-invocation tools, e.g., `$feature`, `$fix`, `$continuous`, `$devflow`, `$discovery`.
+1. **Canonical Command Names & AI Provider Invocation**: Each workflow stage and companion tool has exactly **one Canonical Name** (e.g. `feature`, `fix`, `implement`, `check`, `complete`, `continuous`, `analyze`, `discovery`, `idea`, `grill`, `brainstorm`, `bughunter`, `devflow`, `doctor`, `overview`, `debug`, `onboard`, `adopt`, `try`, `rollback`, `ci`, `test`, `setup-tests`, `browser-tests`, `autopilot`, `prototype`, `report-html`, `brief`, `audit`, `release`, `convert-any-to-md`, `publish-devflow`). The way you invoke commands depends on your AI Provider / Tool:
+   - **Canonical Name (Plain text)**: Directly invoke or prompt the command by its standard name (e.g., `feature`, `implement`, `continuous`, `devflow`, `discovery`, `analyze`).
+   - **Slash Prefix (`/`)**: For tools supporting slash commands (Claude Code, Google Antigravity, Gemini CLI), e.g., `/feature`, `/fix`, `/implement`, `/continuous`, `/devflow`, `/discovery`, `/analyze`.
+   - **Dollar Prefix (`$`)**: For OpenAI Codex CLI or skill-invocation tools, e.g., `$feature`, `$fix`, `$continuous`, `$devflow`, `$discovery`, `$analyze`.
 2. **OpenAI Codex & Non-Native CLI Tools**: In environments without automatic background skill discovery (such as OpenAI Codex CLI, Aider, or generic terminals), **you MUST use your file reading tool to inspect `.agents/skills/<skill>/SKILL.md` before executing the stage** to strictly follow its schema, artifact contract, and quality gates.
 3. **Google Antigravity & Claude Code**: Native skill engines automatically discover and surface `.agents/skills/` and `.claude/skills/`.
 4. **State-Aware Inspection**: When unsure what to do next, invoke `devflow` to automatically inspect active task directories in `devflow/context/{xxx-slug}/`, `devflow/discoveries/`, and `devflow/ideas.md`.
@@ -71,8 +71,9 @@ All development tasks execute through the 4-step progressive lifecycle:
 
 ---
 
-## 🔮 Pre-Flight Discovery & Architectural Alignment (Companions)
+## 🔮 Pre-Flight Discovery, SA & Architectural Alignment (Companions)
 
+- `analyze`: Unified SA requirement ingestion, multi-format doc parsing (PDF, Word, Excel, images, text), codebase impact scan (`devflow/inbox/`, `devflow/analysis/`).
 - `discovery`: Unified pre-delivery discovery & exploration (`devflow/discoveries/{DISC-ID}/discovery.md`).
 - `idea`: Quick idea capture and AI feasibility scoring (`devflow/ideas.md`).
 - `grill` (or `align`): Socratic alignment, domain modeling, and ADR recording (`devflow/decisions/`).
@@ -84,13 +85,20 @@ All development tasks execute through the 4-step progressive lifecycle:
 
 The dashboard and status reporting can show the active or most recent substantial DevFlow command from `devflow/.state/run.json`. This file is generated local state, ignored by Git, and never part of a feature commit.
 
-<<<<<<< HEAD
-Commands with meaningful progress or a durable handoff should write it when the state directory exists: `onboard`, `adopt`, `discovery`, `overview`, `feature`, `fix`, `rollback`, `implement`, `debug`, `check`, `audit`, `tests`, `browser-tests`, `ci`, `prototype`, `autopilot`, `continuous`, `complete`, and `release`. Short read-only orientation commands such as `brief`, `try`, `status`, and `doctor` do not need activity state.
-=======
-Commands with meaningful progress or a durable handoff should write it when the state directory exists: `onboard`, `adopt`, `discovery`, `overview`, `feature`, `fix`, `rollback`, `implement`, `debug`, `check`, `audit`, `setup-tests`, `ci`, `prototype`, `autopilot`, `continuous`, `complete`, and `release`. Short read-only orientation commands such as `brief`, `try`, `status`, and `doctor` do not need activity state.
->>>>>>> feature/064-bughunter-master-skill-and-sync-engine
+Commands with meaningful progress or a durable handoff should write it when the state directory exists: `onboard`, `adopt`, `analyze`, `discovery`, `overview`, `feature`, `fix`, `rollback`, `implement`, `debug`, `check`, `audit`, `bughunter`, `setup-tests`, `browser-tests`, `test`, `ci`, `prototype`, `autopilot`, `continuous`, `complete`, and `release`. Short read-only orientation commands such as `brief`, `try`, `status`, and `doctor` do not need activity state. Doctor's optional approved reset removes malformed activity instead of recording another run.
 
-Writing the initial activity record is the first action of a tracked command, before project inspection, preflight, or other tool calls. This one generated state write does not authorize product changes or bypass any safety check. Set status to `running`, use the command name and a truthful initial summary, then replace the record at meaningful milestones. On a preflight stop or another blocker, set it to `blocked` with the exact recovery command. Leave the final state in place for the next session; the next tracked command replaces it. Use this schema:
+Writing the initial activity record is the first action of a tracked command, before project inspection, preflight, or other tool calls. This one generated state write does not authorize product changes or bypass any safety check.
+
+Never create or edit `run.json` directly. From the project root, use the first helper that exists:
+
+```text
+node .agents/skills/doctor/scripts/run-state.mjs <action> <options>
+node .claude/skills/doctor/scripts/run-state.mjs <action> <options>
+```
+
+Start with `start --command <skill> --summary <truthful-summary> --boundary <boundary>`. Use `update` at meaningful milestones or for a blocker, with `--status blocked` and `--resume <exact-command>` when recovery is needed. End with `finish --status ready|completed --summary <truthful-summary>`. The helper validates every field before atomically replacing the generated file. If it is missing or fails, report the activity warning and continue the workflow without writing a manual fallback.
+
+The helper writes this schema:
 
 ```json
 {

package/template/devflow/build-plan.md

@@ -172,4 +172,35 @@
   - *Dependencies*: Feature 20, DISC-20260902-001
   - *Scope*: ขยายชุดทดสอบ Evals Routing ให้ครอบคลุมทุกสคิล (`browser-tests.json`, `continuous.json`, `bughunter.json`, `publish-devflow.json`), นำเข้าและปรับใช้ Live-Agent E2E Test Harness (`scripts/e2e/`), สคริปต์จำลองติดตั้ง Sandbox Scaffolding (`scripts/scaffold-sandbox.ts`), สคริปต์ตรวจจับ Upstream Drift (`scripts/check-upstream-drift.ts`), และเอกสารวิเคราะห์ Token Efficiency (`benchmarks/context-efficiency.md`)
 
+---
+
+## 🎨 Phase 22: Visual Dashboard & Diagram Integration
+
+- [x] **22. Standalone HTML Report Diagram Integration (`DISC-20260902-003`, `069-report-html-diagram-integration`)** `[Size: S]`
+  - *Dependencies*: Feature 17 (`055`), DISC-20260902-003
+  - *Scope*: ปรับปรุง `md2html-report.mjs` รองรับการเรนเดอร์ native Mermaid block (`.mermaid`), เพิ่มการสแกนและ embed ไฟล์ไดอะแกรมจาก `devflow/context/{xxx-slug}/diagrams/` (`.svg` และ `.html`), อัปเดต `report-html` skill ให้ตรวจจับและ auto-install `archify` / `diagram-design` ผ่าน `nexus-devflow skill add` และเขียนชุดทดสอบครอบคลุม
+
+---
+
+## 🧹 Phase 23: Reference Artifacts Housekeeping
+
+- [x] **23. Prune Studio Reference Artifacts (`069-prune-studio-reference-artifacts`)** `[Size: S]`
+  - *Dependencies*: None
+  - *Scope*: ลบไฟล์ Static HTML Snapshot ตกค้าง `devflow/reference/studio.html` และสคริปต์ `scripts/export-studio.ts` โดยยังคงรักษา Webview Studio Engine (`webview-studio.ts`), MCP tool (`devflow_get_studio_html`), CLI Command (`nexus-devflow studio`) และชุดทดสอบทั้งหมดให้ทำงานได้สมบูรณ์ 100%
+
+---
+
+## 📐 Phase 24: Role-Based Profiles & SA Command Suite Engine
+
+- [x] **24. Role-Based Profiles & SA Analyze Command Engine (`DISC-20260903-001`, `070-role-based-profile-and-sa-analyze-engine`)** `[Size: M]`
+  - *Dependencies*: None
+  - *Scope*: เพิ่มตัวเลือก `--role [sa|dev|full]` ใน CLI Installer (`create-nexus-devflow`), ระบบจำแนกชุด Skill Profiles ใน `skill-manager.ts`, โฟลเดอร์ Template สำหรับ SA (`devflow/inbox/`, `devflow/analysis/`, `devflow/blueprints/`), พัฒนาสคิล `/analyze` สำหรับสกัดเอกสารหลายรูปแบบ (PDF, Word, Excel, รูปภาพ, ข้อความ) และวิเคราะห์ Codebase Impact พร้อมชุดทดสอบ Automated Tests
+
+---
+
+## 🔄 Phase 25: Upstream AI Blueprint v1.5.0 – v1.5.1 Synchronization
+
+- [x] **25. Sync Upstream v1.5.0 & v1.5.1 (Hardened Run-State Engine & On-Demand Context Loading) (`DISC-20260903-001`, `070-sync-upstream-ai-blueprint-v150-v151`)** `[Size: M]`
+  - *Dependencies*: Feature 20, Feature 21, DISC-20260903-001
+  - *Scope*: พอร์ตและปรับแต่ง Hardened Dashboard Activity State Helper (`.agents/skills/doctor/scripts/run-state.mjs` และ `.claude/`), บังคับใช้ Zero-Manual Writes กับ `devflow/.state/run.json`, ปรับใช้ On-Demand Context Loading Protocol พร้อมแยก Reference Templates ย่อย (`reference/`), เพิ่ม Unit Tests `run-state-helper.test.ts`, อัปเดต `scripts/validate-framework.ts`, `AGENTS.md`, `CLAUDE.md` และยืนยันการผ่าน 100%