@jakkrichm/create-nexus-devflow 2.9.0 → 2.9.4

package/template/.agents/skills/feature/SKILL.md

@@ -6,6 +6,10 @@ argument-hint: "[{number, name, DISC-id, or IDEA-id}]"
 
 # feature - turn a build-plan feature into a buildable spec
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     project-overview.md  +  build-plan.md  ->  [this skill]  ->  build

package/template/.agents/skills/fix/SKILL.md

@@ -6,6 +6,10 @@ argument-hint: "[{title or issue-description}]"
 
 # fix - document an ad-hoc fix, then build it like anything else
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     /fix  ->  /implement  ->  /complete  ->  back to your features

package/template/.agents/skills/implement/SKILL.md

@@ -6,6 +6,10 @@ argument-hint: "[{run-id, number, or name}]"
 
 # implement - build the target spec, one reviewed step at a time
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     /feature, /fix, or /rollback  ->  [implement]  ->  /complete  ->  next

package/template/.agents/skills/onboard/SKILL.md

@@ -5,6 +5,10 @@ description: "[devflow] Set up the Blueprint after overlaying it onto a freshly
 
 # onboard - finish the Blueprint overlay setup
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     scaffold app  ->  overlay Blueprint  ->  [onboard]  ->  project-plan + build-plan  ->  /overview

package/template/.agents/skills/overview/SKILL.md

