@jakkrichm/create-nexus-devflow 2.0.13 → 2.0.15

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

@@ -5,104 +5,113 @@ description: "[Devflow] Flagship interactive guide, state inspector, and intent
 
 # devflow - Interactive Workflow Guide & Intent Router for Nexus-DevFlow
 
-Use this skill to guide the user on what to do next, inspect current workspace state, map their natural language intent to the right Nexus-DevFlow stage or companion command, or display a sitemap of available DevFlow skills.
+Use this skill to guide the user on what to do next, inspect current workspace state, map their natural language intent to the right Nexus-DevFlow track (Fast-Track or Deep-Track) or companion command, or display a sitemap of available DevFlow skills.
 
 ## Input
 
-- **No argument (`devflow`, `devflow`, `$devflow`, or `status`)**: Inspect current workspace state (active run in `devflow/runs/` or `devflow/context/current-stage.md`, active discovery in `devflow/discoveries/`, open findings in `devflow/context/findings.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 2.0 stage or companion command path.
+- **No argument (`devflow`, `devflow`, `$devflow`, or `status`)**: Inspect current workspace state (active run in `devflow/runs/` or `devflow/context/current-stage.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.
+- **With user request (`devflow "<request>"`)**: Classify the user's intent and guide them to the matching DevFlow workflow track or companion command path.
+
+## Dual-Track Architecture
+
+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).*
+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.*
+
+---
 
 ## Workspace State Inspection
 
 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 they are 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}/` for active artifacts (`10-define.md`, `20-spec.md`, `30-plan.md`, `40-implement.md`, `50-verify.md`, `60-report.md`, `70-release.md`).
+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 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)**:
+     - If at `10-define.md` -> Recommend `20-spec {RUNNING_ID}`.
+     - If at `20-spec.md` -> Recommend `30-plan {RUNNING_ID}`.
+     - If at `30-plan.md` -> Recommend `40-execute {RUNNING_ID}`.
+     - If at `40-execute.md` with all tasks done -> Recommend `50-verify {RUNNING_ID}`.
+     - If passed `50-verify.md` -> Recommend `60-report {RUNNING_ID}` then `70-release {RUNNING_ID}`.
 3. **Active Discovery**: Check `devflow/discoveries/` for open discovery notes.
-4. **Audit Findings Ledger**: Check `devflow/context/findings.md` for open high-severity findings.
+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 `/spec IDEA-xxx`.
+5. **Audit Findings Ledger**: Check `devflow/context/findings.md` for open high-severity findings.
 
-### State-Based Recommendation Rules
+### Default State Recommendations
+- If no run is active and user wants to start a feature -> Recommend `/spec <name>` (or `/feature <name>`).
+- If no run is active and user wants to fix a bug -> Recommend `/fix <bug>`.
+- If no run is active and user has pending ideas in `devflow/ideas.md` -> Highlight `/spec IDEA-xxx`.
+- If no run is active and user wants deep architectural exploration -> Recommend `00-discover`.
+- If user asks to check system health -> Recommend `doctor`.
 
-- If context is empty/unconfigured -> Recommend `onboard` (for fresh project) or `adopt` (for brownfield codebase).
-- If a run is at `10-define.md` -> Recommend `20-spec {RUNNING_ID}` (or `20-spec`, `$20-spec`, `spec`).
-- If a run is at `20-spec.md` -> Recommend `30-plan {RUNNING_ID}` (or `30-plan`, `$30-plan`, `plan`).
-- If a run is at `30-plan.md` -> Recommend `40-implement {RUNNING_ID}` (or `40-implement`, `$40-implement`, `implement`).
-- If a run is at `40-implement.md` with incomplete tasks -> Recommend `40-implement {RUNNING_ID}`.
-- If a run is at `40-implement.md` with all tasks done -> Recommend `50-verify {RUNNING_ID}` (or `50-verify`, `$50-verify`, `verify`).
-- If a run passed `50-verify.md` -> Recommend `60-report {RUNNING_ID}` then `70-release {RUNNING_ID}`.
-- If no run is active and user wants to explore an idea -> Recommend `00-discover` (or `discover`, `Brainstorm`).
-- If no run is active and open P0/P1 findings exist -> Recommend `security-review` or `debug`.
-- If user asks to check system health or configuration -> Recommend `doctor` (or `doctor`, `$doctor`).
+---
 
 ## Intent Classification & Skill Routing
 
-When the user specifies a request, map it to the matching DevFlow 2.0 stage or companion command:
-
-| User Intent / Request Type | Recommended Skill | Normal Name / Alias | Lifecycle Path |
+| User Intent / Request Type | Recommended Skill | Normal Name / Alias | Track / Lifecycle Path |
 | :--- | :--- | :--- | :--- |
-| "Setup DevFlow on fresh/new project" | `onboard` | `onboard` / `setup` | `onboard` -> `00-discover` or `10-define` |
-| "Adopt DevFlow on existing codebase" | `adopt` | `adopt` / `bootstrap` | `adopt` -> `00-discover` or `10-define` |
+| **"Spec new feature / lean workflow"** | `spec` | `/spec` / `/feature` | **Fast-Track**: `/spec` -> `/implement` -> `/check` -> `/complete` |
+| **"Quick bugfix / ad-hoc change"** | `spec` | `/fix` | **Fast-Track**: `/fix` -> `/implement` -> `/check` -> `/complete` |
+| **"Capture quick idea / thought"** | `idea` | `/idea` | **Companion**: Enriches & saves to `devflow/ideas.md` |
+| **"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 |
+| "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` |
-| "Explore a new request / idea" | `00-discover` | `discover` | `00-discover` -> `10-define` -> `20-spec` -> ... |
-| "Define delivery boundaries and ID" | `10-define` | `define` | `10-define` -> `20-spec` -> `30-plan` |
-| "Write formal markdown specification" | `20-spec` | `spec` | `20-spec` -> `30-plan` -> `40-implement` |
-| "Break down spec into actionable plan" | `30-plan` | `plan` | `30-plan` -> `40-implement` -> `50-verify` |
-| "Execute code implementation" | `40-implement` | `implement` | `40-implement` -> `50-verify` |
-| "Verify code quality & QA review" | `50-verify` | `verify` | `50-verify` -> `60-report` -> `70-release` |
-| "Generate summary HTML/MD report" | `60-report` | `report` | `60-report` -> `70-release` |
-| "Package for PR merge or deployment" | `70-release` | `release` | `70-release` |
-| "Human manual QA walkthrough guide" | `try` | `try` | `try` (after implement or verify) |
-| "Safely plan feature or run reversal" | `rollback` | `rollback` | `rollback` -> `40-implement` |
-| "Set up automatic GitHub Actions CI" | `ci` | `ci` | `ci` (after onboard or adopt) |
-| "Pre-check scope & risks before spec" | `brief` | `brief` | `brief` -> `20-spec` |
-| "Run autonomous bounded delivery loop"| `autopilot` | `autopilot` | `autopilot` -> `70-release` |
-| "High-level goal or long-running task" | `goal` | `goal` | `goal` -> `00-discover` |
-| "Brainstorm ideas without allocating ID" | `brainstorm` | `brainstorm` | `brainstorm` -> `00-discover` |
-| "Deep codebase or web research" | `research` | `research` | `research` |
-| "Investigate failure or root cause" | `debug` | `debug` | `debug` -> `40-implement` or `10-define` |
-| "Product framing & PRD creation" | `prd` | `prd` | `prd` -> `00-discover` |
-| "Intake and triage incoming bugs" | `issue-triage` | `issue-triage` | `issue-triage` -> `debug` or `10-define` |
-| "High-severity security audit" | `security-review` | `security-review` | `security-review` |
-| "Manage project knowledge base" | `wiki` | `wiki` | `wiki` |
-| "Verify or update DevFlow setup" | `check-for-updates` | `check-for-updates` | `check-for-updates` |
+| "Explore a new request / deep idea" | `00-discover` | `discover` | **Deep-Track**: `00` -> `10` -> `20` -> ... |
+| "Define delivery boundaries and ID" | `10-define` | `define` | **Deep-Track**: `10` -> `20` -> `30` |
+| "Break down spec into plan (Deep)" | `30-plan` | `plan` | **Deep-Track**: `30` -> `40` -> `50` |
+| "Deep code implementation" | `40-execute` | `implement` | **Deep-Track**: `40` -> `50` |
+| "Deep QA verification" | `50-verify` | `verify` | **Deep-Track**: `50` -> `60` -> `70` |
+| "Deep markdown digest report" | `60-report` | `report` | **Deep-Track**: `60` -> `70` |
+| "Deep release packaging & merge" | `70-release` | `release` | **Deep-Track**: `70-release` |
+| "Human manual QA walkthrough guide" | `try` | `try` | Companion (after implement or check) |
+| "Safely plan feature or run reversal" | `rollback` | `rollback` | Companion |
+| "Set up automatic GitHub Actions CI" | `ci` | `ci` | Companion |
+| "Pre-check scope & risks before spec" | `brief` | `brief` | Companion |
+| "Run autonomous bounded delivery loop"| `autopilot` | `autopilot` | Companion |
+| "Brainstorm ideas without ID" | `brainstorm` | `brainstorm` | Companion |
+| "Investigate failure or root cause" | `debug` | `debug` | Companion |
+
+---
 
 ## Available Skills Sitemap
 
