@jakkrichm/create-nexus-devflow 2.6.0 → 2.6.2

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

@@ -1,6 +1,6 @@
 ---
 name: devflow
-description: "[devflow][B] Flagship interactive guide, state inspector, and intent router for DevFlow workflows."
+description: "[devflow] Flagship interactive guide, state inspector, and intent router for DevFlow workflows."
 ---
 
 # devflow - Interactive Workflow Guide & Intent Router for Nexus-DevFlow

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

@@ -1,6 +1,6 @@
 ---
 name: discovery
-description: "[devflow][D] Unified discovery and exploration stage in DevFlow 2.5.0 - conducts project-level roadmap discovery (project-plan.md/build-plan.md) or feature-level pre-delivery exploration before the Single Living Spec lifecycle."
+description: "[devflow] Unified discovery and exploration stage in DevFlow 2.5.0 - conducts project-level roadmap discovery (project-plan.md/build-plan.md) or feature-level pre-delivery exploration before the Single Living Spec lifecycle."
 argument-hint: "[{title, request, IDEA-xxx, or discovery-id}]"
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 name: doctor
-description: "[devflow][B] Run a read-only Blueprint health check for setup, onboarding, required files, tool adapters, commands, optional verification and CI, Blueprint visibility, ignore rules, planning readiness, overview freshness, and workflow drift. Use when the user runs /doctor, asks whether the Blueprint is installed correctly, wants a health check, setup check, doctor pass, or says something feels off before starting or resuming work."
+description: "[devflow] Run a read-only Blueprint health check for setup, onboarding, required files, tool adapters, commands, optional verification and CI, Blueprint visibility, ignore rules, planning readiness, overview freshness, and workflow drift. Use when the user runs /doctor, asks whether the Blueprint is installed correctly, wants a health check, setup check, doctor pass, or says something feels off before starting or resuming work."
 ---
 
 # doctor - Blueprint health check

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

@@ -1,6 +1,7 @@
 ---
 name: feature
-description: "[devflow][F] Turn a feature from build-plan.md into a buildable spec. With no argument, specs the next unchecked item in the build plan; given a number or name, specs that one. If a clearly new feature does not match the plan, proposes a reviewed plan addition, refreshes the overview after approval, then specs it. Sizes the feature and splits anything too big into smaller sub-features (4a, 4b, ...), writes small, reviewable build steps to devflow/context/current-feature.md, then red-teams its own draft for gaps, oversized steps, and scope creep before stopping at a review gate. Use when the user runs /feature, names or numbers a feature, asks to add and start a new feature, or asks to spec out, break down, or start the next feature."
+description: "[devflow] Turn a feature from build-plan.md into a buildable living spec. Supports Multi-Run Spec Queue: drafts dedicated context in devflow/context/{xxx-slug}/ without blocking additional specs. With no argument, specs the next unchecked item; given a number or name, specs that one. Sizes and splits large items (4a, 4b), generates TDD checklist steps, red-teams the draft, and stops at review gate. Use when running /feature, naming a feature, or drafting the next living spec."
+argument-hint: "[{number, name, DISC-id, or IDEA-id}]"
 ---
 
 # feature - turn a build-plan feature into a buildable spec
@@ -8,18 +9,22 @@ description: "[devflow][F] Turn a feature from build-plan.md into a buildable sp
 Where this sits in the workflow:
 
     project-overview.md  +  build-plan.md  ->  [this skill]  ->  build
-    (source of truth,        (which feature       (the spec for      (code,
-     from /overview)          to build)            one feature)        reviewed)
+    (source of truth,        (which feature       (the spec in       (code,
+     from /overview)          to build)            contexts/xxx/)      reviewed)
 
 `build-plan.md` is intentionally high-level - one line per feature, no detail,
 no ordering ceremony. All of that is this skill's job: take one listed feature,
 read the full context from `project-overview.md`, and turn it into something
-buildable.
+buildable in `devflow/context/{xxx-slug}/spec.md`.
+
+## Multi-Run Spec-Ahead Support
+
+`/feature` supports drafting multiple specs ahead of time. Creating a spec creates a dedicated workspace directory at `devflow/context/{xxx-slug}/` and does **not block** drafting subsequent features.
 
 ## Input
 
 A feature from `build-plan.md`, by number or name - e.g. `/feature 3` or
-`/feature "typing engine"`.
+`/feature "typing engine"` or `/feature DISC-20260826-001`.
 
 The request may also describe a genuinely new feature that is not in the build
 plan yet. That goes through the new-feature intake in Step 1. Never silently add

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

@@ -1,6 +1,7 @@
 ---
 name: fix
-description: "[devflow][F] Document an ad-hoc bug fix or small change (one not in the build plan) into devflow/context/current-feature.md so it runs through the same build loop. Writes a short fix spec and stops; then /implement builds it and /complete logs it to devflow/history/fixes/ and merges. Use when the user runs /fix, reports a bug, or asks to fix or change something that isn't a planned build-plan feature."
+description: "[devflow] Document an ad-hoc bug fix or small change (one not in the build plan) into devflow/context/{xxx-slug}/spec.md so it runs through the same build loop. Supports Multi-Run: drafts dedicated fix context and allows selective /implement [id]. Writes a short fix spec and stops; then /implement builds it and /complete logs it to devflow/history/fixes/ and merges. Use when running /fix, reporting a bug, or fixing an ad-hoc issue."
+argument-hint: "[{title or issue-description}]"
 ---
 
 # fix - document an ad-hoc fix, then build it like anything else