@@ -5,6 +5,10 @@ description: "[devflow] Distill user-owned planning docs into `devflow/context/p
 
 # overview - dynamic project overview compiler
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 ## Position in workflow
 
 ```text

package/template/.agents/skills/prototype/SKILL.md

@@ -5,6 +5,10 @@ description: "[devflow] Interactively prototype the look of a project. Asks abou
 
 # prototype - lock the look before you build
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     plan  ->  /overview  ->  [prototype]  ->  /feature  ->  build

package/template/.agents/skills/release/SKILL.md

@@ -5,6 +5,10 @@ description: "[devflow] Prepare a Blueprint project for deployment to Render or
 
 # release - deployment readiness for Render and Vercel
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     /complete  ->  [release]  ->  deploy with explicit approval

package/template/.agents/skills/rollback/SKILL.md

@@ -5,6 +5,10 @@ description: "[devflow] Plan a safe reversal of a completed Blueprint feature us
 
 # rollback - safely reverse a completed feature
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     completed feature + git history  ->  [rollback]  ->  /implement  ->  /check  ->  /complete
@@ -57,10 +61,16 @@ Use the archive path to locate the commit that added it:
     git log --diff-filter=A --format="%H %s" HEAD -- <archive-path>
 
 Use the newest matching commit reachable from the current branch. Confirm the
-archive was added by that commit, the commit has exactly one parent, and its
-subject and diff are consistent with the requested feature. A merge commit needs
-mainline selection, so stop rather than guessing. If the archive was never
-committed, explain that git cannot reconstruct a safe rollback from it.
+archive was added by that commit and its subject and diff are consistent with the
+requested feature. If the target is a merge commit, stop before Step 2 and before
+writing or changing `devflow/context/{xxx-slug}/spec.md`. Do not record a
+target parent or choose a mainline. Publish `blocked` to
+`devflow/.state/run.json`, explain that DevFlow cannot safely infer which
+merge parent represents the pre-feature state, and include the exact `/rollback`
+command the user can rerun after choosing a safe remediation or mainline
+strategy. `/implement` retains its merge-target stop as defense in depth. If the
+archive was never committed, explain that git cannot reconstruct a safe rollback
+from it.
 
 ## Step 2 - separate product changes from Blueprint history
 
@@ -108,7 +118,8 @@ remediation or explicitly plan the dependent rollbacks.
 Allocate sequential ID (`xxx-slug`) and create `devflow/context/{xxx-slug}/`. Write `devflow/context/{xxx-slug}/spec.md` using
 `reference/rollback-spec-template.md`. Also initialize `stage.md` and `findings.md` in that folder. Fill in:
 
-- target feature, archive, exact commit, and parent commit
+- target feature and archive
+- target commit and parent commit as full 40-character SHA values
 - user's reason
 - product paths introduced or changed by the target
 - protected workflow paths
@@ -142,6 +153,8 @@ spec, then run `/implement` to create the rollback branch and apply it.
 - Preserve history. Never delete or rewrite the original feature archive.
 - Plan only. This skill writes the rollback spec and nothing else.
 - One completed feature per rollback.
+- Record both the target commit and its parent as full 40-character SHA values.
+  Each value must resolve to the recorded commit in the current repository.
 - Never use `git reset --hard`, force-push, history rewriting, or broad file
   restoration.
 - Never infer permission to cascade into later features or destroy stored data.

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

@@ -51,6 +51,13 @@ state.
 6. **Progress drift** - flag active task on `main`, a spec in progress but no
    matching `feature/{xxx-slug}`, `fix/{xxx-slug}`, or `rollback/{xxx-slug}` branch, all spec steps checked but
    not completed, or disagreement between `build-plan.md` and active specs.
+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.
+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.
 
 ## Output
 

package/template/.agents/skills/tests/SKILL.md

@@ -5,6 +5,10 @@ description: "[devflow] Add or normalize unit testing for a Blueprint project. D
 
 # tests - add unit testing to the project
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     any time  ->  [tests]  ->  test command in AGENTS.md  ->  /feature + /implement use it

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

@@ -5,6 +5,10 @@ description: "[devflow] Bring the blueprint into an existing (brownfield) codeba
 
 # adopt - bootstrap the blueprint from an existing codebase
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     existing codebase  ->  [adopt]  ->  project-plan + build-plan + coding-standards  ->  /overview  ->  normal loop

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

@@ -5,6 +5,10 @@ description: "[devflow] Read-only code audit for a Blueprint project, except for
 
 # audit - review code quality against the project standards
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     /implement or /autopilot  ->  [audit]  ->  fixes or /complete

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

@@ -5,6 +5,10 @@ description: "[devflow] Optional explicit Blueprint mode for one bounded spec/bu
 
 # autopilot - optional Blueprint loop
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     /status  ->  [autopilot]  ->  review packet  ->  /complete

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

@@ -6,6 +6,10 @@ argument-hint: "[{run-id, number, or name}]"
 
 # check - Dual-Axis Independent Verification Engine
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     /implement  ->  [check]  ->  /complete

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

@@ -5,6 +5,10 @@ description: "[devflow] Set up or normalize automatic GitHub checks for a Bluepr
 
 # ci - set up automatic GitHub checks
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     /onboard or /adopt  ->  [ci]  ->  Verify locally  ->  GitHub runs Verify

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

@@ -6,6 +6,10 @@ argument-hint: "[{run-id, number, or name}]"
 
 # complete - log the finished work, make the work commit, and deliver
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     /feature, /fix, or /rollback  ->  /implement  ->  [complete]  ->  next
@@ -70,7 +74,9 @@ and records the exact target feature, archive, commit, and parent.
 **Archive resolved findings.** If `devflow/context/{xxx-slug}/findings.md` holds any
 findings, append a `## Findings` section to the archive file just written with
 every `closed`, `accepted`, or `invalid` entry at its final status (`accepted`
-entries keep their recorded reason).
+entries keep their recorded reason). Do not archive or remove a `fixed` finding
+at any severity; repaired findings must remain in the ledger until an `/audit`
+re-review closes them.
 
 **Clean up run workspace.** Delete the task directory `devflow/context/{xxx-slug}/`. In Pure Multi-Run architecture, completed work leaves zero residual stubs in `devflow/context/`.
 

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