-Always provide a clean summary of available Nexus-DevFlow skills grouped by lifecycle stage:
-
-### 1. Mainline Lifecycle Stages (Linear Order)
-- `00-discover` (`discover`, `00-discover`, `$00-discover`) - Explore request, route inquiries, go/no-go under Discovery ID
-- `10-define` (`define`, `10-define`, `$10-define`) - Lock delivery boundaries and allocate Running ID (`devflow/runs/{ID}`)
-- `20-spec` (`spec`, `20-spec`, `$20-spec`) - Formalize markdown-first specifications and acceptance criteria
-- `30-plan` (`plan`, `30-plan`, `$30-plan`) - Transform spec into executable task breakdown with test decisions
-- `40-implement` (`implement`, `40-implement`, `$40-implement`) - Execute planned tasks incrementally with evidence
-- `50-verify` (`verify`, `50-verify`, `$50-verify`) - Senior QA review, validation checks, and pass/fail gate
-- `60-report` (`report`, `60-report`, `$60-report`) - Generate standardized markdown and HTML summary report
-- `70-release` (`release`, `70-release`, `$70-release`) - Package verified work for PR merge or deployment
-
-### 2. Public Companion Commands
-- `devflow` (`status`, `devflow`, `$devflow`) - Guide, state inspector, and intent router
-- `onboard` (`onboard`, `$onboard`) - Baseline stack setup for freshly scaffolded projects
-- `adopt` (`adopt`, `$adopt`) - Survey and bootstrap DevFlow into existing brownfield projects
-- `doctor` (`doctor`, `$doctor`) - Read-only health check for setup, scripts, and workflow drift
-- `try` (`try`, `$try`) - Step-by-step human manual QA review guide (where to go, what to click, what to expect)
-- `rollback` (`rollback`, `$rollback`) - Safe feature/run reversal planner with dependency risk analysis
-- `ci` (`ci`, `$ci`) - Automatic GitHub Actions workflow (`.github/workflows/verify.yml`) setup
-- `brief` (`brief`, `$brief`) - Read-only scope, dependency, and size pre-briefing before speccing
-- `autopilot` (`autopilot`, `$autopilot`) - Optional bounded autonomous loop (spec -> plan -> implement -> verify -> report)
-- `goal` - Route broad goals before Discovery
+### 1. Fast-Track (Blueprint Mode - 4 Steps)
+- `spec` (`/spec`, `/feature`, `/fix`, `$spec`) - Define, spec, plan, and create `spec.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
+
+### 2. Deep-Track (Architect Mode - 8 Steps)
+- `00-discover` - Explore request and decide Proceed/Defer/Reject
+- `10-define` - Lock delivery boundaries and allocate Running ID
+- `20-spec` - Formalize markdown delivery contract
+- `30-plan` - Breakdown spec into phased tasks with test decisions
+- `40-execute` - Incremental task implementation
+- `50-verify` - Senior QA review and multi-lane validation
+- `60-report` - Generate standardized markdown digest report
+- `70-release` - Release packaging, release notes, and merge
+
+### 3. Public Companion Commands
+- `devflow` (`status`, `/devflow`) - Interactive guide, state inspector, and router
+- `idea` (`/idea`) - Quick idea capture and AI feasibility enrichment into `devflow/ideas.md`
+- `report-html` (`/report:html`) - Standalone interactive HTML report dashboard generator
+- `onboard` - Baseline stack setup for freshly scaffolded projects
+- `adopt` - Bootstrap DevFlow into existing brownfield projects
+- `doctor` - Read-only health check for setup and drift
+- `try` - Step-by-step human manual QA review guide
+- `rollback` - Safe feature/run reversal planner
+- `ci` - Automatic GitHub Actions workflow setup
+- `brief` - Read-only scope and risk pre-briefing
+- `autopilot` - Autonomous bounded delivery loop
 - `brainstorm` - Ideate without allocating running IDs
-- `research` - Conduct codebase or web research
 - `debug` - Root cause investigation before or during implementation
-- `prd` - Product framing before delivery commitment
-- `issue-triage` - Intake and triage incoming bug reports
-- `security-review` - High-severity security review
-- `wiki` - Knowledge base management under `devflow/wiki/`
-- `check-for-updates` - Verify or upgrade DevFlow setup
-- `help` - Process assistance and stage routing
-
-### 3. Engineering & Specialist Skills
-- **Frontend & UI**: `frontend-ui-engineering`, `nextjs-react-expert`, `tailwind-patterns`, `ui-ux-pro-max`, `mobile-design`
-- **Quality & Security**: `code-review-and-quality`, `security-and-hardening`, `test-driven-development`, `vulnerability-scanner`, `performance-optimization`
-- **Architecture & System**: `architecture`, `database-design`, `domain-modeling`, `codebase-design`, `api-and-interface-design`
-- **Tools & Productivity**: `md2html`, `obsidian-markdown`, `git-workflow-and-versioning`, `parallel-agents`, `context-engineering`
+- `overview` - Living context synchronization into project-overview.md

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

@@ -52,7 +52,7 @@ Run through these 5 health checks:
   - Are there active runs?
   - Is `current-stage.md` consistent with the latest stage artifact in the active run?
   - Are checklists (`checklists/implementation-checklist.md`, `checklists/verification-checklist.md`) properly tracked?
-  - Detect stage skips or workflow drift (e.g. jumping from `10-define` directly to `40-implement` without `20-spec` and `30-plan`).
+  - Detect stage skips or workflow drift (e.g. jumping from `10-define` directly to `40-execute` without `20-spec` and `30-plan`).
 
 ### Check 5: Findings Ledger Inspection
 - Inspect `devflow/context/findings.md`:

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

@@ -0,0 +1,103 @@
+---
+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."
+argument-hint: "{feature title, IDEA-xxx, or feature description}"
+---
+
+# Fast-Track: Feature (Blueprint Mode)
+
+$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`).
+
+## Invocations & Aliases
+
+- `/feature <title>` or `feature <title>`: Fast-Track feature specification
+- `/feature IDEA-xxx`: Intake and promote a pending idea from `devflow/ideas.md`
+- `$feature`: Codex CLI invocation
+
+## Fast-Track Mainline Workflow
+
+```text
+/feature (หรือ /fix) ──▶ /implement ──▶ /check ──▶ /complete
+```
+
+## Behavior & Contract
+
+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`):
+   - 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}/`.
+
+### 2. Generate the Single Living Spec (`spec.md`)
+Write `devflow/runs/{RUNNING_ID}/spec.md` using the structured template below in **Thai (`th`)**:
+
+```markdown
+# 📐 [{RUNNING_ID}] {Feature Title} (Living Spec)
+
+> **Status**: In-Progress  
+> **Track**: Fast-Track (Blueprint Mode - Feature)  
+> **Branch**: `{branch_name}`  
+> **Created Date**: {YYYY-MM-DD}  
+> **Owner**: {Contributor or Team}  
+
+---
+
+## 1. Specification & Scope
+- **Problem Statement**: {ปัญหาหรือที่มาของฟีเจอร์นี้}
+- **In-Scope**:
+  - {ขอบเขตสิ่งที่ต้องทำสำหรับฟีเจอร์นี้}
+- **Out-of-Scope**:
+  - {สิ่งที่ไม่ทำในรอบนี้}
+- **Acceptance Criteria**:
+  - [ ] AC-1: {เงื่อนไขการตรวจรับข้อที่ 1}
+  - [ ] AC-2: {เงื่อนไขการตรวจรับข้อที่ 2}
+
+## 2. Plan & Test Strategy
+- **Files to Modify / Create**:
+  - `{path/to/file1}`: {หน้าที่ที่ต้องสร้าง/แก้ไข}
+  - `{path/to/file2}`: {หน้าที่ที่ต้องสร้าง/แก้ไข}
+- **Test Decision**: `Required (TDD)` | `Manual/Command Only` | `Not Required`
+  - *Rationale*: {เหตุผลความจำเป็นในการเขียนเทสต์}
+  - *Planned Cases*: {กรณีทดสอบหลักตาม AAA Pattern}
+- **Impact & Rollback Strategy**:
+  - *Impact*: {ผลกระทบต่อโมดูลอื่น}
+  - *Rollback*: {วิธีย้อนคืนการทำงานกรณีเกิดปัญหา}
+
+## 3. Implementation Checklist
+- [ ] Task 1.1: {งานย่อยข้อที่ 1}
+- [ ] Task 1.2: {งานย่อยข้อที่ 2}
+- [ ] Task 1.3: {งานย่อยข้อที่ 3}
+
+## 4. Implementation Record
+- *(จะถูกบันทึกเมื่อรัน /implement)*
+
+## 5. Verification Evidence
+- *(จะถูกบันทึกเมื่อรัน /check)*
+
+## 6. Release & Handoff
+- *(จะถูกบันทึกเมื่อรัน /complete)*
+```
+
+### 3. Update Workspace Status
+Update `devflow/context/current-stage.md`:
+- `Active Running ID`: `{RUNNING_ID}`
+- `Current Stage`: `feature (Fast-Track -> Ready for /implement)`
+- `Living Spec`: `devflow/runs/{RUNNING_ID}/spec.md`
+- `Last Updated`: `{YYYY-MM-DD}`
+
+### 4. 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}`)

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

