@jakkrichm/create-nexus-devflow 2.6.2 → 2.8.0

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

@@ -9,14 +9,14 @@ Use this skill to guide the user on what to do next, inspect current workspace s
 
 ## Input
 
-- **No argument (`devflow`, `/devflow`, `$devflow`, or `status`)**: Inspect current workspace state (active run in `devflow/context/current-stage.md`, active living spec in `devflow/context/current-feature.md`, active discovery in `devflow/discoveries/`, pending ideas in `devflow/ideas.md`, open findings in `devflow/context/findings.md`, and project overview in `devflow/context/project-overview.md`) and recommend the exact next action.
+- **No argument (`devflow`, `/devflow`, `$devflow`, or `status`)**: Inspect current workspace state (active tasks in `devflow/context/{xxx-slug}/`, active discovery in `devflow/discoveries/`, pending ideas in `devflow/ideas.md`, and project overview in `devflow/context/project-overview.md`) and recommend the exact next action.
 - **With user request (`devflow "<request>"`)**: Classify the user's intent and guide them to the matching DevFlow workflow stage or companion command path.
 
-## The Unified Living Spec Architecture (DevFlow 2.5.0)
+## The Task-Isolated Living Spec Architecture
 
-Nexus-DevFlow uses a **Single Unified Living Spec Model**:
+Nexus-DevFlow uses a **Task-Isolated Living Spec Model**:
 - **The 4-Stage Lifecycle**: `/feature` (or `/fix`) ➔ `/implement` ➔ `/check` ➔ `/complete`
-- Driven by a **Single Living Spec (`devflow/context/current-feature.md`)** that integrates architectural depth (Define, Spec, Plan, Execution Log, Multi-Lane QA, and Release Digest) into one clear living document.
+- Driven by a **Task-Isolated Living Spec (`devflow/context/{xxx-slug}/spec.md`)** that integrates architectural depth (Define, Spec, Plan, Execution Log, Multi-Lane QA, and Release Digest) into dedicated task workspaces without root bottleneck.
 - **Pre-Flight Inception Engine**: Companion skills (`/discovery`, `/idea`, `/grill`, `/brainstorm`) feed directly into `/feature`.
 
 ---
@@ -26,13 +26,13 @@ Nexus-DevFlow uses a **Single Unified Living Spec Model**:
 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 `devflow/context/current-feature.md`.
-   - If `current-feature.md` has incomplete checklist tasks (`- [ ]`) -> Recommend `/implement`.
-   - If all tasks are completed (`- [x]`) but no passing verification evidence in Section 5 -> Recommend `/check`.
-   - If verification evidence passed in Section 5 -> Recommend `/complete`.
+2. **Active Delivery Runs**: Scan `devflow/context/{xxx-slug}/` subdirectories.
+   - If active `spec.md` has incomplete checklist tasks (`- [ ]`) -> Recommend `/implement [id]`.
+   - If all tasks are completed (`- [x]`) but no passing verification evidence in Section 5 -> Recommend `/check [id]`.
+   - If verification evidence passed in Section 5 -> Recommend `/complete [id]`.
 3. **Active Discovery**: Check `devflow/discoveries/` for open discovery notes.
 4. **Pending Ideas Inbox**: Check `devflow/ideas.md`. If items exist under `## 📌 Pending Ideas`, summarize them in a **💡 Pending Ideas (Inbox)** list with their IDs (`[IDEA-xxx]`), feasibility, and mention that they can be started with `/feature IDEA-xxx` or `/discovery IDEA-xxx`.
-5. **Audit Findings Ledger**: Check `devflow/context/findings.md` for open high-severity findings.
+5. **Audit Findings Ledger**: Check `devflow/context/{xxx-slug}/findings.md` for open high-severity findings.
 
 ### Default State Recommendations
 - If no run is active and user wants to start a feature -> Recommend `/feature <name>`.
@@ -55,7 +55,7 @@ When invoked without an argument (or when determining the next step), inspect:
 | **"Execute implementation tasks"** | `implement` | `/implement` | **Core Loop**: `/implement` -> `/check` |
 | **"Run QA verification & check"** | `check` | `/check` | **Core Loop**: `/check` -> `/complete` |
 | **"Complete run & git merge"** | `complete` | `/complete` | **Core Loop**: `/complete` |