@@ -6,6 +6,10 @@ argument-hint: "[{resume, max-features, or start-feature}]"
 
 # continuous - Complete the Build Plan One Local Feature at a Time
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
 ```text

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

@@ -5,6 +5,10 @@ description: "[devflow] Diagnose a failing test, broken build, crash, error, reg
 
 # debug - 6-Phase Scientific Debugging Protocol
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     reported failure  ->  [debug]  ->  /fix or /implement

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

@@ -8,6 +8,10 @@ argument-hint: "[{title, request, IDEA-xxx, or discovery-id}]"
 
 $ARGUMENTS
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 `/discovery` is the central discovery entry point in Nexus-DevFlow. It operates in two adaptive modes based on input scope:
 1. **🗺️ Macro Project Discovery**: Develops high-level product and build roadmap plans (`devflow/project-plan.md` & `devflow/build-plan.md`) through an adaptive conversation before `/overview`.
 2. **🔍 Micro Feature Exploration (Pre-Flight)**: Explores a specific feature, request, or idea before committing to delivery, routes through supporting lenses, and finishes with a visible `Proceed`, `Defer`, or `Reject` decision before `/feature` or `/fix`.
@@ -72,10 +76,10 @@ devflow/discoveries/{DISCOVERY_ID}-{slug}/discovery.md
 5. **Socratic Grilling & Domain Alignment Lens (`grill`)**:
    - Codebase-grounded interactive inquiry to clarify entity boundaries, data flows, and edge cases.
    - Record agreed terminology in `devflow/context/glossary.md` and major architecture decisions in `devflow/decisions/ADR-xxx-{slug}.md`.
-6. **🎨 Visual Architecture & Diagram Design Lens (`diagram-design`)**:
-   - When exploring system topologies, legacy IT modernizations, sequence flows, data platform pipelines, or user journeys, check if the third-party skill `diagram-design` is installed in `.agents/skills/diagram-design/`.
-   - If available: Read `.agents/skills/diagram-design/SKILL.md` and load the matching type reference (e.g. `references/type-architecture.md`, `references/type-data-flow.md`, `references/type-sequence.md`, `references/type-journey.md`).
-   - Strictly follow the genuine design rules: editorial palette, style guide gate, target density 4/10, and self-contained HTML/SVG output.
+6. **🎨 Visual Architecture & Diagram Design Lens (`archify` / `diagram-design`)**:
+   - When exploring system topologies, legacy IT modernizations, sequence flows, data platform pipelines, state machines, or user journeys, check for `archify` or `diagram-design` in `.claude/skills/`.
+   - **For interactive system architecture, dataflows, state transitions, and sequence traces**: Use `archify` (`.claude/skills/archify/SKILL.md`) to compile validated interactive HTML artifacts with dark/light themes, motion, and route probes.
+   - **For editorial, business, quadrant, or broad diagram types**: Use `diagram-design` (`.claude/skills/diagram-design/SKILL.md`).
    - Save diagram artifacts to `devflow/discoveries/{DISCOVERY_ID}-{slug}/diagrams/{name}.html` and reference them directly in `discovery.md`.
 
 ### Decision & Approval Gate:

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

@@ -6,6 +6,10 @@ argument-hint: "[{number, name, DISC-id, or IDEA-id}]"
 
 # feature - turn a build-plan feature into a buildable spec
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     project-overview.md  +  build-plan.md  ->  [this skill]  ->  build

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

@@ -6,6 +6,10 @@ argument-hint: "[{title or issue-description}]"
 
 # fix - document an ad-hoc fix, then build it like anything else
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     /fix  ->  /implement  ->  /complete  ->  back to your features

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

@@ -6,6 +6,10 @@ argument-hint: "[{run-id, number, or name}]"
 
 # implement - build the target spec, one reviewed step at a time
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     /feature, /fix, or /rollback  ->  [implement]  ->  /complete  ->  next

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

@@ -5,6 +5,10 @@ description: "[devflow] Set up the Blueprint after overlaying it onto a freshly
 
 # onboard - finish the Blueprint overlay setup
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     scaffold app  ->  overlay Blueprint  ->  [onboard]  ->  project-plan + build-plan  ->  /overview

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

@@ -5,6 +5,10 @@ description: "[devflow] Distill user-owned planning docs into `devflow/context/p
 
 # overview - dynamic project overview compiler
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 ## Position in workflow
 
 ```text

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

@@ -5,6 +5,10 @@ description: "[devflow] Interactively prototype the look of a project. Asks abou
 
 # prototype - lock the look before you build
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     plan  ->  /overview  ->  [prototype]  ->  /feature  ->  build

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

@@ -5,6 +5,10 @@ description: "[devflow] Prepare a Blueprint project for deployment to Render or
 
 # release - deployment readiness for Render and Vercel
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     /complete  ->  [release]  ->  deploy with explicit approval

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

@@ -5,6 +5,10 @@ description: "[devflow] Plan a safe reversal of a completed Blueprint feature us
 
 # rollback - safely reverse a completed feature
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     completed feature + git history  ->  [rollback]  ->  /implement  ->  /check  ->  /complete
@@ -57,10 +61,16 @@ Use the archive path to locate the commit that added it:
     git log --diff-filter=A --format="%H %s" HEAD -- <archive-path>
 
 Use the newest matching commit reachable from the current branch. Confirm the
-archive was added by that commit, the commit has exactly one parent, and its
-subject and diff are consistent with the requested feature. A merge commit needs
-mainline selection, so stop rather than guessing. If the archive was never
-committed, explain that git cannot reconstruct a safe rollback from it.
+archive was added by that commit and its subject and diff are consistent with the
+requested feature. If the target is a merge commit, stop before Step 2 and before
+writing or changing `devflow/context/{xxx-slug}/spec.md`. Do not record a
+target parent or choose a mainline. Publish `blocked` to
+`devflow/.state/run.json`, explain that DevFlow cannot safely infer which
+merge parent represents the pre-feature state, and include the exact `/rollback`
+command the user can rerun after choosing a safe remediation or mainline
+strategy. `/implement` retains its merge-target stop as defense in depth. If the
+archive was never committed, explain that git cannot reconstruct a safe rollback
+from it.
 
 ## Step 2 - separate product changes from Blueprint history
 
@@ -108,7 +118,8 @@ remediation or explicitly plan the dependent rollbacks.
 Allocate sequential ID (`xxx-slug`) and create `devflow/context/{xxx-slug}/`. Write `devflow/context/{xxx-slug}/spec.md` using
 `reference/rollback-spec-template.md`. Also initialize `stage.md` and `findings.md` in that folder. Fill in:
 
-- target feature, archive, exact commit, and parent commit
+- target feature and archive
+- target commit and parent commit as full 40-character SHA values
 - user's reason
 - product paths introduced or changed by the target
 - protected workflow paths
@@ -142,6 +153,8 @@ spec, then run `/implement` to create the rollback branch and apply it.
 - Preserve history. Never delete or rewrite the original feature archive.
 - Plan only. This skill writes the rollback spec and nothing else.
 - One completed feature per rollback.
+- Record both the target commit and its parent as full 40-character SHA values.
+  Each value must resolve to the recorded commit in the current repository.
 - Never use `git reset --hard`, force-push, history rewriting, or broad file
   restoration.
 - Never infer permission to cascade into later features or destroy stored data.

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

@@ -51,6 +51,13 @@ state.
 6. **Progress drift** - flag active task on `main`, a spec in progress but no
    matching `feature/{xxx-slug}`, `fix/{xxx-slug}`, or `rollback/{xxx-slug}` branch, all spec steps checked but
    not completed, or disagreement between `build-plan.md` and active specs.
+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.
+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.
 
 ## Output
 

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

@@ -5,6 +5,10 @@ description: "[devflow] Add or normalize unit testing for a Blueprint project. D
 
 # tests - add unit testing to the project
 
+**First action:** Before project inspection, preflight, or any other tool call,
+publish `running` to `devflow/.state/run.json` using the dashboard activity
+contract in `AGENTS.md`.
+
 Where this sits in the workflow:
 
     any time  ->  [tests]  ->  test command in AGENTS.md  ->  /feature + /implement use it

package/template/AGENTS.md

@@ -78,12 +78,31 @@ All development tasks execute through the 4-step progressive lifecycle:
 
 ---
 
-## 🌐 Standalone HTML Reporting Policy
+## 📊 Dashboard Activity State Contract
+
+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.
+
+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`, `ci`, `prototype`, `autopilot`, `continuous`, `complete`, and `release`. Short read-only orientation commands such as `brief`, `try`, `status`, and `doctor` do not need activity state.
+
+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:
+
+```json
+{
+  "schemaVersion": 1,
+  "command": "continuous",
+  "status": "running",
+  "summary": "Completing the remaining build plan",
+  "detail": "Implementing feature 3.",
+  "boundary": "local-only",
+  "startedAt": "<ISO-8601 timestamp>",
+  "updatedAt": "<ISO-8601 timestamp>",
+  "resumeCommand": "/continuous resume",
+  "progress": { "current": 2, "total": 5, "label": "features" },
+  "feature": { "id": "3", "title": "Export reports" }
+}
+```
 