@@ -0,0 +1,102 @@
+---
+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."
+argument-hint: "{bug description, issue ID, or IDEA-xxx}"
+---
+
+# Fast-Track: Fix (Blueprint Mode)
+
+$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.
+
+## Invocations & Aliases
+
+- `/fix <bug-description>` or `fix <bug-description>`: Fast-Track ad-hoc bugfix workflow
+- `/fix IDEA-xxx`: Intake and fix a reported issue or idea from `devflow/ideas.md`
+- `$fix`: Codex CLI invocation
+
+## Fast-Track Mainline Workflow
+
+```text
+/feature (หรือ /fix) ──▶ /implement ──▶ /check ──▶ /complete
+```
+
+## Behavior & Contract
+
+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`):
+   - 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}/`.
+
+### 2. Generate the Single Living Spec (`spec.md`)
+Write `devflow/runs/{RUNNING_ID}/spec.md` using the structured template below in **Thai (`th`)**:
+
+```markdown
+# 📐 [{RUNNING_ID}] {Bug/Fix Title} (Living Spec)
+
+> **Status**: In-Progress  
+> **Track**: Fast-Track (Blueprint Mode - Fix)  
+> **Branch**: `{branch_name}`  
+> **Created Date**: {YYYY-MM-DD}  
+> **Owner**: {Contributor or Team}  
+
+---
+
+## 1. Specification & Scope
+- **Problem Statement & Reproduction**: {อาการบั๊กที่พบ ขั้นตอนที่ทำให้เกิดปัญหา หรือ Error Log}
+- **Root Cause Analysis**: {สาเหตุที่แท้จริงของบั๊ก}
+- **In-Scope**:
+  - {ขอบเขตการแก้ไขบั๊กและการป้องกัน regression}
+- **Out-of-Scope**:
+  - {สิ่งที่ไม่แตะต้องหรืออยู่นอกเหนือการแก้จุดนี้}
+- **Acceptance Criteria**:
+  - [ ] AC-1: {เงื่อนไขการแก้ปัญหาสำเร็จและพฤติกรรมที่ถูกต้อง}
+  - [ ] AC-2: {มี Regression Test ป้องกันไม่ให้เกิดซ้ำ}
+
+## 2. Plan & Test Strategy
+- **Files to Modify / Create**:
+  - `{path/to/file1}`: {หน้าที่ที่ต้องแก้ไข}
+  - `{path/to/test_file}`: {เทสต์เคสจำลองและป้องกันบั๊ก}
+- **Test Decision**: `Required (TDD / Regression Test)`
+  - *Rationale*: {การแก้บั๊กต้องมี Regression Test ยืนยันเสมอ}
+  - *Planned Cases*: {เคสทดสอบจำลองบั๊ก (Red) และทดสอบหลังแก้ (Green)}
+- **Impact & Rollback Strategy**:
+  - *Impact*: {ผลกระทบต่อโมดูลข้างเคียง}
+  - *Rollback*: {วิธีย้อนคืนการทำงานกรณีเกิดปัญหา}
+
+## 3. Implementation Checklist
+- [ ] Task 1.1: {เขียน Regression Test เพื่อ reproduce บั๊ก}
+- [ ] Task 1.2: {แก้ไขโค้ดที่จุดเกิดเหตุ}
+- [ ] Task 1.3: {รันชุดทดสอบเพื่อยืนยันว่าบั๊กหายและไม่กระทบจุดอื่น}
+
+## 4. Implementation Record
+- *(จะถูกบันทึกเมื่อรัน /implement)*
+
+## 5. Verification Evidence
+- *(จะถูกบันทึกเมื่อรัน /check)*
+
+## 6. Release & Handoff
+- *(จะถูกบันทึกเมื่อรัน /complete)*
+```
+
+### 3. Update Workspace Status
+Update `devflow/context/current-stage.md`:
+- `Active Running ID`: `{RUNNING_ID}`
+- `Current Stage`: `fix (Fast-Track -> Ready for /implement)`
+- `Living Spec`: `devflow/runs/{RUNNING_ID}/spec.md`
+- `Last Updated`: `{YYYY-MM-DD}`
+
+### 4. 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}`)

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