-| **"Generate HTML dashboard report"**| `report-html` | `/report:html` | **Standalone**: Converts `current-feature.md` or archive to HTML |
+| **"Generate HTML dashboard report"**| `report-html` | `/report:html` | **Standalone**: Converts living spec or archive to HTML |
 | "Setup DevFlow on fresh/new project" | `onboard` | `onboard` / `setup` | `onboard` -> `/feature` |
 | "Adopt DevFlow on existing codebase" | `adopt` | `adopt` / `bootstrap` | `adopt` -> `/feature` |
 | "Check setup health & diagnostics" | `doctor` | `doctor` / `health` | `doctor` |
@@ -72,8 +72,8 @@ When invoked without an argument (or when determining the next step), inspect:
 ## Available Skills Sitemap
 
 ### 1. Mainline Living Spec Loop (4 Steps)
-- `feature` (`/feature`, `/spec`) - Define, spec, and plan in `current-feature.md`
-- `fix` (`/fix`) - Document an ad-hoc bug or change in `current-feature.md`
+- `feature` (`/feature`, `/spec`) - Define, spec, and plan in `devflow/context/{xxx-slug}/spec.md`
+- `fix` (`/fix`) - Document an ad-hoc bug or change in `devflow/context/{xxx-slug}/spec.md`
 - `implement` (`/implement`) - Execute planned checklist tasks with TDD
 - `check` (`/check`) - Senior QA review, multi-lane verification, record evidence
 - `complete` (`/complete`) - Safety pass, release digest, git merge, close run

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

@@ -76,7 +76,7 @@ devflow/discoveries/{DISCOVERY_ID}-{slug}/discovery.md
 ### Decision & Approval Gate:
 Set one visible decision:
 - `Proceed`: Enough value and evidence exist to define delivery work:
-  - Handoff to `/feature {discovery_id}` or `/fix {discovery_id}` to create the Single Living Spec in `devflow/context/current-feature.md`.
+  - Handoff to `/feature {discovery_id}` or `/fix {discovery_id}` to create the Task-Isolated Living Spec in `devflow/context/{xxx-slug}/spec.md`.
 - `Defer`: The idea remains relevant but timing or evidence is not ready.
 - `Reject`: The idea should not proceed under current framing.
 
@@ -85,5 +85,5 @@ Set one visible decision:
 ## Next Workflow Recommendations
 
 - **From Macro Project Mode**: Run `/overview` to compile context into `devflow/context/project-overview.md`.
-- **From Micro Pre-Flight (Approved Proceed)**: Run `/feature {discovery_id}` or `/fix {discovery_id}` to start the Single Living Spec lifecycle.
+- **From Micro Pre-Flight (Approved Proceed)**: Run `/feature {discovery_id}` or `/fix {discovery_id}` to start the Task-Isolated Living Spec lifecycle.
 - **From Micro Pre-Flight (Defer / Reject)**: No next command needed.

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

@@ -30,10 +30,10 @@ Gather these, then summarize. Do not dump file contents.
 1. **Required DevFlow files**
    - Confirm `AGENTS.md`, `devflow/project-plan.md`,
      `devflow/build-plan.md`, and `devflow/context/` exist.
-   - Confirm `devflow/context/coding-standards.md`,
-     `devflow/context/ai-interaction.md`,
-     `devflow/context/current-feature.md`, and
-     `devflow/context/project-overview.md` exist.
+   - Confirm `devflow/context/project-overview.md`,
+     `devflow/context/coding-standards.md`,
+     `devflow/context/ai-interaction.md`, and
+     `devflow/context/glossary.md` exist.
    - Confirm `devflow/history/features/` and `devflow/history/fixes/` exist.
      When the rollback skill is installed, also check
      `devflow/history/rollbacks/`. A missing rollback folder on a legacy
@@ -48,6 +48,14 @@ Gather these, then summarize. Do not dump file contents.
    - If `.gitignore` marks DevFlow workflow files as local-only, still require
      the files to exist on disk. Ignored but present is healthy; ignored and
      missing means the local workflow needs to be restored.
+   - Read `devflow/config.json` when present. Missing is healthy and means
+     built-in defaults. When present, require a regular non-symbolic-link JSON
+     file with `schemaVersion: 1`. Reject unknown keys and unsupported values.
+     Report the effective workflow, git, verification, regular quality-gate,
+     Continuous quality-gate, and Continuous Mode settings. Confirm each audit,
+     check, and try-guide gate uses its supported values and defaults to `manual`.
+     An invalid config is a setup blocker for mutating workflow skills because
+     they must not guess which policy to follow.
 2. **Tool adapters**
    - Read `.nexus/nexus-devflow.json` when present and report its exact
      logical adapters: Codex, Claude Code, GitHub Copilot, Antigravity, and OpenCode.