-> [!IMPORTANT]
-> **No Auto-Generated HTML**: Mainline flows (`/complete`) strictly output Markdown only.
-> When an interactive web dashboard is desired for presentation or sharing, invoke the standalone companion command:
-> `/report:html` (or `npm run report:html -- {ID}`).
+`status` must be `running`, `blocked`, `ready`, or `completed`. Use `ready` when the command reached its intended review handoff, such as Autopilot waiting for review before `/complete`. Use `blocked` with the exact recovery command when work can resume. `boundary` must be `read-only`, `reviewed`, or `local-only`. The progress, feature, detail, boundary, and resume fields are optional. Never put secrets, raw logs, prompts, or user content in this file. Activity tracking must not change a command's approval boundaries or turn a reporting failure into a workflow failure.
 
 ---
 

package/template/devflow/build-plan.md

@@ -116,4 +116,28 @@
   - *Dependencies*: Feature 11, Feature 12, Feature 13
   - *Scope*: ยกเลิกไฟล์ Single Living Spec ที่ Root (`current-feature.md`, `current-stage.md`, `findings.md`) อย่างสมบูรณ์ ปรับโครงสร้างสู่ Task-Isolated Subdirectories 100% (`devflow/context/{xxx-slug}/`), อัปเกรด Agent Directives, Core Context Resolver, Scaffolding Templates และ Workflow Skills ทั้งหมด
 
