@jakkrichm/create-nexus-devflow 2.0.16 → 2.0.19

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

@@ -16,7 +16,7 @@ Use this skill to guide the user on what to do next, inspect current workspace s
 
 Nexus-DevFlow supports two seamless workflow tracks:
 1. **🏎️ Fast-Track (Blueprint Mode - 4 Steps)**: `/spec` ➔ `/implement` ➔ `/check` ➔ `/complete`  
-   *Driven by a **Single Living Spec (`spec.md`)** for fast, high-velocity daily development and bugfixes (85% of tasks).*
+   *Driven by a **Single Living Spec (`current-feature.md`)** for fast, high-velocity daily development and bugfixes (85% of tasks).*
 2. **🏗️ Deep-Track (Architect Mode - 8 Steps)**: `00-discover` ➔ `10-define` ➔ `20-spec` ➔ `30-plan` ➔ `40-execute` ➔ `50-verify` ➔ `60-report` ➔ `70-release`  
    *Driven by modular separate stage files for large, high-stakes architectural epics and multi-agent coordination.*
 
@@ -28,8 +28,8 @@ When invoked without an argument (or when determining the next step), inspect:
 
 1. **Project Setup Baseline**: Read `devflow/context/project-overview.md` and `devflow/context/coding-standards.md`. If empty or default placeholders, recommend `onboard` (for fresh projects) or `adopt` (for existing codebases).
 2. **Active Delivery Run**: Read `devflow/context/current-stage.md` and check `devflow/runs/{RUNNING_ID}/`.
-   - **If Fast-Track (`spec.md` or `blueprint.md` present)**:
-     - If `spec.md` has incomplete checklist items -> Recommend `/implement` (or `implement {RUNNING_ID}`).
+   - **If Fast-Track (`current-feature.md`, `spec.md`, or `blueprint.md` present)**:
+     - If `current-feature.md` (or `spec.md`) has incomplete checklist items -> Recommend `/implement` (or `implement {RUNNING_ID}`).
      - If all tasks done but no passing verification evidence -> Recommend `/check` (or `check {RUNNING_ID}`).
      - If verification evidence passed -> Recommend `/complete` (or `complete {RUNNING_ID}`).
    - **If Deep-Track (numbered stage files present)**:
@@ -61,7 +61,7 @@ When invoked without an argument (or when determining the next step), inspect:
 | **"Execute implementation tasks"** | `implement` | `/implement` | **Fast-Track**: `/implement` -> `/check` |
 | **"Run QA verification & check"** | `check` | `/check` | **Fast-Track**: `/check` -> `/complete` |
 | **"Complete run & git merge"** | `complete` | `/complete` | **Fast-Track**: `/complete` |
-| **"Generate HTML dashboard report"**| `report-html` | `/report:html` | **Standalone**: Converts `spec.md` / `60-report.md` to HTML |
+| **"Generate HTML dashboard report"**| `report-html` | `/report:html` | **Standalone**: Converts `current-feature.md` / `60-report.md` to HTML |
 | "Setup DevFlow on fresh/new project" | `onboard` | `onboard` / `setup` | `onboard` -> `/spec` or `10-define` |
 | "Adopt DevFlow on existing codebase" | `adopt` | `adopt` / `bootstrap` | `adopt` -> `/spec` or `10-define` |
 | "Check setup health & diagnostics" | `doctor` | `doctor` / `health` | `doctor` |
@@ -85,7 +85,7 @@ When invoked without an argument (or when determining the next step), inspect:
 ## Available Skills Sitemap
 
 ### 1. Fast-Track (Blueprint Mode - 4 Steps)
-- `spec` (`/spec`, `/feature`, `/fix`, `$spec`) - Define, spec, plan, and create `spec.md`
+- `spec` (`/spec`, `/feature`, `/fix`, `$spec`) - Define, spec, plan, and create `current-feature.md`
 - `implement` (`/implement`, `$implement`) - Execute planned checklist tasks with TDD
 - `check` (`/check`, `$check`) - Senior QA review, multi-lane verification, record evidence
 - `complete` (`/complete`, `$complete`) - Safety pass, release digest, git merge, close run

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

@@ -1,6 +1,6 @@
 ---
 name: feature
