@jakkrichm/create-nexus-devflow 2.0.15 → 2.0.18

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

@@ -1,6 +1,6 @@
----name: 70-release
-
-description: "[Devflow] Release stage in DevFlow 2.0 - package verified work for delivery, git merge, PR, or deployment."
+---
+name: 70-release
+description: "[Devflow] Release stage in DevFlow 2.0 - package verified work for delivery, archive run to categorized history, git merge, PR, or deployment."
 argument-hint: "{running-id or workspace path}"
 ---
 
@@ -8,26 +8,20 @@ argument-hint: "{running-id or workspace path}"
 
 $ARGUMENTS
 
-Package approved work for delivery after the report stage has captured the final verified story. This stage turns report sign-off into release-ready execution and handoff.
+Package approved work for delivery after the report stage has captured the final verified story. Archives the active run from `devflow/context/current-run/` to `devflow/history/{features|fixes|rollbacks}/{xxx-slug}/`, updates `HISTORY.md`, performs git merge, and closes the run.
 
 ## Usage
 
 ```text
-70-release {running-id or workspace path}
+70-release {id or workspace path}
 ```
 
-Use this when:
-
-- `60-report` is complete
-- the work needs release execution or a release-facing handoff packet
-- downstream stakeholders need delivery notes instead of raw implementation detail
-
 ## Markdown-First Contract
 
 Write the primary stage artifact to:
 
 ```text
-devflow/runs/{ID}-{slug}70-release.md
+devflow/context/current-run/70-release.md
 ```
 
 using:
