@jakkrichm/create-nexus-devflow 2.0.15 → 2.0.18

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

@@ -1,6 +1,6 @@
 ---
 name: deploy
-description: "[Devflow] Production deployment pre-flight checks, launch readiness, smoke validation, and deployment execution."
+description: "[Devflow] Production deployment pre-flight checks, smoke validation, and deployment execution."
 ---
 
 # Production Deployment & Launch Readiness

package/template/.agents/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/.agents/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/.agents/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/.agents/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/.agents/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/.agents/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/.agents/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/.agents/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/.agents/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/.agents/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/.agents/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/.claude/skills/00-discover/SKILL.md

@@ -1,5 +1,5 @@
----name: 00-discover
-
+---
+name: 00-discover
 description: "[Devflow] Discover stage in DevFlow 2.0 - explore a request, route supporting inquiry, and decide whether delivery work should begin without allocating a running ID."
 argument-hint: "{title, request, or discovery-id}"
 ---

package/template/.claude/skills/10-define/SKILL.md

@@ -1,6 +1,6 @@
----name: 10-define
-
-description: "[Devflow] Define stage in DevFlow 2.0 - turn an approved discovery into one or more bounded delivery runs with stable scope."
+---
+name: 10-define
+description: "[Devflow] Define stage in DevFlow 2.0 - turn an approved discovery into a bounded delivery run in context/current-run with stable scope."
 argument-hint: "{approved discovery-id, discovery path, running-id, or run path}"
 ---
 
@@ -8,23 +8,21 @@ argument-hint: "{approved discovery-id, discovery path, running-id, or run path}
 
 $ARGUMENTS
 
-Convert an approved `Proceed` discovery into bounded delivery slices. Allocate one Running ID per independently specifiable and reviewable slice, then write one `10-define.md` contract per generated run. This is the first stage that creates Running IDs.
+Convert an approved `Proceed` discovery into a bounded delivery run. Checks the Single Active Run Guardrail, allocates a sequential ID without prefix (`xxx-slug`), and writes `devflow/context/current-run/10-define.md`.
 
 ## Usage
 
 ```text
 10-define {discovery-id or discovery path}
-10-define {running-id or run path}
+10-define {id or run path}
 ```
 
-Use a Discovery ID to materialize new delivery runs. Use an existing Running ID only to revise or split a definition that already exists.
-
 ## Markdown-First Contract
 
-For every approved delivery slice, write:
+For the active delivery run, write:
 
 ```text
-devflow/runs/{ID}-{slug}10-define.md
+devflow/context/current-run/10-define.md
 ```
 
 using:
@@ -33,138 +31,24 @@ using:
 .agent/resources/schemas/define.template.md
 ```
 
-Before writing any `10-define.md`, read `artifact_language` from `define.template.md` and produce every generated artifact in that language.
-
-## Required Section Content
-
-Before completing any generated artifact:
-
-- preserve every heading required by the selected template
-- write concrete information under every heading
-- when no information exists or the section does not apply, write exactly `-`
-- never leave a heading immediately followed by another heading with no body content
-- remove template placeholders from the final artifact
-- do not invent facts merely to avoid using `-`
-- re-read the saved artifact and verify every heading satisfies this rule
-
-## Process
-
-### Loop Contract
-
-Run definition as a scope-stabilization and run-allocation loop.
-
-- **Intent**: turn an approved discovery into the smallest coherent set of delivery runs that can each be specified, planned, implemented, and verified without carrying the entire initiative context.
-- **Context**: read the approved `00-discover.md`, linked Brainstorm/PRD/Research/Debug outputs, project-wide rules, existing run IDs, and dependencies between candidate slices.
-- **Action**: lock initiative and scope boundaries, decompose delivery slices, review the run map, allocate collision-free Running IDs, and write one `10-define.md` per slice.
-- **Observation**: use independent acceptance boundaries, release boundaries, ownership, dependencies, context size, cross-domain coupling, and reviewability as evidence for splitting or combining slices.
-- **Adjustment**: merge slices that are only implementation tasks; split slices that require separate specs, releases, ownership, or large independent context; return to `00-discover` if the decision or product direction is still unstable.
-- **Stop Condition**: stop when the run map is approved, IDs are materialized without collision, each run has stable in/out scope, and every generated run can proceed independently to `20-spec {running_id}`.
-- **Handoff**: each `10-define.md` must identify its source Discovery ID, sibling runs, dependencies, scope, non-goals, and exact next command.
-
-### 1. Validate The Discovery Gate
+## Process & Quality Gates
 
-For new delivery work, require:
+### 1. Single Active Run Guardrail (One Thing at a Time)
+1. Inspect `devflow/context/current-stage.md`, `devflow/context/current-feature.md`, and `devflow/context/current-run/`.
+2. If an active uncompleted run exists:
+   - **HALT and reject opening a new define stage**.
+   - Warn the user to complete or close the active run with `/complete` or `70-release` first.
 
+### 2. Validate The Discovery Gate
+Require:
 - `Decision: Proceed`
 - `Approval Status: Approved`
-- a resolvable Discovery ID and `00-discover.md`
-
-If either gate is missing, do not create a Running ID. Return to `00-discover {discovery_id}`.
-
-### 2. Build The Delivery Run Map
-
-Define candidate slices around coherent delivery outcomes, not small tasks.
-
-Create separate runs when work has materially independent:
-
-- acceptance or verification boundaries
-- release or rollback boundaries
-- domain context or ownership
-- dependency sequencing
-- implementation context large enough to threaten reliable planning or review
-
-Keep ordinary subtasks inside `30-plan` and checklists.
-
-For every slice record:
-
-- title and slug
-- outcome and scope boundary
-- exclusions
-- dependencies
-- shared project constraints
-- reason it deserves one Running ID
-
-### 3. Review Before Allocation
-
-Present the proposed run map for human review before consuming numeric IDs when the split is large, disputed, or high risk. A single clear slice may proceed directly when approval is already explicit.
-
-### 4. Allocate Running IDs
-
-- inspect `devflow/runs/` immediately before allocation
-- choose sequential IDs after the highest existing numeric Running ID
-- never reuse a gap merely because it is available
-- create each target directory immediately to reserve it
-- recheck for collisions before writing artifacts
-- if any collision occurs, stop, rescan, and allocate a fresh contiguous range
-
-One invocation may create one or many Running IDs. Record the complete allocation back into the source discovery's `related_runs` and allocated-run section.
-
-### 5. Write One `10-define.md` Per Run
-
-- preserve template headings
-- set `source_discovery`
-- identify sibling runs and dependencies
-- carry forward only the project context needed by this slice
-- make scope, non-goals, assumptions, and success criteria explicit
-- keep implementation tasks out of Define
-
-### 6. Split An Existing Run When Necessary
-
-If an existing definition is too broad:
-
-- propose a replacement run map
-- preserve traceability to the original run and discovery
-- allocate new IDs only after approval
-- mark the old definition as `Superseded` and list its replacement runs
-- do not silently fork scope during `20-spec`
-
-### 7. Manual Review Gate
-
-Before recommending `20-spec`, confirm each generated definition independently. Approval of one run must not imply approval of every sibling run.
-
-## Output
-
-Report:
-
-- source Discovery ID
-- proposed and allocated run map
-- workspace path for every generated run
-- scope and dependency summary per run
-- any superseded run
-- exact `20-spec {running_id}` commands for approved runs
-
-## Relationship To DevFlow 2.0
-
-- Classification: Mainline workflow and Running ID creation boundary
-- Previous state: approved `00-discover`
-- Next state: `20-spec {running_id}` per generated run
-- Running ID lifecycle: starts here
-
-## Sources
-
-- `AGENTS.md`
-- `docs/workspace-artifacts.md`
-- `.agent/resources/schemas/define.template.md`
-
-## Next Workflow Recommendation
-
-- **Primary**: `20-spec {running_id}` for each approved run
-- **Alternatives**:
-  - `00-discover {discovery_id}` when the go/no-go decision or direction is unstable
-  - `Research {discovery_id}` when evidence still blocks a reliable split
-  - `grill-with-docs` when boundaries or terminology remain ambiguous
-
-## Nexus Event
-
-- Use `domain-modeling` when sibling runs need shared language or durable architectural decisions.
-- Use `planning-and-task-breakdown` only after the delivery boundary is stable; small tasks belong in `30-plan`, not separate Running IDs.
+- A resolvable Discovery ID and `00-discover.md`
+
+### 3. Allocate Sequential ID
+- Inspect `devflow/history/HISTORY.md` and allocate sequential ID without prefix (e.g. `022-{slug}`).
+- Create directory `devflow/context/current-run/` if it does not exist.
+- Write `devflow/context/current-run/10-define.md`.
+- Update `devflow/context/current-stage.md`:
+  - `Active Running ID`: `{ID}`
+  - `Current Stage`: `10-define (Completed -> Ready for 20-spec)`

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

@@ -1,5 +1,5 @@
----name: 20-spec
-
+---
+name: 20-spec
 description: "[Devflow] Spec stage in DevFlow 2.0 - write the formal markdown-first specification from a stable definition."
 argument-hint: "{running-id or workspace path}"
 ---

package/template/.claude/skills/30-plan/SKILL.md

@@ -1,5 +1,5 @@
----name: 30-plan
-
+---
+name: 30-plan
 description: "[Devflow] Plan stage in DevFlow 2.0 - transform 20-spec.md into an executable task breakdown with test decisions."
 ---
 # Phase 30: Plan Implementation

package/template/.claude/skills/50-verify/SKILL.md

@@ -1,5 +1,5 @@
----name: 50-verify
-
+---
+name: 50-verify
 description: "[Devflow] Verify stage in DevFlow 2.0 - perform senior QA review, record evidence, and decide pass or return-to-implement."
 ---
 # Phase 50: Verify Quality

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

@@ -1,6 +1,6 @@
 ---
 name: 60-report
-description: "[Devflow] Report stage in DevFlow 2.0 - produce standardized markdown summary report for the completed run."
+description: "[Devflow] Report stage in DevFlow 2.0 - produce standardized markdown and HTML summary report for the completed run."
 argument-hint: "{running-id or workspace path}"
 ---