-description: "[Devflow] Fast-Track Feature stage in DevFlow (Blueprint Mode) - define, spec, plan, and create the living spec.md contract for new features."
+description: "[Devflow] Fast-Track Feature stage in DevFlow (Blueprint Mode) - define, spec, plan, and create the living current-feature.md contract in context for new features."
 argument-hint: "{feature title, IDEA-xxx, or feature description}"
 ---
 
@@ -8,7 +8,7 @@ argument-hint: "{feature title, IDEA-xxx, or feature description}"
 
 $ARGUMENTS
 
-Fast-Track entry point combining Discovery, Definition, Specification, and Implementation Planning into one streamlined, review-gated step for **new features or enhancements**. Creates and maintains the **Single Living Spec (`spec.md`)** for the feature run. Supports intake from Idea Inbox (`IDEA-xxx`).
+Fast-Track entry point combining Discovery, Definition, Specification, and Implementation Planning into one streamlined, review-gated step for **new features or enhancements**. Creates and maintains the **Single Living Spec (`devflow/context/current-feature.md`)** for the feature run. Supports intake from Idea Inbox (`IDEA-xxx`).
 
 ## Invocations & Aliases
 
@@ -26,25 +26,31 @@ Fast-Track entry point combining Discovery, Definition, Specification, and Imple
 
 When invoked:
 
-### 1. Work Identity & Idea Intake
-1. Inspect `devflow/context/current-stage.md` and `devflow/runs/`.
-2. **Idea Inbox Intake**: If the argument is an idea identifier (e.g. `IDEA-001`):
+### 1. Single Active Run Guardrail (One Thing at a Time)
+1. Inspect `devflow/context/current-stage.md` and `devflow/context/current-feature.md`.
+2. If `Active Running ID` is not `None` and `Current Stage` is not `Idle`, or if `current-feature.md` contains an active uncompleted spec:
+   - **HALT and reject opening a new feature**.
+   - Explain to the user that an active run is currently in progress:
+     > ⚠️ *"มีงาน `{active_id}` กำลังดำเนินการอยู่ กรุณาปิดงานเดิมด้วย `/complete` หรือ `70-release` (หรือสั่ง `/rollback`) ก่อนเริ่มงานใหม่"*
+
+### 2. Work Identity & Idea Intake
+1. **Idea Inbox Intake**: If the argument is an idea identifier (e.g. `IDEA-001`):
    - Read `devflow/ideas.md` and extract the idea's title, raw problem statement, AI Feasibility notes, and Quick Seed points.
    - Use these details as the primary input for Specification & Scope.
-   - In `devflow/ideas.md`, update the item's status to `[x] Claimed ({RUNNING_ID})` and move it under `## 📦 Archived / Shipped Ideas`.
-3. Determine or allocate the sequential Running ID (e.g. `RUN-018-{slug}`).
-4. Identify Git branch naming:
-   - `feature/{slug}-{RUNNING_ID}`
-5. Create directory `devflow/runs/{RUNNING_ID}/`.
+   - In `devflow/ideas.md`, update the item's status to `[x] Claimed ({ID})` and move it under `## 📦 Archived / Shipped Ideas`.
+2. Inspect `devflow/history/HISTORY.md` and determine the next sequential ID without prefix (e.g. `022-{slug}`).
+3. Identify Git branch naming:
+   - `feature/{xxx-slug}`
 
-### 2. Generate the Single Living Spec (`spec.md`)
-Write `devflow/runs/{RUNNING_ID}/spec.md` using the structured template below in **Thai (`th`)**:
+### 3. Generate the Living Spec (`devflow/context/current-feature.md`)
+Write `devflow/context/current-feature.md` using the structured template below in **Thai (`th`)**:
 
 ```markdown
-# 📐 [{RUNNING_ID}] {Feature Title} (Living Spec)
+# 📐 [{ID}] {Feature Title} (Living Spec)
 
 > **Status**: In-Progress  
 > **Track**: Fast-Track (Blueprint Mode - Feature)  
+> **Category**: Feature  
 > **Branch**: `{branch_name}`  
 > **Created Date**: {YYYY-MM-DD}  
 > **Owner**: {Contributor or Team}  
@@ -87,17 +93,16 @@ Write `devflow/runs/{RUNNING_ID}/spec.md` using the structured template below in
 - *(จะถูกบันทึกเมื่อรัน /complete)*
 ```
 