@@ -13,7 +14,7 @@ Where this sits in the workflow:
 
 A fix is a bug or small change that isn't a planned build-plan feature. It runs
 through the same loop as a feature (build with review gates, iterate, then merge);
-it just starts here instead of `/feature`, and is logged separately.
+it creates a dedicated run folder at `devflow/context/{xxx-slug}/` (e.g. `059-fix-login-error`).
 
 ## Input
 
@@ -21,16 +22,13 @@ A description of the bug or change, for example `/fix "password reset email neve
 sends"`. If the user just reported the problem in chat, use that.
 
 The input may also be a finding ID from `devflow/context/findings.md`, alone
-or with a description, for example `/fix F-03`. Pull the problem statement from
-that ledger entry. Use this form only between work items, when
-`current-feature.md` is the reset stub: this skill overwrites that file, so
-while a spec is active, repair its findings through `/implement` instead.
+or with a description, for example `/fix F-03`.
 
 ## Step 1 - write the fix spec
 
 Pull context from `devflow/context/project-overview.md` and `devflow/context/coding-standards.md`,
-then write a short spec to `devflow/context/current-feature.md` (this file holds whatever
-is being built now, feature or fix). Keep it lighter than a feature spec:
+calculate the next sequential running ID (e.g. `059-fix-slug`),
+then write a short spec to `devflow/context/{xxx-slug}/spec.md` (and update `devflow/context/current-feature.md`). Keep it lighter than a feature spec:
 
 - **Title** - the bug or change in a few words.
 - **Type:** Fix  (so `/complete` logs it to `devflow/history/fixes/`, not `devflow/history/features/`).

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

@@ -1,6 +1,6 @@
 ---
 name: grill
-description: "[devflow][B] Interactive Socratic alignment & domain modeling - stress-test plans, extract domain glossary, and record architecture decision records (ADRs) before delivery."
+description: "[devflow] Interactive Socratic alignment & domain modeling - stress-test plans, extract domain glossary, and record architecture decision records (ADRs) before delivery."
 argument-hint: "{topic, plan, or question}"
 ---
 
@@ -89,5 +89,5 @@ Allocate the next sequential ID (`ADR-001`, `ADR-002`, ...) and create `devflow/
 When all design branches are resolved:
 1. Summarize settled domain terms and created ADRs.
 2. Provide explicit next command recommendations:
-   - **Fast-Track (Standard Features/Fixes)**: Run `/feature {topic}` or `/fix {topic}` to immediately start the living spec.
-   - **Deep-Track (Large Architectural Epics)**: Run `10-define` or `/discovery` with the discovery context.
+   - **Living Spec (Standard Delivery)**: Run `/feature {topic}` or `/fix {topic}` to immediately start the living spec.
+   - **Pre-Flight Discovery**: Run `/discovery {topic}` to conduct comprehensive discovery exploration before specification.

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

@@ -1,6 +1,6 @@
 ---
 name: idea
-description: "[devflow][B] Quick idea capture and AI enrichment - analyze feasibility, value, key points, and record into devflow/ideas.md inbox."
+description: "[devflow] Quick idea capture and AI enrichment - analyze feasibility, value, key points, and record into devflow/ideas.md inbox."
 argument-hint: "\"<idea text or description>\""
 ---
 
@@ -44,7 +44,7 @@ Insert the new idea block directly under `## 📌 Pending Ideas` in `devflow/ide
 - **Quick Seed (กันลืม)**:
   1. {ประเด็นสำคัญที่ 1}
   2. {ประเด็นสำคัญที่ 2}