+---
+
+## 🔄 Phase 15: Upstream AI Blueprint v1.0.0 / v1.0.1 Synchronization
+
+- [x] **15. Sync Upstream v1.0.0 (Activity Contract, Rollback & Complete Safeguards, Local Linking)** `[Size: M]`
+  - *Dependencies*: Feature 14, DISC-20260828-001-sync-upstream-ai-blueprint-v100
+  - *Scope*: ผสาน Activity State Contract (`devflow/.state/run.json`) และ Live Dashboard Activity, เสริม Rollback 40-char SHA & Merge Commit Protection, Complete Fixed Finding Persistence, คำสั่ง `npm run link:local` / `unlink:local` พร้อม `findPackageRoot()`, Onboarding Markers และ Windows Smoke/Path Fixes
+
+---
+
+## 🖥️ Phase 16: Multi-Task Dashboard & Live Kanban Studio UI
+
+- [x] **16. Multi-Task Dashboard & Live Kanban Studio UI (`DISC-20260828-002`)** `[Size: M]`
+  - *Dependencies*: Feature 14, Feature 15
+  - *Scope*: ปรับปรุง Full Web Dashboard (`dashboard-page.ts`) และ Live Kanban Studio (`webview-studio.ts`) ให้อ่านและวนลูปแสดงผลรายการ Task ทั้งหมดใน `status.activeRuns` จาก `devflow/context/{xxx-slug}/` พร้อม Task Progress Bar, Branch Pill, Findings Indicator และปุ่ม Quick Actions แบบเจาะจง Target Run ID
+
+---
+
+## 🔌 Phase 17: Unified Third-Party Skills Installer & Updater
+
+- [x] **17. Unified Third-Party Skills Installation & Update Command (`DISC-20260831-001`, `055-unified-third-party-skills-installer`)** `[Size: S]`
+  - *Dependencies*: None
+  - *Scope*: เพิ่มฟังก์ชัน `installRecommendedSkills` และ `updateRecommendedSkills` ใน `skill-manager.ts`, รองรับสวิตช์ `--recommended` ในคำสั่ง `nexus-devflow skill add` และ `nexus-devflow skill update`, พร้อมอัปเดตเอกสาร `README.md`, `README.th.md` และ Automated Tests
+
 