@@ -36,142 +30,24 @@ using:
 .agent/resources/schemas/release.template.md
 ```
 
-Before writing `70-release.md`, read `artifact_language` from `release.template.md` and produce the 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 release as a readiness-packaging loop, not as a celebratory summary.
-
-- **Intent**: convert verified work into a clear release, PR, merge, deploy, or handoff packet without hiding unresolved risk.
-- **Context**: read `50-verify.md`, `50-verify-impact.md` when present, `40-execute.md`, `20-spec.md`, checklist state, and any PR, deploy, merge, or handoff notes.
-- **Action**: summarize delivered scope, user/system impact, readiness state, validation evidence, rollback or mitigation notes, and follow-up items.
-- **Observation**: use concrete evidence such as verify verdict, failed or skipped checks, impact notes, residual risks, merge/deploy constraints, and checklist status.
-- **Adjustment**: if release readiness becomes uncertain, return to `50-verify`; if fixes are required, return to `40-execute`; if context must transfer, use `handoff`.
-- **Stop Condition**: stop when the release state is explicit, evidence supports readiness, residual risks and follow-ups are named, and the next delivery or reporting route is clear.
-- **Handoff**: `70-release.md` must close the mainline run or tell the next reader what shipped, what did not ship, what evidence supports readiness, and what follow-ups remain.
+## Process & Quality Gates
 
 ### 0. Step 0 Safety Pass & Findings Ledger Gate
 
 Before packaging, merging, or releasing:
 
 1. **Findings Ledger Blockers**:
-   - ตรวจสอบ `devflow/context/findings.md`
-   - ต้องไม่มี Finding ระดับ P0 หรือ P1 ในสถานะ `open` หรือ `fixed` ค้างอยู่
-   - สถานะ `fixed` ยังคงบล็อก release เสมอจนกว่าจะผ่านการ Review ใน `50-verify` เพื่อเลื่อนเป็น `closed`
+   - Inspect `devflow/context/findings.md`.
+   - No Finding of severity `P0` or `P1` in `open` or `fixed` status is permitted.
+   - `fixed` still blocks release until reviewed and closed in `50-verify`.
 2. **2-Stage Approval Separation**:
-   - การขออนุมัติ Merge เข้า `main` หรือ `master` เป็นการอนุมัติขั้นแรก
-   - **การ Push ไปยัง Remote หรือ Deploy จะต้องขออนุมัติแยกต่างหากอย่างชัดเจน (Merge approval DOES NOT equal Push approval)**
+   - Consent to merge into `main` is strictly separate from consent to `git push` to remote or deploy.
 3. **Archive Resolved Findings**:
-   - ย้ายรายการ Findings ที่ปิดแล้ว (`closed`, `accepted`, `invalid`) ไปบันทึกในเอกสาร Release และรีเซ็ต `findings.md` ให้สะอาด
-4. **Append to Master History Ledger**:
-   - บันทึก Entry ใหม่ลงใน `devflow/history/HISTORY.md` พร้อมระบุ Running ID, Title, วันที่, Git Commit Hash / Tag, สถานะ (`Released`), และลิงก์ไปยังรายงานสรุป `60-report.md`
-
-### 1. Load Verified Context
-
-Read:
-
-- `60-report.md`
-- `50-verify.md`
-- `40-execute.md`
-- `20-spec.md`
-- `devflow/context/findings.md`
-- any PR, deploy, merge, or handoff notes already captured
-
-### 2. Package The Release Outcome
-
-Summarize:
-
-- what is being delivered
-- what changed in user or system terms
-- what state the work is in for PR, deploy, merge, or handoff
-- resolved and archived findings
-- what follow-up items remain
-
-### 3. Write `70-release.md`
-
-Keep the language understandable for someone who did not do the work.
-Follow the `artifact_language` configured in `release.template.md`.
-
-Prefer clear release-note style wording:
-
-- what was added
-- what changed
-- what was fixed
-- what is intentionally deferred
-- archived findings summary
-
-### 4. Confirm Readiness & 2-Stage Execution
-
-If release readiness changes because unresolved issues are found:
-
-- route back to `50-verify` or `40-execute`
-
-Do not package unfinished work as release-ready through wording tricks.
-When executing git operations:
-1. Obtain explicit user confirmation before merging.
-2. Obtain separate explicit user confirmation before running `git push` or deployment.
-
-### 5. Manual Review Soft Gate
-
-Before closing the mainline run, warn when release approval is still pending.
-If release blockers, operator questions, or handoff approvals remain open:
-
-- mark them visibly in `70-release.md`
-- recommend human confirmation before closing the phase
-- keep the mainline closeout as a soft recommendation only
-
-## Output
-
-Report:
-
-- delivered scope
-- release, PR, merge, deploy, or handoff state
-- follow-up items
-- recommended next step
-
-## Relationship To DevFlow 2.0
-
-- Classification: Mainline workflow
-- Previous state: `60-report`
-- Next state: End of the mainline run when release packaging or handoff is complete
-- Common companion commands: `Commit`, `PR`, `Deploy`, `Changelog`, `Merge`, `Wiki`, `overview`
-- Support skills: `resolving-merge-conflicts`, `handoff`, and `setup-pre-commit` when release packaging needs conflict resolution, transfer notes, or local quality gates
-
-## Sources
-
-- `AGENTS.md`
-- `docs/workspace-artifacts.md`
-- `.agent/resources/schemas/release.template.md`
-- Related commands: `60-report`, `Commit`, `PR`, `Deploy`, `Changelog`, `Merge`, `Wiki`, `overview`
-
-## Next Workflow Recommendation
-
-- **Primary**: End of Timeline flow (or run `/overview` to sync living project context)
-- **Why**: The report is already complete, and this phase is the final release-facing execution step.
-- **Alternatives**:
-  - `overview` - choose this to immediately sync newly shipped capabilities into `devflow/context/project-overview.md`.
-  - `60-report` - choose this when the release package diverges from the approved report and the summary must be refreshed first.
-  - `50-verify` - choose this when release readiness becomes uncertain.
-  - `40-execute` - choose this when additional fixes are needed before release can proceed.
-  - `handoff` - choose this when release-ready context must move to another session, agent, or stakeholder packet.
-
-## Nexus Event
-
-- Use `Commit`, `PR`, `Deploy`, `Merge`, `Changelog`, or `overview` when release execution still needs a concrete lane.
-- Return to `60-report` when release notes, scope, or handoff wording diverge from the approved summary.
-- Return to `50-verify` or `40-execute` when release readiness changes because unresolved issues are discovered.
-
+   - Move resolved findings (`closed`, `accepted`, `invalid`) into release archive notes and clean `findings.md`.
+4. **Archive Run Folder to Categorized History**:
+   - Determine Category (`features`, `fixes`, `rollbacks`).
+   - Move directory `devflow/context/current-run/` (or `devflow/runs/{xxx-slug}/`) ➔ `devflow/history/{category}/{xxx-slug}/`.
+5. **Append to Master History Ledger**:
+   - Append entry to `devflow/history/HISTORY.md` linking to `history/{category}/{xxx-slug}/60-report.md`.
+6. **Update Workspace State**:
+   - Set `devflow/context/current-stage.md` to `Idle`.

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

@@ -1,6 +1,6 @@
 ---
 name: check
-description: "[Devflow] Fast-Track Check stage in DevFlow (Blueprint Mode) - perform senior QA review, run multi-lane verification, and record evidence in spec.md."
+description: "[Devflow] Fast-Track Check stage in DevFlow (Blueprint Mode) - perform senior QA review, run multi-lane verification, and record evidence in current-feature.md in context."
 argument-hint: "{running-id or workspace path}"
 ---
 
@@ -8,18 +8,18 @@ argument-hint: "{running-id or workspace path}"
 
 $ARGUMENTS
 
-Quality assurance and multi-lane verification stage in Fast-Track. Validates the implementation against Acceptance Criteria, runs test suites, checks for regressions, and records evidence in the Single Living Spec (`spec.md`).
+Quality assurance and multi-lane verification stage in Fast-Track. Validates the implementation against Acceptance Criteria, runs test suites, checks for regressions, and records evidence in the Single Living Spec (`devflow/context/current-feature.md`).
 
 ## Invocations & Aliases
 
 - `/check`: Run verification on current active run
-- `/check {running-id}`: Run verification on specified running ID
+- `/check {id}`: Run verification on specified ID
 - `$check`: Codex CLI invocation
 
 ## Fast-Track Mainline Workflow
 
 ```text