-- **สถานะ**: `Pending` (หยิบไปทำได้ด้วย `/spec IDEA-001` หรือ `/00-explore IDEA-001`)
+- **สถานะ**: `Pending` (หยิบไปทำได้ด้วย `/feature IDEA-001` หรือ `/discovery IDEA-001`)
 ```
 
 *(หากมีข้อความ `*(ยังไม่มีไอเดียค้างอยู่...)*` ให้ลบออกเมื่อมีไอเดียแรก)*
@@ -54,4 +54,4 @@ Report to the user:
 - Allocated Idea ID: `[IDEA-xxx]`
 - Summary of Feasibility & Value analysis
 - Seed points saved
-- Instructions for promotion: "เมื่อพร้อมลงมือทำ สามารถพิมพ์ `/spec IDEA-xxx` หรือ `/00-explore IDEA-xxx` ได้ทันที"
+- Instructions for promotion: "เมื่อพร้อมลงมือทำ สามารถพิมพ์ `/feature IDEA-xxx` หรือ `/discovery IDEA-xxx` ได้ทันที"

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

@@ -1,9 +1,10 @@
 ---
 name: implement
-description: "[devflow][F] Build the feature, fix, or rollback spec'd in devflow/context/current-feature.md, one small reviewable step at a time. Creates the matching branch, implements each step, shows the diff and explains it in plain English, tests, and iterates until it works. Type: Rollback specs use a guarded reverse patch that preserves Blueprint history. After each approved step it offers an optional commit checkpoint on the branch; the work-level commit, merge, and logging are /complete's job. Use when the user runs /implement, or asks to build, implement, or start the current feature, fix, or rollback once its spec is ready."
+description: "[devflow] Build the feature, fix, or rollback spec, one small reviewable step at a time with Strict TDD. Supports Multi-Run: given an optional ID or name (/implement 12, /implement 012), targets that spec from devflow/context/{xxx-slug}/. Checks out matching branch, runs pre-flight drift revalidation, executes TDD steps with diffs, and offers commit checkpoints. Use when running /implement, or starting work on a spec."
+argument-hint: "[{run-id, number, or name}]"
 ---
 
-# implement - build the current spec, one reviewed step at a time
+# implement - build the target spec, one reviewed step at a time
 
 Where this sits in the workflow:
 
@@ -12,7 +13,7 @@ Where this sits in the workflow:
                                         reviewed)        merge + log)
 
 `/feature`, `/fix`, or `/rollback` wrote the spec to
-`devflow/context/current-feature.md` and stopped.
+`devflow/context/{xxx-slug}/spec.md` (or `devflow/context/current-feature.md`) and stopped.
 This skill turns that spec into code, following the build loop in
 `devflow/context/ai-interaction.md`, without vibe coding: small steps, a visible diff plus
 a plain-English explanation for each, testing, and iteration until it works, all
@@ -20,9 +21,14 @@ behind your approval. It builds on a branch and offers an optional commit
 checkpoint after each step; the work-level commit, merging, and logging are
 `/complete`'s job.
 
+## Multi-Run Target Resolution
+
+- **Given an ID or name** (e.g. `/implement 12`, `/implement 012`, `/implement kanban`) -> locates the matching run folder `devflow/context/{xxx-slug}/`, checks out `feature/{xxx-slug}`, and loads only that run's `spec.md`.
+- **With no argument** (`/implement`) -> checks current git branch, or auto-picks if only 1 spec is active, or prompts the user if multiple specs are queued.
+
 ## Before you start
 
-Read `devflow/context/current-feature.md`. If it has no real spec (still the stub, or its
+Read the target spec from `devflow/context/{xxx-slug}/spec.md` (or `devflow/context/current-feature.md`). If it has no real spec (still the stub, or its
 status is already complete), stop and tell the user to run `/feature` (for a
 planned feature), `/fix` (for an ad-hoc bug or change), or `/rollback` (for a
 completed feature reversal) first. Pull the

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

@@ -1,6 +1,6 @@
 ---
 name: onboard
-description: "[devflow][B] Set up the Blueprint after overlaying it onto a freshly scaffolded or early project. Detects the stack, tunes project files and adapters, documents real commands and existing checks, points to the optional standalone CI setup, and tells the user what to fill in before /overview or $overview. Use when the user runs /onboard, invokes $onboard, just copied the Blueprint into a new project, or asks what to do after overlaying the Blueprint. For an existing app with meaningful shipped features, use adopt instead."
+description: "[devflow] Set up the Blueprint after overlaying it onto a freshly scaffolded or early project. Detects the stack, tunes project files and adapters, documents real commands and existing checks, points to the optional standalone CI setup, and tells the user what to fill in before /overview or $overview. Use when the user runs /onboard, invokes $onboard, just copied the Blueprint into a new project, or asks what to do after overlaying the Blueprint. For an existing app with meaningful shipped features, use adopt instead."
 ---
 
 # onboard - finish the Blueprint overlay setup

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

@@ -1,6 +1,6 @@
 ---
 name: overview
-description: "[devflow][B] Distill user-owned planning docs into `devflow/context/project-overview.md` using a deterministic compiler. The overview is the living source of truth that agents read every session."
+description: "[devflow] Distill user-owned planning docs into `devflow/context/project-overview.md` using a deterministic compiler. The overview is the living source of truth that agents read every session."
 ---
 
 # overview - dynamic project overview compiler

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

@@ -1,6 +1,6 @@
 ---
 name: prototype
-description: "[devflow][B] Interactively prototype the look of a project. Asks about the desired look and feel and which pages to draft, proposes a plan, and only then writes throwaway static HTML/CSS mockups to prototypes/ that share one theme (a set of CSS theme variables). A plan-first, pre-build helper that sits outside the spec-driven feature loop, like scaffolding. Use when the user runs /prototype, names screens to mock up, or asks to prototype the layout, theme, or look and feel."
+description: "[devflow] Interactively prototype the look of a project. Asks about the desired look and feel and which pages to draft, proposes a plan, and only then writes throwaway static HTML/CSS mockups to prototypes/ that share one theme (a set of CSS theme variables). A plan-first, pre-build helper that sits outside the spec-driven feature loop, like scaffolding. Use when the user runs /prototype, names screens to mock up, or asks to prototype the layout, theme, or look and feel."
 ---
 
 # prototype - lock the look before you build

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

@@ -1,6 +1,6 @@
 ---
 name: release
-description: "[devflow][B] Prepare a Blueprint project for deployment to Render or Vercel. Reads the plans, project commands, app config, and current repo state; verifies build, start, output, env, health checks, and provider config; can create or update render.yaml or vercel.json when requested; and stops before any external deploy, service creation, remote env change, push, publish, or destructive action unless the user explicitly approves. Use when the user runs /release, invokes $release, asks for Render setup, Vercel setup, deploy readiness, deployment config, render.yaml, or vercel.json."
+description: "[devflow] Prepare a Blueprint project for deployment to Render or Vercel. Reads the plans, project commands, app config, and current repo state; verifies build, start, output, env, health checks, and provider config; can create or update render.yaml or vercel.json when requested; and stops before any external deploy, service creation, remote env change, push, publish, or destructive action unless the user explicitly approves. Use when the user runs /release, invokes $release, asks for Render setup, Vercel setup, deploy readiness, deployment config, render.yaml, or vercel.json."
 ---
 
 # release - deployment readiness for Render and Vercel

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

@@ -1,21 +1,21 @@
 ---
 name: report-html
-description: "[devflow][B] Standalone HTML Report Generator - render an interactive standalone HTML dashboard from current-feature.md or 60-report.md on demand."
-argument-hint: "{running-id or workspace path}"
+description: "[devflow] Standalone HTML Report Generator - render an interactive standalone HTML dashboard from current-feature.md or history archives on demand."
+argument-hint: "[{running-id or workspace path}]"
 ---
 
 # Standalone: Report HTML
 
 $ARGUMENTS
 
-Standalone companion command to generate an interactive, self-contained HTML report dashboard on demand from either a Fast-Track `current-feature.md` or a Deep-Track `60-report.md`.
+Standalone companion command to generate an interactive, self-contained HTML report dashboard on demand from `current-feature.md`, task-specific context `devflow/context/{xxx-slug}/spec.md`, or archived history files in `devflow/history/`.
 
 > [!NOTE]
-> HTML reports are **never automatically generated** during normal mainline stages (`/complete` or `60-report`). Use this command whenever you or stakeholders wish to view or share an interactive web report.
+> HTML reports are **never automatically generated** during normal mainline stages (`/complete`). Use this command whenever you or stakeholders wish to view or share an interactive web report.
 
 ## Invocations & Aliases
 
-- `/report:html`: Generate HTML report for the active or most recent run
+- `/report:html`: Generate HTML report for the active run
 - `/report:html {running-id}`: Generate HTML report for the specified running ID
 - `npm run report:html -- {running-id}`: CLI npm script invocation
 - `$report:html`: Codex CLI invocation
@@ -25,21 +25,21 @@ Standalone companion command to generate an interactive, self-contained HTML rep
 When invoked:
 
 ### 1. Identify Target Run
-1. Locate target run directory in `devflow/runs/{running-id}` from argument or `devflow/context/current-stage.md`.
-2. Check for either:
-   - Fast-Track Living Spec: `devflow/runs/{RUNNING_ID}/current-feature.md` (or `spec.md` / `blueprint.md`)
-   - Deep-Track Report Digest: `devflow/runs/{RUNNING_ID}/60-report.md`
+1. Locate target markdown document:
+   - Active Living Spec: `devflow/context/current-feature.md` or `devflow/context/{xxx-slug}/spec.md`
+   - 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
-Execute the HTML generation engine:
+Execute the HTML generation engine or script:
 ```bash
 npm run report:html -- {RUNNING_ID}
 ```
-Or execute the renderer to transform Markdown into a styled, standalone HTML document:
-- Path: `devflow/runs/{RUNNING_ID}/report.html`
+Or transform Markdown into a styled, standalone HTML document:
+- Output: `devflow/reports/{RUNNING_ID}-report.html` (or adjacent `{xxx-slug}.html`)
 
 ### 3. Output
 Provide:
-- Generated HTML file path: `file:///devflow/runs/{RUNNING_ID}/report.html`
+- Generated HTML file path: `file:///devflow/reports/{RUNNING_ID}-report.html`
 - Summary of sections rendered (Spec, Plan, Progress, QA Evidence, Release Notes)
 - Instructions to open the file in any browser

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