@@ -36,7 +36,7 @@ Read:
 - `devflow/runs/{ID}-*10-define.md`
 - `devflow/runs/{ID}-*20-spec.md`
 - `devflow/runs/{ID}-*30-plan.md`
-- `devflow/runs/{ID}-*40-implement.md`
+- `devflow/runs/{ID}-*40-execute.md`
 - `devflow/runs/{ID}-*50-verify.md` if present
 
 ### 2. Classify The Follow-Up
@@ -57,7 +57,7 @@ Append the follow-up scope directly to the relevant stage markdown files for the
 
 ### 4. Ask For Confirmation
 
-After adding or proposing follow-up subtasks, ask the user to confirm before `40-implement`.
+After adding or proposing follow-up subtasks, ask the user to confirm before `40-execute`.
 
 ## Output
 
@@ -66,18 +66,18 @@ Return:
 - follow-up category
 - new phase/subtask plan
 - validation result
-- next command: `40-implement {ID}`
+- next command: `40-execute {ID}`
 
 ## Relationship To DevFlow 2.0
 
 - Classification: Companion command
 - Mainline status: Not a numbered stage
 - Typical entry points: after review, triage, or release follow-up work is identified
-- Typical handoff targets: `10-define`, `20-spec`, `30-plan`, `40-implement`
+- Typical handoff targets: `10-define`, `20-spec`, `30-plan`, `40-execute`
 
 ## Sources
 
 - `AGENTS.md`