-### 3. Update Workspace Status
+### 4. Update Workspace Status
 Update `devflow/context/current-stage.md`:
-- `Active Running ID`: `{RUNNING_ID}`
+- `Active Discovery ID`: `None`
+- `Active Running ID`: `{ID}`
 - `Current Stage`: `feature (Fast-Track -> Ready for /implement)`
-- `Living Spec`: `devflow/runs/{RUNNING_ID}/spec.md`
+- `Living Spec`: `devflow/context/current-feature.md`
 - `Last Updated`: `{YYYY-MM-DD}`
 
-### 4. Output Summary & Next Step
+### 5. Output Summary & Next Step
 Report to the user:
 - Running ID and allocated branch
 - Summary of Scope and Acceptance Criteria
-- Living Spec path: `devflow/runs/{RUNNING_ID}/spec.md`
-- If promoted from `IDEA-xxx`, confirm status update in `devflow/ideas.md`
-- **Next Command**: `/implement` (or `/implement {RUNNING_ID}`)
+- Explicit next step: `/implement`

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

@@ -1,6 +1,6 @@
 ---
 name: fix
-description: "[Devflow] Fast-Track Fix stage in DevFlow (Blueprint Mode) - define, spec, plan, and create the living spec.md contract for bug fixes."
+description: "[Devflow] Fast-Track Fix stage in DevFlow (Blueprint Mode) - define, spec, plan, and create the living current-feature.md contract in context for bug fixes."
 argument-hint: "{bug description, issue ID, or IDEA-xxx}"
 ---
 
@@ -8,7 +8,7 @@ argument-hint: "{bug description, issue ID, or IDEA-xxx}"
 
 $ARGUMENTS
 
-Fast-Track entry point combining Bug Triage, Root Cause Isolation, Specification, and Implementation Planning into one streamlined, review-gated step for **bug fixes and hotfixes**. Creates and maintains the **Single Living Spec (`spec.md`)** for the fix run.
+Fast-Track entry point combining Bug Triage, Root Cause Isolation, Specification, and Implementation Planning into one streamlined, review-gated step for **bug fixes and hotfixes**. Creates and maintains the **Single Living Spec (`devflow/context/current-feature.md`)** for the fix run.
 
 ## Invocations & Aliases
 
@@ -26,24 +26,30 @@ Fast-Track entry point combining Bug Triage, Root Cause Isolation, Specification
 
 When invoked:
 
-### 1. Work Identity & Issue Intake
-1. Inspect `devflow/context/current-stage.md` and `devflow/runs/`.
-2. **Idea / Issue Inbox Intake**: If the argument is an identifier (e.g. `IDEA-001`):
+### 1. Single Active Run Guardrail (One Thing at a Time)
+1. Inspect `devflow/context/current-stage.md` and `devflow/context/current-feature.md`.
+2. If `Active Running ID` is not `None` and `Current Stage` is not `Idle`, or if `current-feature.md` contains an active uncompleted spec:
+   - **HALT and reject opening a new fix**.
+   - Explain to the user that an active run is currently in progress:
+     > ⚠️ *"มีงาน `{active_id}` กำลังดำเนินการอยู่ กรุณาปิดงานเดิมด้วย `/complete` หรือ `70-release` (หรือสั่ง `/rollback`) ก่อนเริ่มงานใหม่"*
+
+### 2. Work Identity & Issue Intake
+1. **Idea / Issue Inbox Intake**: If the argument is an identifier (e.g. `IDEA-001`):
    - Read `devflow/ideas.md` or issue notes and extract problem statement and root cause hints.
-   - In `devflow/ideas.md`, update status to `[x] Claimed ({RUNNING_ID})` and move under `## 📦 Archived / Shipped Ideas`.
-3. Determine or allocate the sequential Running ID (e.g. `RUN-018-{slug}`).
-4. Identify Git branch naming:
-   - `fix/{slug}-{RUNNING_ID}`
-5. Create directory `devflow/runs/{RUNNING_ID}/`.
+   - In `devflow/ideas.md`, update status to `[x] Claimed ({ID})` and move under `## 📦 Archived / Shipped Ideas`.
+2. Inspect `devflow/history/HISTORY.md` and determine the next sequential ID without prefix (e.g. `022-{slug}`).
+3. Identify Git branch naming:
+   - `fix/{xxx-slug}`
 