@@ -1,6 +1,6 @@
 ---
 name: rollback
-description: "[devflow][B] Plan a safe reversal of a completed Blueprint feature using its archived spec and squashed git commit. Finds the exact feature commit, reviews later commits for dependency risk, writes a Type: Rollback spec to devflow/context/current-feature.md, and stops for review before /implement applies any code change. Use when the user runs /rollback, asks to remove or undo a completed feature, or wants to return the app to its pre-feature behavior without erasing Blueprint history."
+description: "[devflow] Plan a safe reversal of a completed Blueprint feature using its archived spec and squashed git commit. Finds the exact feature commit, reviews later commits for dependency risk, writes a Type: Rollback spec to devflow/context/current-feature.md, and stops for review before /implement applies any code change. Use when the user runs /rollback, asks to remove or undo a completed feature, or wants to return the app to its pre-feature behavior without erasing Blueprint history."
 ---
 
 # rollback - safely reverse a completed feature

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

@@ -1,6 +1,6 @@
 ---
 name: status
-description: "[devflow][B] Show where the project stands: build-plan progress, the current feature's checked and unchecked steps, git state, drift warnings, and the exact next action. Read-only. Use when the user runs /status, asks where things stand, what's next, what's in progress, or is picking work back up after a break or a context clear."
+description: "[devflow] Show where the project stands: build-plan progress, the current feature's checked and unchecked steps, git state, drift warnings, and the exact next action. Read-only. Use when the user runs /status, asks where things stand, what's next, what's in progress, or is picking work back up after a break or a context clear."
 ---
 
 # status - where the project stands right now

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