-/spec ──▶ /implement ──▶ /check ──▶ /complete
+/feature (หรือ /fix) ──▶ /implement ──▶ /check ──▶ /complete
 ```
 
 ## Behavior & Contract
@@ -27,8 +27,8 @@ Quality assurance and multi-lane verification stage in Fast-Track. Validates the
 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 `## 1. Specification & Scope` (Acceptance Criteria) and `## 3. Implementation Checklist`.
 
 ### 2. Multi-lane Verification Execution
@@ -41,8 +41,8 @@ Execute the verification gates across all lanes:
    - Verify specific scenarios against Acceptance Criteria (`AC-1`, `AC-2`).
    - Summarize "Where to go", "What to click/call", and "What to expect".
 
-### 3. Update Living Spec (`spec.md`)
-Append or update `## 5. Verification Evidence` in `spec.md` in **Thai (`th`)**:
+### 3. Update Living Spec (`current-feature.md`)
+Append or update `## 5. Verification Evidence` in `devflow/context/current-feature.md` in **Thai (`th`)**:
 
 ```markdown
 ## 5. Verification Evidence
@@ -64,5 +64,5 @@ Update `devflow/context/current-stage.md`:
 ### 5. Output Summary & Next Step
 Report to the user:
 - Summary of verification results across all lanes
-- Evidence recorded in `spec.md`
-- **Next Command**: `/complete` (or `/complete {RUNNING_ID}`)
+- Evidence recorded in `devflow/context/current-feature.md`
+- **Next Command**: `/complete` (or `/complete {ID}`)

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

@@ -1,6 +1,6 @@
 ---
 name: ci
-description: "[Devflow] CI/CD pipeline automation and GitHub Actions setup (.github/workflows/verify.yml). Automates quality gates, typechecks, tests, and build checks."
+description: "[Devflow] Set up automated GitHub Actions CI workflow (.github/workflows/verify.yml) aligned with project verify command."
 ---
 
 # CI/CD Pipeline Automation & Quality Gates

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

@@ -1,6 +1,6 @@
 ---
 name: complete
-description: "[Devflow] Fast-Track Complete stage in DevFlow (Blueprint Mode) - perform final safety pass, record release digest in spec.md, git merge, and close run without auto HTML generation."
+description: "[Devflow] Fast-Track Complete stage in DevFlow (Blueprint Mode) - final safety pass, archive living spec into categorized history, reset stub, git merge, and close run."
 argument-hint: "{running-id or workspace path}"
 ---
 
@@ -8,18 +8,18 @@ argument-hint: "{running-id or workspace path}"
 
 $ARGUMENTS
 
-Final delivery, safety pass, and run closure stage in Fast-Track. Validates verification status, records the Release Digest into `spec.md`, performs git merge, and marks the run as completed **without auto-generating HTML reports**.
+Final delivery, safety pass, archive, and run closure stage in Fast-Track. Validates verification status, archives `devflow/context/current-feature.md` to `devflow/history/{features|fixes|rollbacks}/{xxx-slug}.md`, resets the stub, performs git merge, and closes the run **without auto-generating HTML reports**.
 
 ## Invocations & Aliases
 
 - `/complete`: Complete current active run
-- `/complete {running-id}`: Complete specified running ID
+- `/complete {id}`: Complete specified ID
 - `$complete`: Codex CLI invocation
 
 ## Fast-Track Mainline Workflow
 
 ```text
-/spec ──▶ /implement ──▶ /check ──▶ /complete
+/feature (หรือ /fix) ──▶ /implement ──▶ /check ──▶ /complete
 ```
 
 ## Behavior & Contract
@@ -27,47 +27,68 @@ Final delivery, safety pass, and run closure stage in Fast-Track. Validates veri
 When invoked:
 
 ### 1. Validate Delivery Pre-conditions
-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. Confirm:
+   - File contains an active spec (not the idle stub `_Nothing in progress._`).
    - All checklist items in `## 3. Implementation Checklist` are marked `- [x]`.
-   - `## 5. Verification Evidence` contains passing verification results.
+   - `## 5. Verification Evidence` contains passing verification results and empirical command outputs.
 