-- Related commands: `PR-Followup`, `Issue-Triage`, `Human-Feedback`, `10-define`, `20-spec`, `40-implement`
+- Related commands: `PR-Followup`, `Issue-Triage`, `Human-Feedback`, `10-define`, `20-spec`, `40-execute`
 
 

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

@@ -77,14 +77,14 @@ Help Summary:
 Environment: All OK
 
 Active Runs:
-- 010-auth-refactor: stage=40-implement | approval=Pending | next=50-verify 010 | warnings: manual review open
+- 010-auth-refactor: stage=40-execute | approval=Pending | next=50-verify 010 | warnings: manual review open
 - 011-billing-phase-1: stage=20-spec | approval=Approved | next=30-plan 011
 - 012-admin-console: stage=50-verify | approval=Approved | next=60-report 012 | warnings: not ready for release
 
 Recommended Next Action:
 - 010 -> 50-verify 010
 - 011 -> 20-spec 011
-- 012 -> 40-implement 012
+- 012 -> 40-execute 012
 ```
 
 ### Phase C: Manual Review Soft Gate
@@ -114,7 +114,7 @@ Manual Review Warning:
 ## DevFlow 2.0 Mainline
 
 ```text
-00-discover -> 10-define -> 20-spec -> 30-plan -> 40-implement -> 50-verify -> 60-report -> 70-release
+00-discover -> 10-define -> 20-spec -> 30-plan -> 40-execute -> 50-verify -> 60-report -> 70-release
 ```
 
 ## Public Companion Commands
@@ -182,7 +182,7 @@ Recommend `30-plan`.
 
 ### 5. If planning is done and work should begin
 
-Recommend `40-implement`.
+Recommend `40-execute`.
 
 ### 6. If implementation exists and needs checking
 

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

@@ -0,0 +1,57 @@
+---
+name: idea
+description: "[Devflow] Quick idea capture and AI enrichment - analyze feasibility, value, key points, and record into devflow/ideas.md inbox."
+argument-hint: "\"<idea text or description>\""
+---
+
+# idea - Quick Idea Capture & AI Enrichment
+
+$ARGUMENTS
+
+Use this skill to quickly capture feature ideas, improvements, or architectural thoughts before they are forgotten. The AI immediately enriches the idea with **Feasibility Assessment**, **Value & Impact Analysis**, and **Quick Seed Key Points** (to prevent forgetting the nuance), then stores it in the central idea inbox at `devflow/ideas.md`.
+
+## Invocations & Aliases
+
+- `/idea "<idea text>"`: Standard slash command in Claude Code / Antigravity
+- `idea "<idea text>"`: Plain text invocation
+- `$idea "<idea text>"`: Codex CLI invocation
+
+## Behavior & Contract
+
+When invoked:
+
+### 1. Load Idea Inbox Hub
+1. Check if `devflow/ideas.md` exists. If not, create it with the standard DevFlow Ideas template.
+2. Read `devflow/ideas.md` and find the highest existing `IDEA-xxx` number.
+3. Allocate the next sequential ID (e.g. `IDEA-001`, `IDEA-002`).
+
+### 2. AI Feasibility & Value Analysis
+Evaluate the user's raw idea and generate an enriched summary in **Thai (`th`)**:
+- **ไอเดียตั้งต้น (Raw Idea)**: ข้อความที่ผู้ใช้ระบุ
+- **AI Feasibility & Tech**: ประเมินความเป็นไปได้ (ง่าย / ปานกลาง / ซับซ้อน) พร้อมแนะนำ Library, API, หรือแนวทางเทคนิคเบื้องต้น
+- **Value & Potential**: คุณค่า ประโยชน์ และความน่าสนใจของฟีเจอร์นี้
+- **Quick Seed (สรุปประเด็นกันลืม)**: 2-3 ประเด็นทางเทคนิคหรือแนวทางการต่อยอด เพื่อให้กลับมาอ่านทีหลังแล้วจำบริบทได้ทันที
+
+### 3. Append to `devflow/ideas.md`
+Insert the new idea block directly under `## 📌 Pending Ideas` in `devflow/ideas.md`:
+
+```markdown
+### [IDEA-001] {หัวข้อไอเดียสั้นๆ}
+- **บันทึกเมื่อ**: {YYYY-MM-DD}
+- **ไอเดียตั้งต้น**: {ข้อความที่ผู้ใช้ป้อน}
+- **AI Feasibility & Tech**: {บทวิเคราะห์ความเป็นไปได้และเครื่องมือ}
+- **Value & Potential**: {บทวิเคราะห์คุณค่าและความน่าสนใจ}
+- **Quick Seed (กันลืม)**:
+  1. {ประเด็นสำคัญที่ 1}
+  2. {ประเด็นสำคัญที่ 2}
+- **สถานะ**: `Pending` (หยิบไปทำได้ด้วย `/spec IDEA-001` หรือ `/00-discover IDEA-001`)
+```
+
+*(หากมีข้อความ `*(ยังไม่มีไอเดียค้างอยู่...)*` ให้ลบออกเมื่อมีไอเดียแรก)*
+
+### 4. Output Summary
+Report to the user:
+- Allocated Idea ID: `[IDEA-xxx]`
+- Summary of Feasibility & Value analysis
+- Seed points saved
+- Instructions for promotion: "เมื่อพร้อมลงมือทำ สามารถพิมพ์ `/spec IDEA-xxx` หรือ `/00-discover IDEA-xxx` ได้ทันที"

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