@@ -1,6 +1,6 @@
 ---
 name: test
-description: "[devflow][B] Test execution, missing test generation, and coverage analysis across unit, integration, and smoke test suites."
+description: "[devflow] Test execution, missing test generation, and coverage analysis across unit, integration, and smoke test suites."
 ---
 
 # Test-Driven Development, Generation & Execution
@@ -81,14 +81,14 @@ For browser and UI features, unit tests alone are insufficient:
 
 ## 6. Test Generation & Persistent Execution Reports
 
-When generating or logging test runs during `40-execute` or `50-verify`:
+When generating or logging test runs during `/implement` or `/check`:
 - Save summary reports to `devflow/reports/{date}-test-report-{slug}.md`
 - Include: Target, Test Cases (Happy Path, Error, Edge Cases), Pass/Fail statistics, and gaps/risks.
 
 ---
 
-## Relationship To DevFlow 2.0
+## Relationship To DevFlow 2.6.x
 
 - **Classification**: Companion command & Engineering standard
-- **Mainline stages**: `30-plan` (TDD decisions), `40-execute` (TDD execution), `50-verify` (QA gate)
-- **Handoff**: `50-verify`, `Debug`, `autopilot`
+- **Mainline stages**: `feature` / `fix` (TDD decisions), `implement` (TDD execution), `check` (QA gate)
+- **Handoff**: `check`, `debug`, `autopilot`

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

@@ -1,6 +1,6 @@
 ---
 name: tests
-description: "[devflow][B] Add or normalize unit testing for a Blueprint project. Detects the stack, reuses an existing test runner when present, or installs the stack-native unit test runner when missing, then adds one small example test, updates AGENTS.md commands, runs build and tests, and reports the diff. Use when the user runs /tests, invokes $tests, asks to add unit tests, set up unit testing, configure tests, or make tests part of the Blueprint workflow."
+description: "[devflow] Add or normalize unit testing for a Blueprint project. Detects the stack, reuses an existing test runner when present, or installs the stack-native unit test runner when missing, then adds one small example test, updates AGENTS.md commands, runs build and tests, and reports the diff. Use when the user runs /tests, invokes $tests, asks to add unit tests, set up unit testing, configure tests, or make tests part of the Blueprint workflow."
 ---
 
 # tests - add unit testing to the project

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

@@ -1,6 +1,6 @@
 ---
 name: try
-description: "[devflow][B] Generate a human manual try guide for the current or most recently completed Blueprint feature, fix, or rollback. Reads the spec, project commands, and available app context, then tells the user exactly what to start, where to go, what to click or run, what to expect, and what would count as wrong. Read-only. Use when the user runs /try, invokes $try, asks how to test manually, asks where to click, asks how to see the change, or wants a manual review path after /implement, /autopilot, /check, or /complete."
+description: "[devflow] Generate a human manual try guide for the current or most recently completed Blueprint feature, fix, or rollback. Reads the spec, project commands, and available app context, then tells the user exactly what to start, where to go, what to click or run, what to expect, and what would count as wrong. Read-only. Use when the user runs /try, invokes $try, asks how to test manually, asks where to click, asks how to see the change, or wants a manual review path after /implement, /autopilot, /check, or /complete."
 ---
 
 # try - manual review guide

package/template/AGENTS.md

@@ -1,4 +1,4 @@
-# Nexus-DevFlow 2.6.0 (The 3-Pillars & Single Living Spec Model)
+# Nexus-DevFlow 2.6.2 (The 3-Pillars & Single Living Spec Model)
 
 Instructions for AI coding agents working in this project. This is the cross-tool entry point: Codex, Google Antigravity, Cursor, GitHub Copilot, Gemini CLI, Aider, Zed, Windsurf, and others read `AGENTS.md`. Claude Code reads `CLAUDE.md`, which imports this file (`@AGENTS.md`), so there is a single source of truth.
 

package/template/devflow/build-plan.md

@@ -33,7 +33,7 @@
 
 - [x] **4. Just-In-Time (JIT) Dynamic Context Slicing Engine** `[Size: M]`
   - *Dependencies*: Feature 3
-  - *Scope*: สร้างตัวตัดตอนบริบท (Context Slicer) สำหรับสคิล `/implement`, `/check`, `/00-explore` เพื่อส่งเฉพาะข้อมูลที่จำเป็นและควบคุม Token Budget ลดการใช้ Token 60–70%
+  - *Scope*: สร้างตัวตัดตอนบริบท (Context Slicer) สำหรับสคิล `/implement`, `/check`, `/discovery` เพื่อส่งเฉพาะข้อมูลที่จำเป็นและควบคุม Token Budget ลดการใช้ Token 60–70%
 
 ---
 