@@ -121,16 +129,12 @@ Gather these, then summarize. Do not dump file contents.
    - If either planning file appears newer than the overview by filesystem time,
      call the overview possibly stale and suggest `/overview` before feature work.
 7. **Current workflow state**
-   - Check whether `devflow/context/current-feature.md` is the reset stub or an
-     active feature, fix, or rollback spec.
+   - Scan `devflow/context/{xxx-slug}/` for active task directories and specs.
    - If a spec is active, report checked and unchecked implementation steps.
-   - If `current-feature.md` is the reset stub but git has source or workflow
+   - If no active task directory exists in `devflow/context/` but git has source or workflow
      changes, warn that work is happening without an active spec.
    - Flag active spec on `main`, all spec steps checked but no completion, or a
-     branch that does not match `feature/`, `fix/`, or `rollback/` for the spec
-     type. For a feature, also flag a mismatch with the next unchecked
-     build-plan item. For a rollback, confirm its target is a checked item and do
-     not compare it to the next unchecked item.
+     branch that does not match `feature/{xxx-slug}`, `fix/{xxx-slug}`, or `rollback/{xxx-slug}`.
 8. **Git**
    - Report current branch, clean vs dirty working tree, rough changed-file count,
      last commit subject, and whether the branch is ahead of upstream.

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

@@ -116,9 +116,8 @@ build plan starts high-level.
 
 ## Step 3 - write the spec
 
-For the one (sub-)feature being built now, write a full spec to
-`devflow/context/current-feature.md` (create `devflow/context/` if needed), following
-`reference/feature-spec-template.md`. Fill every section:
+For the one (sub-)feature being built now, allocate sequential ID (`xxx-slug`) and create a dedicated workspace at `devflow/context/{xxx-slug}/`. Write the full living spec to
+`devflow/context/{xxx-slug}/spec.md`, following `reference/feature-spec-template.md`. Also initialize `stage.md` and `findings.md` in that folder. Fill every section:
 - Goal, Problem Statement, and In/Out of scope
 - Acceptance Criteria (AC-1, AC-2, ...)
 - Small build steps as atomic 2-5 min checklist items (`- [ ]`, supporting `[TDD-Red]`, `[TDD-Green]`, `[TDD-Refactor]` triplets for functional logic)
@@ -178,7 +177,7 @@ code exists. Run the draft against these questions:
   test when a `test` command is declared in `AGENTS.md`, UI/integration rides on
   screenshot + build?
 
-Apply the fixes to `current-feature.md`. Then stop and present the spec, leading
+Apply the fixes to `devflow/context/{xxx-slug}/spec.md`. Then stop and present the spec, leading
 with a short **"what the critique changed"** note - the splits, gaps, or scope
 cuts you made (or "nothing - the draft held up"). That note is the point: it shows
 the gate working before a line of code is written.
@@ -201,8 +200,8 @@ Tell the user to review and adjust. This skill plans; it never starts building.
 ## When a (sub-)feature is done
 
 Check its box in `build-plan.md` (and the parent item once all its sub-items are
-checked), archive the finished `devflow/context/current-feature.md` to
-`devflow/history/features/NN-name.md`, then run `/feature` again for the next one.
+checked), archive the finished `devflow/context/{xxx-slug}/spec.md` to
+`devflow/history/features/{xxx-slug}.md`, delete the run workspace `devflow/context/{xxx-slug}/`, then run `/feature` again for the next one.
 
 ## Formatting
 

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