-### 2. Generate the Single Living Spec (`spec.md`)
-Write `devflow/runs/{RUNNING_ID}/spec.md` using the structured template below in **Thai (`th`)**:
+### 3. Generate the Living Spec (`devflow/context/current-feature.md`)
+Write `devflow/context/current-feature.md` using the structured template below in **Thai (`th`)**:
 
 ```markdown
-# 📐 [{RUNNING_ID}] {Bug/Fix Title} (Living Spec)
+# 📐 [{ID}] {Bug/Fix Title} (Living Spec)
 
 > **Status**: In-Progress  
 > **Track**: Fast-Track (Blueprint Mode - Fix)  
+> **Category**: Fix  
 > **Branch**: `{branch_name}`  
 > **Created Date**: {YYYY-MM-DD}  
 > **Owner**: {Contributor or Team}  
@@ -87,16 +93,16 @@ Write `devflow/runs/{RUNNING_ID}/spec.md` using the structured template below in
 - *(จะถูกบันทึกเมื่อรัน /complete)*
 ```
 
-### 3. Update Workspace Status
+### 4. Update Workspace Status
 Update `devflow/context/current-stage.md`:
-- `Active Running ID`: `{RUNNING_ID}`
+- `Active Discovery ID`: `None`
+- `Active Running ID`: `{ID}`
 - `Current Stage`: `fix (Fast-Track -> Ready for /implement)`
-- `Living Spec`: `devflow/runs/{RUNNING_ID}/spec.md`
+- `Living Spec`: `devflow/context/current-feature.md`
 - `Last Updated`: `{YYYY-MM-DD}`
 
-### 4. Output Summary & Next Step
+### 5. Output Summary & Next Step
 Report to the user:
 - Running ID and allocated branch
 - Summary of Scope, Reproduction, and Acceptance Criteria
-- Living Spec path: `devflow/runs/{RUNNING_ID}/spec.md`
-- **Next Command**: `/implement` (or `/implement {RUNNING_ID}`)
+- Explicit next step: `/implement`

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

@@ -1,6 +1,6 @@
 ---
 name: implement
-description: "[Devflow] Fast-Track Implement stage in DevFlow (Blueprint Mode) - execute checklist tasks incrementally with TDD and update spec.md."
+description: "[Devflow] Fast-Track Implement stage in DevFlow (Blueprint Mode) - execute checklist tasks incrementally with TDD and update current-feature.md in context."
 argument-hint: "{running-id or workspace path}"
 ---
 
@@ -8,18 +8,18 @@ argument-hint: "{running-id or workspace path}"
 
 $ARGUMENTS
 
-Incremental code execution stage in Fast-Track. Reads the Single Living Spec (`spec.md`), executes checklist tasks, implements tests (TDD), and updates the implementation record.
+Incremental code execution stage in Fast-Track. Reads the Single Living Spec (`devflow/context/current-feature.md`), executes checklist tasks, implements tests (TDD), and updates the implementation record.
 
 ## Invocations & Aliases
 
 - `/implement`: Run implementation on current active run
-- `/implement {running-id}`: Run implementation on specified running ID
+- `/implement {id}`: Run implementation on specified ID
 - `$implement`: Codex CLI invocation
 
 ## Fast-Track Mainline Workflow
 
 ```text
-/spec ──▶ /implement ──▶ /check ──▶ /complete
+/feature (หรือ /fix) ──▶ /implement ──▶ /check ──▶ /complete
 ```
 
 ## Behavior & Contract