@@ -84,6 +84,18 @@
   - *Dependencies*: ADR-001
   - *Scope*: รวมความสามารถเชิงสถาปัตยกรรมระดับลึกของ Deep-Track เข้าสู่ 4 ขั้นตอนหลักของ Fast-Track บนเอกสาร Single Living Spec (`current-feature.md`) จัดเก็บประวัติแบบ Single Archive (`.md`), ปลดระวาง stage skills 10-70 ที่ซ้ำซ้อน, และปรับปรุงเอกสาร & Schemas ทั้งหมด
 
+---
+
+## 🚀 Phase 11: Multi-Run Context Architecture & Spec Queue Engine
 
+- [x] **11. Multi-Run Context Architecture & Spec Queue Engine (`IDEA-026`, `DISC-20260826-001`)** `[Size: M]`
+  - *Dependencies*: Feature 10, Feature 3
+  - *Scope*: แยกจัดเก็บ Task-Specific Context เป็นโฟลเดอร์ย่อยใน `devflow/context/{xxx-slug}/`, พัฒนา Context Resolver สำหรับสลับและเรียกใช้งาน `/implement <id>`, `/check <id>`, `/complete <id>` แบบระบุ Running ID หรือ Fuzzy Match, และอัปเกรด CLI/Dashboard/Skills ให้รองรับ Spec Queue หลายรันพร้อมกัน
+
+---
 
+## 🧹 Phase 12: Purge Legacy Deep-Track & Numbered Stage Artifacts
 
+- [x] **12. Purge Legacy Deep-Track & Numbered Stage Artifacts (`DISC-20260826-002`)** `[Size: M]`
+  - *Dependencies*: Feature 10, Feature 11
+  - *Scope*: ล้างโค้ดตกค้างของ Deep-Track (สเตจ 00-70 เช่น `40-execute`, `50-verify`, `60-report`, `70-deliver`, `10-define`, `20-spec`, `30-plan`) ออกจาก package engine (`status.ts`, `current-work.ts`, `history.ts`), agent skills (`.agents/`, `.claude/`), automation scripts & tests ใน `scripts/`, และเอกสาร/mockup ให้เป็นปัจจุบันสมบูรณ์

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

@@ -139,7 +139,7 @@ Progress lives in persistent files, not in transient chat history:
 
 ## 9. Socratic Alignment & Grilling Discipline (`/grill`)
 
-- **Align Before You Build**: When plans, domain language, or architectural boundaries are fuzzy, invoke `/grill` (or use the Grilling Lens in `00-explore`) to conduct a structured interview before creating specifications.
+- **Align Before You Build**: When plans, domain language, or architectural boundaries are fuzzy, invoke `/grill` (or use the Grilling Lens in `/discovery`) to conduct a structured interview before creating specifications.
 - **Codebase-Grounded Inquiry**: Inspect existing context and code before asking questions. Never ask questions the codebase already answers.
 - **Turn Discipline**: Ask only 1–2 high-leverage questions per turn with clear recommended defaults. Never dump a wall of questions.
 - **Lazy Inline Persistence**:

package/template/devflow/context/coding-standards.md

@@ -88,7 +88,7 @@ nexus-devflow/
 ├── devflow/                    # Framework workspace context, history, and discoveries
 │   ├── context/                # Living source-of-truth context files
 │   ├── decisions/              # Architecture Decision Records (ADRs)
-│   ├── discoveries/            # Pre-delivery discovery records (00-explore.md)
+│   ├── discoveries/            # Pre-delivery discovery records (discovery.md)
 │   ├── history/                # Master delivery archive (features/, fixes/, rollbacks/, HISTORY.md)
 │   └── ideas.md                # Idea Inbox and backlog
 ├── packages/
@@ -104,7 +104,7 @@ nexus-devflow/
 ## 6. Naming Conventions
 
 - **Files & Directories**:
-  - Skills and command directories: `kebab-case` (e.g. `00-explore`, `report-html`, `sync-upstream`).
+  - Skills and command directories: `kebab-case` (e.g. `discovery`, `report-html`, `convert-any-to-md`).
   - Source modules and scripts: `kebab-case.ts` / `kebab-case.mjs` (e.g. `current-work.ts`, `check-devflow.ts`).
   - Test files: `[module].test.ts` (e.g. `status.test.ts`, `uninstall.test.ts`).
 - **Identifiers**:

package/template/devflow/decisions/README.md

@@ -1,6 +1,6 @@
 # 🏛️ Architecture Decision Records (ADRs)
 
-This directory stores durable Architecture Decision Records (ADRs) produced during `/grill`, `00-explore`, or high-stakes architectural design sessions.
+This directory stores durable Architecture Decision Records (ADRs) produced during `/grill`, `/discovery`, or high-stakes architectural design sessions.
 
 ---
 

package/template/devflow/history/features/README.md

@@ -1,5 +1,5 @@
 # Completed Features Archive
 
-Finished feature specs, enhancements, architecture migrations, and tooling runs are archived here as `xxx-name.md` (for Fast-Track single living specs) or `xxx-name/` (for Deep-Track stage runs).
+Finished feature specs, enhancements, architecture migrations, and tooling runs are archived here as `{xxx-slug}.md`.
 
 Together they form the project's permanent feature build history, recording what was built, why, and how it was verified.