@@ -0,0 +1,64 @@
+---
+name: implement
+description: "[Devflow] Fast-Track Implement stage in DevFlow (Blueprint Mode) - execute checklist tasks incrementally with TDD and update spec.md."
+argument-hint: "{running-id or workspace path}"
+---
+
+# Fast-Track: Implement (Blueprint Mode)
+
+$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.
+
+## Invocations & Aliases
+
+- `/implement`: Run implementation on current active run
+- `/implement {running-id}`: Run implementation on specified running ID
+- `$implement`: Codex CLI invocation
+
+## Fast-Track Mainline Workflow
+
+```text
+/spec ──▶ /implement ──▶ /check ──▶ /complete
+```
+
+## Behavior & Contract
+
+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`.
+3. Locate `## 2. Plan & Test Strategy` and `## 3. Implementation Checklist`.
+
+### 2. Incremental Execution with TDD
+1. Select unchecked items `- [ ]` from the checklist in order.
+2. For each task:
+   - **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`.
+
+### 3. Update Living Spec (`spec.md`)
+Append or update `## 4. Implementation Record` in `spec.md` with:
+- Summary of completed tasks and modified files
+- Key architectural observations or notes
+- Status of checklist items
+
+Example:
+```markdown
+## 4. Implementation Record
+- **[Task 1.1]**: Implemented JWT auth middleware in `src/middleware/auth.ts`
+- **[Task 1.2]**: Added unit tests in `test/auth.test.ts` (All 6 tests passing)
+- **[Task 1.3]**: Registered auth route in `src/server.ts`
+```
+
+### 4. Update Workspace Status
+Update `devflow/context/current-stage.md`:
+- `Current Stage`: `implement (Fast-Track -> Checklist Completed -> Ready for /check)`
+
+### 5. Output Summary & Next Step
+Report to the user:
+- Completed checklist items and modified files
+- Local verification results
+- **Next Command**: `/check` (or `/check {RUNNING_ID}`)

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

@@ -27,7 +27,7 @@ What Broke ➔ Business Impact ➔ Root Cause ➔ Fix Evidence ➔ Prevention &
 
 ## 2. Process & Recording Destinations
 
-1. **Load Evidence**: Review `git diff`, `40-implement.md`, `50-verify.md`, or test logs.
+1. **Load Evidence**: Review `git diff`, `40-execute.md`, `50-verify.md`, or test logs.
 2. **Distill Insights**: Formulate clear, actionable, non-generic takeaways.
 3. **Save to Persistent Memory**:
    - Save project-wide engineering lessons to `devflow/context/lessons.md` (or `knowledge/lessons.md`).