@@ -27,8 +27,8 @@ Incremental code execution stage in Fast-Track. Reads the Single Living Spec (`s
 When invoked:
 
 ### 1. Load Active Context
-1. Identify active Running ID from `devflow/context/current-stage.md` or argument.
-2. Read `devflow/runs/{RUNNING_ID}/spec.md`.
+1. Identify active Running ID from `devflow/context/current-stage.md` or `devflow/context/current-feature.md`.
+2. Read `devflow/context/current-feature.md`.
 3. Locate `## 2. Plan & Test Strategy` and `## 3. Implementation Checklist`.
 
 ### 2. Incremental Execution with TDD
@@ -37,10 +37,10 @@ When invoked:
    - **TDD (Red-Green-Refactor)**: When `Test Decision: Required`, create or update unit tests first.
    - Implement the minimal, clean code change satisfying the task.
    - Run localized verification (e.g. `npm test`, linter).
-   - Mark the item as `- [x]` in `spec.md`.
+   - Mark the item as `- [x]` in `current-feature.md`.
 
-### 3. Update Living Spec (`spec.md`)
-Append or update `## 4. Implementation Record` in `spec.md` with:
+### 3. Update Living Spec (`current-feature.md`)
+Append or update `## 4. Implementation Record` in `devflow/context/current-feature.md` with:
 - Summary of completed tasks and modified files
 - Key architectural observations or notes
 - Status of checklist items
@@ -61,4 +61,4 @@ Update `devflow/context/current-stage.md`:
 Report to the user:
 - Completed checklist items and modified files
 - Local verification results
-- **Next Command**: `/check` (or `/check {RUNNING_ID}`)
+- **Next Command**: `/check` (or `/check {ID}`)

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

@@ -1,6 +1,6 @@
 ---
 name: insight
-description: "[Devflow] Extract reusable lessons, architectural patterns, post-mortem incident learning, and token optimizations from completed work."
+description: "[Devflow] Extract reusable lessons, patterns, file insights, and post-mortem learning from completed work."
 ---
 
 # Insight Extraction & Post-Mortem Learning

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

@@ -13,7 +13,7 @@ codebase + devflow/history/HISTORY.md  ->  [overview]  ->  devflow/context/proje
                                              synthesize)
 ```
 
-`overview` is the context synchronization and synthesis engine for Nexus-DevFlow. It inspects the actual codebase (manifest, dependencies, directory layout, models/schemas, entry points) along with the completed delivery history (`devflow/history/HISTORY.md` and `devflow/runs/`) to build or refresh `devflow/context/project-overview.md`.
+`overview` is the context synchronization and synthesis engine for Nexus-DevFlow. It inspects the actual codebase (manifest, dependencies, directory layout, models/schemas, entry points) along with the completed delivery history (`devflow/history/HISTORY.md` and `devflow/history/`) to build or refresh `devflow/context/project-overview.md`.
 
 It ensures that `project-overview.md` remains a **Living Source of Truth** that evolves alongside your software, rather than a stale artifact left behind after onboarding.
 
@@ -26,7 +26,7 @@ overview
 ```
 
 Use this when:
-- Multiple delivery runs (`RUN-xxx`) have shipped and `project-overview.md` needs to reflect newly added capabilities.
+- Multiple delivery runs (`xxx-slug`) have shipped and `project-overview.md` needs to reflect newly added capabilities.
 - New database schemas, ORM models, or API boundaries were introduced.
 - Major dependencies or architectural patterns were added or modified.
 - After completing `70-release` to keep project context perfectly aligned.
@@ -59,7 +59,7 @@ Inspect the actual codebase to establish hard facts:
 Inspect DevFlow history records:
 
 1. Read `devflow/history/HISTORY.md` for completed and released milestones.
-2. Scan completed delivery runs in `devflow/runs/` to extract shipped user-visible capabilities and core system features.
+2. Scan completed delivery runs in `devflow/history/features/`, `devflow/history/fixes/`, and `devflow/history/rollbacks/` to extract shipped user-visible capabilities and core system features.
 
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 name: report-html
-description: "[Devflow] Standalone HTML Report Generator - render an interactive standalone HTML dashboard from spec.md or 60-report.md on demand."
+description: "[Devflow] 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}"
 ---
 
@@ -8,7 +8,7 @@ argument-hint: "{running-id or workspace path}"
 
 $ARGUMENTS
 