package/template/devflow/history/fixes/README.md

@@ -1,5 +1,5 @@
 # Completed Fixes Archive
 
-Finished bug fixes, hotfixes, regressions, security patches, and performance optimizations are archived here as `xxx-name.md` (for Fast-Track single living specs) or `xxx-name/` (for Deep-Track stage runs).
+Finished bug fixes, hotfixes, regressions, security patches, and performance optimizations are archived here as `{xxx-slug}.md`.
 
 Together they form the project's permanent bug resolution history, recording root causes, TDD test decisions, and empirical proof.

package/template/devflow/history/rollbacks/README.md

@@ -1,5 +1,5 @@
 # Completed Rollbacks Archive
 
-Safely reversed features and rollback execution records are archived here as `YYYY-MM-DD-xxx-name.md` (or `YYYY-MM-DD-xxx-name/`).
+Safely reversed features and rollback execution records are archived here as `YYYY-MM-DD-{xxx-slug}.md`.
 
 Together they form the project's safe feature reversal ledger, documenting target commits, dependency review, and post-reversal verification.

package/template/devflow/reference/mockup.html

@@ -221,22 +221,21 @@ footer a{color:var(--cyan);text-decoration:none}
         <span class="badge violet">Track: Idle</span>
       </div>
     </div>
-    <dl class="tb-table">
-      <dt>Package</dt><dd>@jakkrichm/create-nexus-devflow</dd>
-      <dt>Adapters</dt><dd>4 detected</dd>
-      <dt>Branch</dt><dd>main</dd>
-      <dt>Revision</dt><dd>2026-08-22</dd>
-    </dl>
+    <div class="meta">
+      <div class="meta-item"><span class="meta-label">Package</span><span class="meta-val">@jakkrichm/create-nexus-devflow</span></div>
+      <div class="meta-item"><span class="meta-label">Adapters</span><span class="meta-val">antigravity, claude, codex, copilot, opencode</span></div>
+      <div class="meta-item"><span class="meta-label">Branch</span><span class="meta-val">main</span></div>
+      <div class="meta-item"><span class="meta-label">Snapshot</span><span class="meta-val">2026-08-26 10:45</span></div>
+    </div>
   </header>
   <div class="live-wrap"><span class="live-dot"></span><span class="muted" style="font:11px var(--font-mono)">Status snapshot · health OK · npx @jakkrichm/create-nexus-devflow status</span></div>
 
-  <!-- Dual-Track Delivery Model -->
+  <!-- Unified Living Spec Model -->
   <section class="pipeline">
     <div class="pipeline-head">
-      <span class="pipeline-title">Dual-Track Delivery Model</span>
+      <span class="pipeline-title">Unified Living Spec Model (Nexus-DevFlow 2.6.x)</span>
       <div class="track-tabs" id="track-tabs">
-        <button class="tab on" data-t="fast">🏎️ Fast-Track · 4 steps</button>
-        <button class="tab" data-t="deep">🏗️ Deep-Track · 8 stages</button>
+        <button class="tab on" data-t="fast">⚡ Living Spec · 4 steps</button>
       </div>
     </div>
 
@@ -245,23 +244,9 @@ footer a{color:var(--cyan);text-decoration:none}
         <div class="step"><span class="step-conn"></span><span class="step-dot">1</span><div class="step-name">feature / fix</div><div class="step-cmd">/feature · /fix</div></div>
         <div class="step"><span class="step-conn"></span><span class="step-dot">2</span><div class="step-name">implement</div><div class="step-cmd">/implement</div></div>
         <div class="step"><span class="step-conn"></span><span class="step-dot">3</span><div class="step-name">check</div><div class="step-cmd">/check</div></div>
-        <div class="step"><span class="step-dot">4</span><div class="step-name">complete</div><div class="step-cmd">/complete</div></div>
-      </div>
-      <div class="track-note"><b>Idle:</b> no active Fast-Track run. Use <code>/feature</code> or <code>/fix</code> to create the Single Living Spec in <code>devflow/context/current-feature.md</code>. Recommended for about 85% of daily engineering work.</div>
-    </div>
-
-    <div class="track-view" id="view-deep">
-      <div class="stepper">
-        <div class="step"><span class="step-conn"></span><span class="step-dot">00</span><div class="step-name">00-explore</div></div>
-        <div class="step"><span class="step-conn"></span><span class="step-dot">10</span><div class="step-name">10-define</div></div>
-        <div class="step"><span class="step-conn"></span><span class="step-dot">20</span><div class="step-name">20-spec</div></div>
-        <div class="step"><span class="step-conn"></span><span class="step-dot">30</span><div class="step-name">30-plan</div></div>
-        <div class="step"><span class="step-conn"></span><span class="step-dot">40</span><div class="step-name">40-execute</div></div>
-        <div class="step"><span class="step-conn"></span><span class="step-dot">50</span><div class="step-name">50-verify</div></div>
-        <div class="step"><span class="step-conn"></span><span class="step-dot">60</span><div class="step-name">60-report</div></div>
-        <div class="step"><span class="step-dot">70</span><div class="step-name">70-deliver</div></div>
+        <div class="step"><span class="step-conn"></span><span class="step-dot">4</span><div class="step-name">complete</div><div class="step-cmd">/complete</div></div>
       </div>