-### 2. Final Safety Pass & Changelog
+### 2. Final Safety Pass & Findings Check
 1. Verify working directory hygiene (no accidental leftover test files or debug statements).
-2. Update `CHANGELOG.md` with release summary under the current version if applicable.
-
-### 3. Update Living Spec (`spec.md`)
-Append or update `## 6. Release & Handoff` in `spec.md` in **Thai (`th`)**:
-
+2. Inspect `devflow/context/findings.md`:
+   - No `P0` or `P1` finding is in `open` or `fixed` status (`fixed` requires re-audit).
+   - Only `closed`, `accepted` (user waived), or `invalid` findings are permitted for completion.
+
+### 3. Update Living Spec & Archive to Categorized History
+1. Append `## 6. Release & Handoff` in `current-feature.md` in **Thai (`th`)**:
+   ```markdown
+   ## 6. Release & Handoff
+   - **Release Digest**: สรุปสิ่งที่ส่งมอบในรอบนี้
+   - **Git Branch**: `{branch_name}`
+   - **Merge Status**: Merged into `main` (Commit `{commit_hash}`)
+   - **Archive Date**: {YYYY-MM-DD}
+   ```
+2. Determine Category:
+   - If spec has `Category: Fix` or `Type: Fix` ➔ `fixes`
+   - If spec has `Category: Rollback` or `Type: Rollback` ➔ `rollbacks`
+   - Otherwise ➔ `features`
+3. Archive `devflow/context/current-feature.md` ➔ `devflow/history/{category}/{xxx-slug}.md`.
+4. If `findings.md` contains resolved entries (`closed`, `accepted`, `invalid`), append a `## Resolved Findings` section to the archive file and clean those resolved entries from `findings.md`.
+5. **Reset Living Spec Stub**: Reset `devflow/context/current-feature.md` to:
+   ```markdown
+   # Current Feature
+
+   _Nothing in progress. Run /feature, /fix, or /rollback to start._
+   ```
+
+### 4. Update Master Ledger (`HISTORY.md`)
+Append a new row to `devflow/history/HISTORY.md` under `## 📜 Master Release Log`:
 ```markdown
-## 6. Release & Handoff
-- **Release Digest**: สรุปสิ่งที่ส่งมอบในรอบนี้
-- **Git Branch**: `{branch_name}`
-- **Merge Status**: Merged into `main` (Commit `{commit_hash}`)
-- **Artifact Contract**: Fast-Track Single Living Spec completed.
+| {YYYY-MM-DD} | `{ID}` | {Category} | {Title} | `{commit_hash}` | `Released` | [`{xxx-slug}.md`]({category}/{xxx-slug}.md) |
 ```
-Update header status in `spec.md`: `> **Status**: Completed`.
 
-### 4. Policy on HTML Reports (Strict Rule)
+### 5. Policy on HTML Reports (Strict Rule)
 > [!IMPORTANT]
 > **No Auto-Generated HTML**: ห้ามสร้างไฟล์ `report.html` หรือ `60-report.html` แบบอัตโนมัติในขั้นตอนนี้โดยเด็ดขาด!
 > หากผู้ใช้ต้องการดู HTML Dashboard สวยงาม ให้แจ้งผู้ใช้ว่าสามารถเรียกคำสั่งแยกได้: `/report:html`
 
-### 5. Git Merge & Branch Cleanup
-1. Commit all modified tracking files (including `spec.md` and `current-stage.md`).
-2. Merge feature branch into target base branch (`main` / `master`).
+### 6. Git Merge & Branch Cleanup
+1. Commit all modified tracking files.
+2. Squash-merge feature branch into target base branch (`main` / `master`) with explicit user approval.
 
-### 6. Close Active Run
+### 7. Close Active Run
 Update `devflow/context/current-stage.md`:
+- `Active Discovery ID`: `None`
 - `Active Running ID`: `None (Idle)`
-- `Current Stage`: `Idle (Ready for new /spec, /feature, /fix, or /00-discover)`
-- `Last Completed Run`: `{RUNNING_ID} ({YYYY-MM-DD})`
+- `Current Stage`: `Idle (Ready for new /feature, /fix, or /00-discover)`
+- `Living Spec`: `None`
+- `Last Completed Run`: `{ID} ({YYYY-MM-DD})`
 - `Last Updated`: `{YYYY-MM-DD}`
 
-### 7. Output Completion Report
+### 8. Output Completion Report
 Report to the user:
 - Run successfully completed and merged
-- Living Spec path: `devflow/runs/{RUNNING_ID}/spec.md`
+- Archived path: `devflow/history/{category}/{xxx-slug}.md`
 - Standalone HTML command tip: `/report:html` (if HTML view is desired)
 - Workspace is now Idle and ready for the next task.

package/template/.claude/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/.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`