-Standalone companion command to generate an interactive, self-contained HTML report dashboard on demand from either a Fast-Track `spec.md` or a Deep-Track `60-report.md`.
+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`.
 
 > [!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.
@@ -27,7 +27,7 @@ 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}/spec.md` (or `blueprint.md`)
+   - 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`
 
 ### 2. Render Interactive HTML Dashboard

package/template/.claude/skills/security-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: security-review
-description: "[Devflow] Security review, vulnerability scanner, and code hardening. Audits for OWASP vulnerabilities, secrets, injections, and auth flaws."
+description: "[Devflow] High-severity security code review and vulnerability audit for folders, projects, files, or diffs."
 ---
 
 # Security Review, Hardening & Vulnerability Audit

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

@@ -1,6 +1,6 @@
 ---
 name: spec
-description: "[Devflow] Fast-Track Spec router in DevFlow (Blueprint Mode) - aliases and routes to /feature or /fix to create the single living spec.md contract."
+description: "[Devflow] Fast-Track Spec router in DevFlow (Blueprint Mode) - aliases and routes to /feature or /fix to create the living current-feature.md contract in context."
 argument-hint: "{feature title, bug description, IDEA-xxx, or running-id}"
 ---
 
@@ -8,7 +8,7 @@ argument-hint: "{feature title, bug description, IDEA-xxx, or running-id}"
 
 $ARGUMENTS
 
-Unified Fast-Track entry point that routes to `/feature` or `/fix` to create and maintain the **Single Living Spec (`spec.md`)**.
+Unified Fast-Track entry point that routes to `/feature` or `/fix` to create and maintain the **Single Living Spec (`devflow/context/current-feature.md`)**.
 
 > [!TIP]
 > **Preferred Commands**:
@@ -32,7 +32,8 @@ Unified Fast-Track entry point that routes to `/feature` or `/fix` to create and
 
 When invoked:
 
-1. If the input describes a bug or hotfix, routes to `/fix` behavior.
-2. Otherwise, routes to `/feature` behavior.
-3. Allocates sequential Running ID (`RUN-xxx`), creates directory `devflow/runs/{RUNNING_ID}/`, and generates `spec.md` in **Thai (`th`)**.
-4. Updates `devflow/context/current-stage.md` and reports next step: `/implement`.
+1. Checks Single Active Run Guardrail: rejects if an uncompleted active run already exists in `devflow/context/current-stage.md` or `devflow/context/current-feature.md`.
+2. If the input describes a bug or hotfix, routes to `/fix` behavior.
+3. Otherwise, routes to `/feature` behavior.
+4. Allocates sequential ID without prefix (`xxx-slug`), generates `devflow/context/current-feature.md` in **Thai (`th`)**.
+5. Updates `devflow/context/current-stage.md` and reports next step: `/implement`.

package/template/.claude/skills/spec-driven-development/SKILL.md

@@ -83,8 +83,8 @@ Don't silently fill in ambiguous requirements. The spec's entire purpose is to s
 
 Every specification must stand on its own in markdown under `devflow/runs/{ID}-*/`:
 
-1. **`define.md`**: Decision and scope framing when the problem still needs clarification.
-2. **`spec.md`**: The delivery contract following the template below.
+1. **`current-feature.md`**: Fast-Track Single Living Spec delivery contract.
+2. **`20-spec.md`**: Deep-Track formal specification delivery contract.
 
 **Spec template:**
 

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

@@ -1,6 +1,6 @@
 ---
 name: test
-description: "[Devflow] Test-driven development, test generation, test execution, 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

package/template/AGENTS.md

@@ -1,12 +1,13 @@
-# Nexus-DevFlow 2.0 (Dual-Track Blueprint & Architect Model)
+# Nexus-DevFlow 2.0 (The 3-Pillars & Dual-Track 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.
 
 ## What this is
 
-This project uses **Nexus-DevFlow**, an agentic workflow layer supporting **Dual-Track Delivery**:
-1. **🏎️ Fast-Track (Blueprint Mode - 4 Steps)**: High-velocity spec-driven loop driven by a **Single Living Spec (`spec.md`)**.
-2. **🏗️ Deep-Track (Architect Mode - 8 Steps)**: Full-lifecycle delivery pipeline with modular stage artifacts (`00-70`).
+This project uses **Nexus-DevFlow**, an agentic workflow layer supporting **The 3-Pillars Workspace Architecture & Dual-Track Delivery**:
+1. **🔮 Future (Backlog)**: `devflow/ideas.md` — Centralized Idea Inbox with AI scoring.
+2. **⚡ Present (Active Context)**: `devflow/context/` — Living Source of Truth & Active Work (`current-feature.md` for Fast-Track, `current-run/` for Deep-Track).
+3. **📦 Past (History Archive)**: `devflow/history/` — Categorized delivery archives (`features/`, `fixes/`, `rollbacks/`, and `HISTORY.md`).
 
 To start a new project, scaffold the application first in an empty folder, then run `npx @jakkrichm/create-nexus-devflow` to overlay DevFlow onto your codebase.
 
@@ -35,8 +36,8 @@ Unused adapter families can be removed. Codex and Antigravity projects keep `.ag
    - **Dollar Prefix (`$`)**: For OpenAI Codex CLI or skill-invocation tools, e.g., `$feature`, `$fix`, `$40-execute`, `$devflow`.
 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 `devflow/context/current-stage.md` and active runs in `devflow/runs/`.