-      <div class="track-note"><b>Reference model:</b> no active Deep-Track run. Recommended for architectural epics, database migrations, security audits, and multi-agent coordination. Progress lives in <code>devflow/context/current-run/</code> and is archived on <code>/70-deliver</code>.</div>
+      <div class="track-note"><b>Single Living Spec:</b> <code>/feature</code>, <code>/implement</code>, <code>/check</code>, <code>/complete</code> with TDD Discipline, Multi-Lane QA, and Durably Categorized History.</div>
     </div>
   </section>
 
@@ -274,7 +259,7 @@ footer a{color:var(--cyan);text-decoration:none}
       </button>
     </div>
     <div class="command" id="next-command">/feature</div>
-    <div class="muted">Workspace is idle and ready for new work. Start a Fast-Track feature, or use <code>/00-explore</code> when the scope needs deeper discovery first.</div>
+    <div class="muted">Workspace is idle and ready for new work. Start a living feature, or use <code>/discovery</code> when the scope needs deeper exploration first.</div>
   </section>
 
   <section class="stats">
@@ -291,7 +276,7 @@ footer a{color:var(--cyan);text-decoration:none}
       <div class="facts">
         <div class="fact"><span>Installed / latest</span><span>v2.0.25 / v2.0.25</span></div>
         <div class="fact"><span>Adapters</span><span>antigravity, codex, claude, copilot</span></div>
-        <div class="fact"><span>Architecture</span><span>3-Pillars + Dual-Track</span></div>
+        <div class="fact"><span>Architecture</span><span>3-Pillars + Living Spec</span></div>
       </div>
     </article>
 
@@ -350,7 +335,7 @@ footer a{color:var(--cyan);text-decoration:none}
       <div class="card-head"><span class="label">Discoveries</span><span class="value">0</span></div>
       <div class="disc-item">
         <div class="disc-id">NO ACTIVE DISCOVERY</div>
-        <div class="disc-title">Use /00-explore to investigate a request before delivery commitment.</div>
+        <div class="disc-title">Use /discovery to investigate a request before delivery commitment.</div>
         <div class="disc-status" style="color:var(--mint)">workspace ready</div>
       </div>
     </article>
@@ -372,7 +357,7 @@ footer a{color:var(--cyan);text-decoration:none}
       <button class="cmdp" data-cmd="rollback" data-tip="Plan a safe reversal with dependency and regression risk analysis.">rollback</button>
       <button class="cmdp" data-cmd="ci" data-tip="Set up the GitHub Actions verification workflow for the project.">ci</button>
       <button class="cmdp" data-cmd="test" data-tip="Inspect test suites and verify the test runner configuration.">test</button>
-      <button class="cmdp" data-cmd="autopilot" data-tip="Run a bounded Fast-Track or Deep-Track execution loop with quality gates.">autopilot</button>
+      <button class="cmdp" data-cmd="autopilot" data-tip="Run a bounded spec/build/check execution loop with quality gates.">autopilot</button>
       <button class="cmdp" data-cmd="prototype" data-tip="Create a throwaway static HTML/CSS mockup to settle UI direction before build.">prototype</button>
       <button class="cmdp" data-cmd="report-html" data-tip="Generate the optional standalone interactive HTML delivery report.">report-html</button>
     </div>
@@ -412,7 +397,7 @@ footer a{color:var(--cyan);text-decoration:none}
       <div class="hist-item"><span class="hist-bar feature"></span><span class="hist-type">feature 039</span><span class="hist-title">Dynamic Project Overview Compiler (/overview) พร้อม Living Context Sync</span></div>
       <div class="hist-item"><span class="hist-bar feature"></span><span class="hist-type">feature 038</span><span class="hist-title">Sub-Feature Automatic Splitting Engine และ Sub-Feature ID Contract</span></div>
       <div class="hist-item"><span class="hist-bar feature"></span><span class="hist-type">feature 037</span><span class="hist-title">Feature Briefing &amp; Deep Scope Assessment Skill (/brief)</span></div>
-      <div class="hist-item"><span class="hist-bar feature"></span><span class="hist-type">feature 036</span><span class="hist-title">Cloud Deployment Readiness Skill (/release) และ 70-deliver</span></div>
+      <div class="hist-item"><span class="hist-bar feature"></span><span class="hist-type">feature 036</span><span class="hist-title">Cloud Deployment Readiness Skill (/release)</span></div>
       <div class="hist-item"><span class="hist-bar feature"></span><span class="hist-type">feature 035</span><span class="hist-title">Guided Project Discovery Interview Skill (/discovery)</span></div>
       <div class="hist-item"><span class="hist-bar feature"></span><span class="hist-type">feature 034</span><span class="hist-title">Dedicated Code &amp; Security Audit Skill (/audit)</span></div>
       <div class="hist-item"><span class="hist-bar feature"></span><span class="hist-type">feature 033</span><span class="hist-title">User-Owned Planning Documents (project-plan.md &amp; build-plan.md)</span></div>