@@ -21,14 +21,14 @@ it creates a dedicated run folder at `devflow/context/{xxx-slug}/` (e.g. `059-fi
 A description of the bug or change, for example `/fix "password reset email never
 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
+The input may also be a finding ID from `devflow/context/{xxx-slug}/findings.md` (or previous findings), alone
 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`,
 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:
+then write a short spec to `devflow/context/{xxx-slug}/spec.md`. Also initialize `stage.md` and `findings.md` in that folder. 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/implement/SKILL.md

@@ -13,7 +13,7 @@ Where this sits in the workflow:
                                         reviewed)        merge + log)
 
 `/feature`, `/fix`, or `/rollback` wrote the spec to
-`devflow/context/{xxx-slug}/spec.md` (or `devflow/context/current-feature.md`) and stopped.
+`devflow/context/{xxx-slug}/spec.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
@@ -24,11 +24,11 @@ checkpoint after each step; the work-level commit, merging, and logging are
 ## 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.
+- **With no argument** (`/implement`) -> checks current git branch matching `feature/{xxx-slug}`, or auto-picks if only 1 spec is active in `devflow/context/`, or prompts the user if multiple specs are queued.
 
 ## Before you start
 
-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
+Read the target spec from `devflow/context/{xxx-slug}/spec.md`. If it has no real spec (missing 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
@@ -45,13 +45,12 @@ feature was started earlier and interrupted (often a cleared context). The spec
 its ticked steps are files, so pick up where it left off: read which steps are done,
 check the git branch and `git status`/log to see what is committed and what is still
 in the working tree, then continue from the **first unchecked step** instead of
-starting over. No separate save/load is needed - the project instructions load
-`current-feature.md` every session.
+starting over.
 
 ## Step 1 - branch
 
-Create and check out a branch named from the spec: `feature/<name>` for a feature,
-`fix/<name>` for a fix, or `rollback/<name>` for a Type: Rollback spec. If the
+Create and check out a branch named from the spec: `feature/{xxx-slug}` for a feature,
+`fix/{xxx-slug}` for a fix, or `rollback/{xxx-slug}` for a Type: Rollback spec. If the
 project isn't a git repo yet, say so and ask the user to run `git init` first;
 the loop needs branches. On resume, the branch already exists - check it out
 instead of creating a new one.
@@ -60,7 +59,7 @@ instead of creating a new one.
 
 For a rollback spec, do not hand-delete the old feature and do not run a whole
 commit `git revert`. Completed feature commits also contain Blueprint history and
-plan bookkeeping, while `current-feature.md` now contains the active rollback
+plan bookkeeping, while `devflow/context/{xxx-slug}/spec.md` now contains the active rollback
 spec. Reversing the whole commit would damage that state.
 
 Before the first rollback build step:
@@ -133,9 +132,9 @@ Work through the spec's build steps in order, one at a time. For each step:
    Repeat until it works and the user approves. Nothing is committed until the
    user is happy with the step.
 6. **Mark it done, then prompt to move on.** Once the step is approved, check that
-   step off (`- [x]`) in `devflow/context/current-feature.md` so progress survives a context
+   step off (`- [x]`) in `devflow/context/{xxx-slug}/spec.md` so progress survives a context
    clear. If the step repaired a finding tracked in
-   `devflow/context/findings.md`, set that finding's status to `fixed` now too
+   `devflow/context/{xxx-slug}/findings.md`, set that finding's status to `fixed` now too
    and note the repair in its **Resolution** line. Never set `closed`: a repair
    is re-reviewed by `/audit` before it clears, because a fix can introduce a
    worse defect than the one it removed. Then offer a short choice, noting that checkpoints are optional since
@@ -164,12 +163,12 @@ pass before any commit.
 
 ## Step 3 - hand off to /complete
 
-Before handing off, check `devflow/context/findings.md`. A P0 or P1 finding
+Before handing off, check `devflow/context/{xxx-slug}/findings.md`. A P0 or P1 finding
 still `open` or `fixed` there means `/complete` will refuse the merge, so close
 the loop now:
 
 - Repair each `open` P0 or P1 as an extra reviewed step. First append it to the
-  spec's build steps in `current-feature.md` (`- [ ] Repair F-03 - <title>`) so
+  spec's build steps in `devflow/context/{xxx-slug}/spec.md` (`- [ ] Repair F-03 - <title>`) so
   the repair is on the record and survives a context clear, then run the same
   loop as Step 2: smallest change, diff, plain-English explanation, evidence.
   Check the step off and mark the finding `fixed` together.

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

@@ -46,7 +46,7 @@ Read:
 - `devflow/project-plan.md`
 - `devflow/build-plan.md`
 - `devflow/context/project-overview.md`
-- `devflow/context/current-feature.md`
+- `devflow/context/{xxx-slug}/spec.md` (when a task is active)
 - package or build files such as `package.json`, lockfiles, framework config,
   Dockerfile, `render.yaml`, `vercel.json`, `.env.example`, and README files
 - git branch and working tree status

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 current-feature.md or history archives on demand."
+description: "[devflow] Standalone HTML Report Generator - render an interactive standalone HTML dashboard from devflow/context/{xxx-slug}/spec.md or history archives 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 `current-feature.md`, task-specific context `devflow/context/{xxx-slug}/spec.md`, or archived history files in `devflow/history/`.
+Standalone companion command to generate an interactive, self-contained HTML report dashboard on demand from 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`). Use this command whenever you or stakeholders wish to view or share an interactive web report.
@@ -26,7 +26,7 @@ When invoked:
 
 ### 1. Identify Target Run
 1. Locate target markdown document:
-   - Active Living Spec: `devflow/context/current-feature.md` or `devflow/context/{xxx-slug}/spec.md`
+   - Active Living Spec: `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.
 

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

@@ -1,6 +1,6 @@
 ---
 name: rollback
-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."
+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/{xxx-slug}/spec.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
@@ -33,14 +33,12 @@ the feature was removed.
 
 ## Step 0 - preflight
 
-Read `AGENTS.md`, `devflow/build-plan.md`,
-`devflow/context/current-feature.md`, the completed feature archives, and git
+Read `AGENTS.md`, `devflow/build-plan.md`, the completed feature archives, and git
 state.
 
 Stop before writing when:
 
 - the directory is not a git repository
-- `current-feature.md` already holds active work
 - the working tree is dirty, including unrelated untracked work
 - the current branch is not the local main or default branch
 - the target is not a checked build-plan feature with a matching archive
@@ -107,8 +105,8 @@ remediation or explicitly plan the dependent rollbacks.
 
 ## Step 4 - write the rollback spec
 
-Write `devflow/context/current-feature.md` using
-`reference/rollback-spec-template.md`. Fill in:
+Allocate sequential ID (`xxx-slug`) and create `devflow/context/{xxx-slug}/`. Write `devflow/context/{xxx-slug}/spec.md` using
+`reference/rollback-spec-template.md`. Also initialize `stage.md` and `findings.md` in that folder. Fill in:
 
 - target feature, archive, exact commit, and parent commit
 - user's reason

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

@@ -34,14 +34,13 @@ state.
 1. **Build plan** - `devflow/build-plan.md`. Count checked vs unchecked leaf
    items. Name the next unchecked leaf, the same target `/feature` would pick,
    and note if a parent item was split into sub-items (`4a`, `4b`, ...).
-2. **Current work** - `devflow/context/current-feature.md`. Is something in
-   progress, or is it the reset stub? If a feature, fix, or rollback spec is
-   present, report its type and name, which build steps are checked, and the
-   first unchecked step where `/implement` resumes.
-3. **Findings** - `devflow/context/findings.md`. Count findings by status and
+2. **Current work & Spec Queue** - scan `devflow/context/{xxx-slug}/`. Is something in
+   progress? If a feature, fix, or rollback spec is
+   present, report its type, name, running ID, which build steps are checked, and the
+   first unchecked step where `/implement` resumes. If multiple tasks are queued, list the active spec queue.
+3. **Findings** - `devflow/context/{xxx-slug}/findings.md`. Count findings by status and
    report open and fixed counts next to build-plan progress. Call out any P0 or
-   P1 still `open` or `fixed` by ID, since those block `/complete`. A missing
-   file means no findings.
+   P1 still `open` or `fixed` by ID, since those block `/complete`.
 4. **Overview freshness** - if `devflow/context/project-overview.md` is missing,
    or if `project-plan.md` or `build-plan.md` appears newer than it by filesystem
    time, mention that `/overview` should run before new feature work.
@@ -49,38 +48,32 @@ state.
    changes, roughly how many files changed, last commit subject, and whether the
    branch is ahead of its remote. If the directory is not a git repo, say so and
    skip this part rather than failing.
-6. **Progress drift** - flag active spec on `main`, a spec in progress but no
-   matching `feature/`, `fix/`, or `rollback/` branch, all spec steps checked but
-   not completed, or disagreement between `build-plan.md` and
-   `current-feature.md`. A rollback legitimately targets a checked build-plan
-   item until `/complete` unchecks it, so do not compare it to the next unchecked
-   feature.
+6. **Progress drift** - flag active task on `main`, a spec in progress but no
+   matching `feature/{xxx-slug}`, `fix/{xxx-slug}`, or `rollback/{xxx-slug}` branch, all spec steps checked but
+   not completed, or disagreement between `build-plan.md` and active specs.
 
 ## Output
 
 A short, scannable summary, not a wall of text. Aim for something like:
 
-    Status: Building feature 4 - PDF export
-    Plans: Overview current. Build plan 3 of 9 complete.
-    Current work: Step 2 of 3 done. Next step: Download PDF button.
-    Findings: 1 open P2 (F-04), 1 fixed P1 awaiting re-review (F-02).
-    Git: branch feature/pdf-export, 3 uncommitted files, last commit "feat: widen export helper".
-    Watch: F-02 is fixed but not re-reviewed; it blocks /complete until /audit closes it.
+    Status: Building feature 061 - Pure Multi-Run Architecture
+    Plans: Overview current. Build plan 13 of 14 complete.
+    Current work: Step 2 of 4 done. Next step: Update Directives & Documentation.
+    Findings: 0 blockers in 061-pure-multi-run-task-isolated-architecture/findings.md.
+    Git: branch feature/061-pure-multi-run-task-isolated-architecture, 3 uncommitted files.
 
-    Next action: run /implement for Step 3.
+    Next action: run /implement 061 for Task 2.
 
 End with a single suggested next action, chosen in this order:
 
 - The overview is missing or stale and no feature is in progress -> `/overview`.
-- A spec is in progress with unchecked steps -> `/implement` and name the step.
-- A spec is in progress and all implementation steps are checked -> `/check` if
+- A spec is in progress with unchecked steps -> `/implement [id]` and name the step.
+- A spec is in progress and all implementation steps are checked -> `/check [id]` if
   proof is not recorded, `/try` if the user wants a manual review path,
-  `/implement` when a P0 or P1 finding is still `open` (the repair is an extra
+  `/implement [id]` when a P0 or P1 finding is still `open` (the repair is an extra
   reviewed step), `/audit` when one is `fixed` and awaiting re-review (both
-  block `/complete`), otherwise `/complete`.
-- `current-feature.md` is the reset stub and a P0 or P1 finding is `open` ->
-  `/fix <finding id>`; when one is `fixed`, `/audit` to re-review and close it.
-- `current-feature.md` is the reset stub and unchecked build-plan items remain ->
+  block `/complete`), otherwise `/complete [id]`.
+- No active tasks in `devflow/context/` and unchecked build-plan items remain ->
   `/feature` and name the next build-plan item.
 - All build-plan items are checked -> say the current milestone is complete;
   suggest hardening, release, or docs when appropriate, or

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

@@ -23,10 +23,10 @@ merge, push, or run destructive commands.
 Optional scope:
 
 - no argument: use the active feature, fix, or rollback in
-  `devflow/context/current-feature.md`
+  `devflow/context/{xxx-slug}/spec.md`
 - `latest`: use the most recent archive under `devflow/history/features/`,
   `devflow/history/fixes/`, or `devflow/history/rollbacks/`
-- a step name or number: focus the guide on that current-feature step
+- a step name or number: focus the guide on that active step
 - a path, route, or command: include it as the main thing to try
 
 If there is no active feature and no useful archive, ask what change the user
@@ -37,16 +37,15 @@ wants to try instead of guessing.
 Read:
 
 - `AGENTS.md`
-- `devflow/context/current-feature.md`
+- `devflow/context/{xxx-slug}/spec.md` (or active task workspace)
 - `devflow/context/project-overview.md`
 - `devflow/context/coding-standards.md`
 - `devflow/build-plan.md`
 - latest files under `devflow/history/features/`,
-  `devflow/history/fixes/`, and `devflow/history/rollbacks/`, if the current
-  feature is reset
+  `devflow/history/fixes/`, and `devflow/history/rollbacks/`, if no task is active
 - git branch and working tree status
 
-Prefer the active spec. If `current-feature.md` is the reset stub, use the most
+Prefer the active task spec. If no active task directory exists, use the most
 recent archived feature, fix, or rollback by filename or modification time and
 say that is what you used.
 

package/template/AGENTS.md

@@ -1,24 +1,30 @@
-# Nexus-DevFlow 2.6.2 (The 3-Pillars & Single Living Spec Model)
+# Nexus-DevFlow (The 3-Pillars & Pure Task-Isolated 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.
 
 ## What this is
 
-This project uses **Nexus-DevFlow**, an agentic workflow layer supporting **The 3-Pillars Workspace Architecture & Single Living Spec Model**:
-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` Single Living Spec).
+This project uses **Nexus-DevFlow**, an agentic workflow layer supporting **The 3-Pillars Workspace Architecture & Pure Task-Isolated Living Spec Model**:
+1. **🔮 Future (Backlog)**: `devflow/ideas.md`, `devflow/project-plan.md`, `devflow/build-plan.md` — Centralized Idea Inbox & Master Build Plan.
+2. **⚡ Present (Active Context)**: `devflow/context/` — Global Shared Source of Truth (`project-overview.md`, `coding-standards.md`, `ai-interaction.md`, `glossary.md`) & Active Task Workspaces (`devflow/context/{xxx-slug}/`).
 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.
 
 ## Read these for full context
 
+- `devflow/config.json` - deterministic project workflow settings
 - `devflow/context/project-overview.md` - the project's source of truth
 - `devflow/context/coding-standards.md` - engineering conventions & rules to follow
 - `devflow/context/ai-interaction.md` - how to interact with the user on this project
-- `devflow/context/current-stage.md` - active discovery or running delivery state
-- `devflow/context/findings.md` - quality, security, and verification ledger
 - `devflow/context/glossary.md` - domain terms & architecture definitions
+- `devflow/context/{xxx-slug}/` - active task living spec, stage, and findings ledger
+
+## Project configuration
+
+`devflow/config.json` is the user-owned, machine-readable workflow policy for this project. Workflow skills read the relevant settings before acting. A missing file means built-in defaults. An invalid file falls back to defaults for read-only status reporting, but mutating workflow commands stop and point to `/doctor` instead of guessing.
+
+`qualityGates.regular` controls automatic audit, check, and try-guide behavior for the normal workflow and Autopilot. `qualityGates.continuous` controls the same per-feature gates for Continuous Mode. Every gate defaults to `manual`.
 
 ## Tool-Specific Adapters & Execution Rules
 
@@ -32,34 +38,34 @@ Unused adapter families can be removed. Codex, Antigravity, GitHub Copilot, and
 
 ### Universal Invocation & Agent Directives:
 
-1. **Canonical Command Names & AI Provider Invocation**: Each workflow stage and companion tool has exactly **one Canonical Name** (e.g. `feature`, `fix`, `implement`, `check`, `complete`, `discovery`, `idea`, `grill`, `brainstorm`, `devflow`, `doctor`, `overview`, `debug`, `onboard`, `adopt`, `try`, `rollback`, `ci`, `test`, `tests`, `autopilot`, `prototype`, `report-html`, `brief`, `audit`, `release`). The way you invoke commands depends on your AI Provider / Tool:
-   - **Canonical Name (Plain text)**: Directly invoke or prompt the command by its standard name (e.g., `feature`, `implement`, `devflow`, `discovery`).
-   - **Slash Prefix (`/`)**: For tools supporting slash commands (Claude Code, Google Antigravity, Gemini CLI), e.g., `/feature`, `/fix`, `/implement`, `/devflow`, `/discovery`.
-   - **Dollar Prefix (`$`)**: For OpenAI Codex CLI or skill-invocation tools, e.g., `$feature`, `$fix`, `$devflow`, `$discovery`.
+1. **Canonical Command Names & AI Provider Invocation**: Each workflow stage and companion tool has exactly **one Canonical Name** (e.g. `feature`, `fix`, `implement`, `check`, `complete`, `continuous`, `discovery`, `idea`, `grill`, `brainstorm`, `devflow`, `doctor`, `overview`, `debug`, `onboard`, `adopt`, `try`, `rollback`, `ci`, `test`, `tests`, `autopilot`, `prototype`, `report-html`, `brief`, `audit`, `release`, `convert-any-to-md`). The way you invoke commands depends on your AI Provider / Tool:
+   - **Canonical Name (Plain text)**: Directly invoke or prompt the command by its standard name (e.g., `feature`, `implement`, `continuous`, `devflow`, `discovery`).
+   - **Slash Prefix (`/`)**: For tools supporting slash commands (Claude Code, Google Antigravity, Gemini CLI), e.g., `/feature`, `/fix`, `/implement`, `/continuous`, `/devflow`, `/discovery`.
+   - **Dollar Prefix (`$`)**: For OpenAI Codex CLI or skill-invocation tools, e.g., `$feature`, `$fix`, `$continuous`, `$devflow`, `$discovery`.
 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 context in `devflow/context/`.
-5. **Default Artifact & Communication Language (Thai)**: All generated markdown stage artifacts (`current-feature.md`, `discovery.md`, etc.) 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 active task directories in `devflow/context/{xxx-slug}/`, `devflow/discoveries/`, and `devflow/ideas.md`.
+5. **Default Artifact & Communication Language (Thai)**: All generated markdown stage artifacts (`spec.md`, `discovery.md`, etc.) and user communication MUST default to **Thai (`th`)**, while code, technical terms, file paths, and identifiers remain in English.
 
 ---
 
-## ⚡ The Unified 4-Stage Living Spec Lifecycle
+## ⚡ The Unified 4-Stage Task-Isolated Living Spec Lifecycle
 
-All development tasks (from lean UI fixes to deep architectural epics) execute through the 4-step progressive lifecycle:
+All development tasks execute through the 4-step progressive lifecycle:
 
 ```text
 /feature (หรือ /fix) ──▶ /implement ──▶ /check ──▶ /complete
 ```
 
-1. **`feature` / `fix` (`/feature`, `/fix`, `/spec`)**:
-   - **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`)** with 6 structured sections.
-   - **Artifact**: `devflow/context/current-feature.md`
-2. **`implement` (`/implement`)**:
-   - **Purpose**: Incrementally executes checklist tasks with TDD discipline (Red-Green-Refactor) and appends diff evidence to `current-feature.md`.
-3. **`check` (`/check`)**:
-   - **Purpose**: Senior QA review, multi-lane verification matrix (Typecheck, Lint, Test suites, manual proof), and records empirical proof into `current-feature.md`.
-4. **`complete` (`/complete`)**:
-   - **Purpose**: Final safety pass, records Release Digest, automatically archives to `devflow/history/{features|fixes|rollbacks}/{xxx-slug}.md`, resets the stub, and performs git squash-merge.
+1. **`feature` / `fix` (`/feature`, `/fix`)**:
+   - **Purpose**: Combines Discover, Define, Spec, and Plan into one unified step. Allocates sequential ID (`xxx-slug`) and initializes the **Task-Isolated Living Spec (`devflow/context/{xxx-slug}/spec.md`)**, stage pointer (`stage.md`), and dedicated audit ledger (`findings.md`).
+   - **Artifact**: `devflow/context/{xxx-slug}/spec.md`
+2. **`implement` (`/implement [id]`)**:
+   - **Purpose**: Checks out `feature/{xxx-slug}` (or auto-detects from branch), incrementally executes checklist tasks in `devflow/context/{xxx-slug}/spec.md` with TDD discipline (Red-Green-Refactor), and appends diff evidence.
+3. **`check` (`/check [id]`)**:
+   - **Purpose**: Senior QA review, multi-lane verification matrix (Typecheck, Lint, Test suites, manual proof), and records empirical proof into `devflow/context/{xxx-slug}/spec.md` and findings into `findings.md`.
+4. **`complete` (`/complete [id]`)**:
+   - **Purpose**: Final safety pass, records Release Digest, automatically archives to `devflow/history/{features|fixes|rollbacks}/{xxx-slug}.md`, cleanly removes `devflow/context/{xxx-slug}/`, updates `HISTORY.md` and `build-plan.md`, and performs git squash-merge.
 
 ---
 

package/template/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 Nexus-DevFlow contributors
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 Nexus-DevFlow contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/template/devflow/build-plan.md

@@ -99,3 +99,21 @@
 - [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 ให้เป็นปัจจุบันสมบูรณ์
+
+---
+
+## 🔄 Phase 13: Upstream AI Blueprint v0.14.0 Synchronization & Deterministic Config Engine
+
+- [x] **13. Sync Upstream v0.14.0 (Deterministic Config & Continuous Mode)** `[Size: M]`
+  - *Dependencies*: Feature 12, DISC-20260826-003
+  - *Scope*: นำระบบ Deterministic Project Configuration (`devflow/config.json`) และสคิล Autonomous Multi-Feature Loop (`/continuous`) เข้าสู่ Nexus-DevFlow พร้อมอัปเกรด `project-config.ts`, `doctor`, `status`, `dashboard` และอัปเดต upstream baseline tracking สู่ v0.14.0
+
+---
+
+## ⚡ Phase 14: Pure Multi-Run Task-Isolated Architecture
+
+- [x] **14. Pure Multi-Run Task-Isolated Architecture (`DISC-20260826-004`)** `[Size: M]`
+  - *Dependencies*: Feature 11, Feature 12, Feature 13
+  - *Scope*: ยกเลิกไฟล์ Single Living Spec ที่ Root (`current-feature.md`, `current-stage.md`, `findings.md`) อย่างสมบูรณ์ ปรับโครงสร้างสู่ Task-Isolated Subdirectories 100% (`devflow/context/{xxx-slug}/`), อัปเกรด Agent Directives, Core Context Resolver, Scaffolding Templates และ Workflow Skills ทั้งหมด
+
+