-5. **Default Artifact & Communication Language (Thai)**: All generated markdown stage artifacts (`spec.md`, `00-discover.md`...`70-release.md`) and user communication MUST default to **Thai (`th`)**, while code, technical terms, file paths, and identifiers remain in English.
+4. **State-Aware Inspection**: When unsure what to do next, invoke `devflow` to automatically inspect `devflow/context/current-stage.md` and active context in `devflow/context/`.
+5. **Default Artifact & Communication Language (Thai)**: All generated markdown stage artifacts (`current-feature.md`, `00-discover.md`...`70-release.md`) and user communication MUST default to **Thai (`th`)**, while code, technical terms, file paths, and identifiers remain in English.
 
 ---
 
@@ -49,14 +50,14 @@ Recommended for 85% of daily work (features, bug fixes, UI improvements, iterati
 ```
 
 1. **`feature` / `fix` (`/feature`, `/fix`, `/spec`)**:
-   - **Purpose**: Combines Discover, Define, Spec, and Plan into one unified step. Allocates sequential Running ID (`RUN-xxx`) and creates the **Single Living Spec (`spec.md`)**.
-   - **Artifact**: `devflow/runs/{running-id}-{slug}/spec.md`
+   - **Purpose**: Combines Discover, Define, Spec, and Plan into one unified step. Checks Single Active Run Guardrail, allocates sequential ID (`xxx-slug`), and creates the **Single Living Spec (`devflow/context/current-feature.md`)**.
+   - **Artifact**: `devflow/context/current-feature.md`
 2. **`implement` (`/implement`)**:
-   - **Purpose**: Incrementally executes checklist tasks with TDD discipline and appends progress to `spec.md`.
+   - **Purpose**: Incrementally executes checklist tasks with TDD discipline and appends progress to `devflow/context/current-feature.md`.
 3. **`check` (`/check`)**:
-   - **Purpose**: Senior QA review, multi-lane verification matrix (Typecheck, Lint, Test suites, manual proof), and records evidence into `spec.md`.
+   - **Purpose**: Senior QA review, multi-lane verification matrix (Typecheck, Lint, Test suites, manual proof), and records evidence into `devflow/context/current-feature.md`.
 4. **`complete` (`/complete`)**:
-   - **Purpose**: Final safety pass, records Release Digest in `spec.md`, performs git merge, and closes the run without auto HTML generation.
+   - **Purpose**: Final safety pass, records Release Digest, automatically archives to `devflow/history/{features|fixes|rollbacks}/{xxx-slug}.md`, resets the stub, performs git merge, and closes the run without auto HTML generation.
 
 ---
 
@@ -69,13 +70,13 @@ Recommended for large architectural epics, database migrations, and multi-agent
 ```
 
 1. `00-discover`: Explore request before delivery commitment without allocating running ID (`00-discover.md`).
-2. `10-define`: Turn approved discovery into bounded delivery run(s) with sequential Running IDs (`10-define.md`).
+2. `10-define`: Turn approved discovery into bounded delivery run in `devflow/context/current-run/10-define.md`.
 3. `20-spec`: Formalize markdown-first delivery contract & acceptance criteria (`20-spec.md`).
 4. `30-plan`: Breakdown spec into executable tasks with test decisions (`30-plan.md` + checklists).
 5. `40-execute`: Incremental task execution behind review gates (`40-execute.md`).
 6. `50-verify`: Senior QA review & multi-lane verification checks (`50-verify.md`).
 7. `60-report`: Standardized markdown delivery digest (`60-report.md`).
-8. `70-release`: Release packaging, release notes, git merge, and deployment (`70-release.md`).
+8. `70-release`: Release packaging, git merge, archives `devflow/context/current-run/` ➔ `devflow/history/{category}/{xxx-slug}/`, and closes run.
 
 ---
 
@@ -84,55 +85,10 @@ Recommended for large architectural epics, database migrations, and multi-agent
 > [!IMPORTANT]
 > **No Auto-Generated HTML**: Mainline flows (`/complete` and `60-report`) 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 -- {RUNNING_ID}`).
+> `/report:html` (or `npm run report:html -- {ID}`).
 
 ---
 
-## Public Companion Commands
-
-- `devflow`: Flagship interactive guide, state inspector, and intent router.
-- `idea` (`/idea`): Quick idea capture and AI feasibility enrichment into `devflow/ideas.md`.
-- `report-html` (`/report:html`): Standalone interactive HTML report dashboard generator.
-- `onboard`: Initial stack detection and baseline setup for fresh/scaffolded projects.
-- `adopt`: Survey existing brownfield codebases and bootstrap DevFlow context.
-- `doctor`: Read-only health check for context files, adapters, commands, and workflow drift.
-- `try`: Step-by-step human manual QA review guide (where to go, what to click, what to expect).
-- `rollback`: Safe feature/run reversal planner with dependency and commit risk analysis.
-- `ci`: Automatic GitHub Actions workflow (`.github/workflows/verify.yml`) setup and alignment.
-- `brief`: Read-only scope, dependency, and size pre-briefing before speccing a run.
-- `autopilot`: Optional explicit mode for one bounded spec/plan/implement/verify/report pass.
-- `goal`: Route broad, open-ended goals before Discovery.
-- `brainstorm`: Structured divergent & convergent ideation without creating running IDs.
-- `research`: Conduct deep codebase or web research with source-backed citations.
-- `debug`: Root cause investigation before or during implementation without editing code.
-- `overview`: Refresh `devflow/context/project-overview.md`.
-- `wiki`: Knowledge base management under `devflow/wiki/`.
-- `check-for-updates`: Verify or upgrade DevFlow setup.
-- `help`: Routing and process assistance across DevFlow workflows.
-
----
-
-## Invocation Reference
-
-| Track / Category | Canonical Name | Claude / Antigravity (`/`) | OpenAI Codex (`$`) | Purpose / Action |
-| :--- | :--- | :--- | :--- | :--- |
-| **Fast: Feature** | `feature` | `/feature` | `$feature` | 4-step Fast-Track spec & living spec creation for new features (supports `IDEA-xxx`) |
-| **Fast: Fix** | `fix` | `/fix` | `$fix` | 4-step Fast-Track spec & living spec creation for bug fixes (supports `IDEA-xxx`) |
-| **Fast: Implement** | `implement` | `/implement` | `$implement` | Fast-Track incremental execution with TDD |
-| **Fast: Check** | `check` | `/check` | `$check` | Fast-Track QA review & multi-lane verification |
-| **Fast: Complete** | `complete` | `/complete` | `$complete` | Fast-Track safety pass, release digest & git merge |
-| **Idea Capture** | `idea` | `/idea` | `$idea` | Quick idea capture and AI feasibility enrichment |
-| **HTML Report** | `report-html` | `/report:html` | `$report:html` | Standalone interactive HTML dashboard generator |
-| **Deep: 00** | `00-discover` | `/00-discover` | `$00-discover` | Explore request and decide Proceed, Defer, or Reject |
-| **Deep: 10** | `10-define` | `/10-define` | `$10-define` | Turn approved discovery into bounded delivery run(s) |
-| **Deep: 20** | `20-spec` | `/20-spec` | `$20-spec` | Formal markdown delivery contract & acceptance criteria |
-| **Deep: 30** | `30-plan` | `/30-plan` | `$30-plan` | Breakdown spec into executable tasks with test decisions |
-| **Deep: 40** | `40-execute` | `/40-execute` | `$40-execute` | Execute planned tasks in small reviewable increments (`40-execute.md`) |
-| **Deep: 50** | `50-verify` | `/50-verify` | `$50-verify` | Senior QA review & multi-lane verification checks |
-| **Deep: 60** | `60-report` | `/60-report` | `$60-report` | Standalone markdown summary report |
-| **Deep: 70** | `70-release` | `/70-release` | `$70-release` | Package for delivery, git merge, PR, or deployment |
-| **Router** | `devflow` | `/devflow` | `$devflow` | Interactive guide, state inspector, and intent router |
-
 ## Commands
 
 - Dev Server: `npm run dev`