package/template/devflow/context/ai-interaction.md

@@ -171,13 +171,13 @@ Nexus-DevFlow natively supports extending workflow capabilities with **Third-Par
 - Installed third-party skills maintain their exact original directory structure, references, assets, scripts, and `SKILL.md`.
 
 ### 🎯 2. Cross-Command Delegation & Genuine Execution
-- **Verbatim & Original Prompt Fidelity**: When a DevFlow stage requires specialized domain expertise (e.g., editorial diagramming, domain modeling, cloud provisioning, UI benchmarking), the AI agent must read the third-party skill's `SKILL.md` (e.g. `.agents/skills/diagram-design/SKILL.md`) and strictly follow its original instructions, philosophy, style guide gates, and complexity constraints.
+- **Verbatim & Original Prompt Fidelity**: When a DevFlow stage requires specialized domain expertise (e.g., editorial diagramming, system mapping, domain modeling, cloud provisioning, UI benchmarking), the AI agent must read the third-party skill's `SKILL.md` (e.g. `.agents/skills/archify/SKILL.md` or `.agents/skills/diagram-design/SKILL.md`) and strictly follow its original instructions, philosophy, style guide gates, and complexity constraints.
 - **Workflow Command Integration Map**:
-  - **`/discovery`**: When macro roadmap planning or micro pre-flight exploration involves system architecture, IT landscape, data pipelines, sequence flows, or user journeys, check for `diagram-design` and generate editorial HTML/SVG diagrams.
-  - **`/feature` & `/fix`**: In Section 2 (`## 📐 2. Technical Spec & Contracts`), invoke `diagram-design` for component diagrams, database ER models, or sequence flows.
+  - **`/discovery`**: When macro roadmap planning or micro pre-flight exploration involves system architecture, IT landscape, data pipelines, sequence flows, or user journeys, check for `archify` (for interactive system maps, data flows, and sequence traces) or `diagram-design` (for editorial and business layouts).
+  - **`/feature` & `/fix`**: In Section 2 (`## 📐 2. Technical Spec & Contracts`), invoke `archify` for interactive component diagrams, state machines, and sequence traces, or `diagram-design` for database ER models.
   - **`/brainstorm` & `/grill`**: Leverage visual trade-off matrices (Quadrant, Radar spider) or domain models (UML class, ER).
   - **`/prototype` & `/report-html`**: Embed standalone HTML/SVG assets seamlessly.
-  - **`/devflow`**: Intent router surfaces installed third-party skills (e.g. `/diagram-design`) directly to the user.
+  - **`/devflow`**: Intent router surfaces installed third-party skills (e.g. `/archify`, `/diagram-design`) directly to the user.
 
 ### 📁 3. Generated Asset Storage Hierarchy
 - **Discovery Stage**: `devflow/discoveries/{id}/diagrams/` (referenced in `discovery.md`).