@jakkrichm/create-nexus-devflow 2.0.14 → 2.0.15

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

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

@@ -40,7 +40,7 @@ You are an orchestrator. Your goal is to call the specialized Git PR Maker agent
 - Prefer markdown-first stage artifacts as the source narrative:
   - `20-spec.md`
   - `30-plan.md`
-  - `40-implement.md`
+  - `40-execute.md`
   - `50-verify.md`
   - `60-report.md` when the final summary already exists
   - `70-release.md` when release execution notes already exist

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

@@ -38,5 +38,5 @@ This is the preview master skill for Nexus-DevFlow. It manages local development
 ## Relationship To DevFlow 2.0
 
 - **Classification**: Companion command & Runtime support
-- **Mainline stages**: `40-implement` (interactive visual check), `50-verify` (smoke test check)
+- **Mainline stages**: `40-execute` (interactive visual check), `50-verify` (smoke test check)
 - **Handoff**: `50-verify`

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

@@ -68,4 +68,4 @@ Categorize all findings into actionable severities:
 
 - **Classification**: Companion command & Verification support
 - **Mainline stages**: `50-verify` (QA & Code Review lane), `70-release` (Pre-merge review)
-- **Handoff**: `40-implement` (for fixes), `50-verify`, `70-release`
+- **Handoff**: `40-execute` (for fixes), `50-verify`, `70-release`

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

@@ -8,7 +8,7 @@ description: "[Devflow] Plan safe feature or run reversal with dependency and co
 Where this sits in the workflow:
 
 ```text
-completed run + git history  ->  [rollback]  ->  40-implement (or fix run)  ->  50-verify  ->  70-release
+completed run + git history  ->  [rollback]  ->  40-execute (or fix run)  ->  50-verify  ->  70-release
 (run archive + commits)          (risk review    (reverse product diff)          (prove)      (log & finalize)
                                   + plan)
 ```
@@ -51,7 +51,7 @@ Identify:
 
 - Exact commit SHA(s) introducing the feature.
 - Parent commit before the feature was introduced.
-- Associated stage artifacts (`20-spec.md`, `40-implement.md`, `70-release.md`).
+- Associated stage artifacts (`20-spec.md`, `40-execute.md`, `70-release.md`).
 
 ## Step 2 - Separate Product Changes From DevFlow History
 
@@ -98,7 +98,7 @@ Draft the rollback plan containing:
 Present the rollback plan to the user:
 
 - Summarize affected files and dependency risks.
-- If approved, route to `40-implement` (or allocate a dedicated Fixrollback Run) to safely execute the reversal steps behind review gates.
+- If approved, route to `40-execute` (or allocate a dedicated Fixrollback Run) to safely execute the reversal steps behind review gates.
 
 ## Rules
 

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

@@ -59,5 +59,5 @@ This is the comprehensive security master skill for Nexus-DevFlow. It combines s
 ## Relationship To DevFlow 2.0
 
 - **Classification**: Companion command & Safety gate
-- **Mainline integration**: Run during `40-implement` or `50-verify` before `70-release`.
-- **Handoff**: P0/P1 security findings block release and return to `40-implement` for immediate remediation.
+- **Mainline integration**: Run during `40-execute` or `50-verify` before `70-release`.
+- **Handoff**: P0/P1 security findings block release and return to `40-execute` for immediate remediation.

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

@@ -66,5 +66,5 @@ Delete commented-out code blocks, `// removed` notes, and unused variables (`_un
 ## Relationship To DevFlow 2.0
 
 - **Classification**: Companion command & Refactoring support
-- **Mainline integration**: Used during `40-implement` (Refactor step of TDD) or `50-verify`.
+- **Mainline integration**: Used during `40-execute` (Refactor step of TDD) or `50-verify`.
 - **Handoff**: `50-verify` (proves zero regressions).

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

@@ -1,105 +1,38 @@
 ---
 name: spec
-description: "[Devflow] Fast-Track Spec stage in DevFlow (Blueprint Mode) - define, spec, plan, and create the single living spec.md contract."
+description: "[Devflow] Fast-Track Spec router in DevFlow (Blueprint Mode) - aliases and routes to /feature or /fix to create the single living spec.md contract."
 argument-hint: "{feature title, bug description, IDEA-xxx, or running-id}"
 ---
 
-# Fast-Track: Spec (Blueprint Mode)
+# Fast-Track: Spec Router (Blueprint Mode)
 
 $ARGUMENTS
 
-Fast-Track entry point combining Discovery, Definition, Specification, and Implementation Planning into one streamlined, review-gated step. Creates and maintains the **Single Living Spec (`spec.md`)** for the run. Supports intake from Idea Inbox (`IDEA-xxx`).
+Unified Fast-Track entry point that routes to `/feature` or `/fix` to create and maintain the **Single Living Spec (`spec.md`)**.
+
+> [!TIP]
+> **Preferred Commands**:
+> - ใช้ **`/feature <title>`** สำหรับฟีเจอร์ใหม่หรืองานพัฒนาทั่วไป
+> - ใช้ **`/fix <bug-description>`** สำหรับแก้บั๊กหรือ hotfix
 
 ## Invocations & Aliases
 
-- `/spec <title>` or `spec <title>`: Standard Fast-Track specification
-- `/spec IDEA-xxx`: Intake and promote a pending idea from `devflow/ideas.md`
-- `/feature <title>` or `feature <title>`: Fast-Track feature workflow
-- `/fix <bug-description>` or `fix <bug-description>`: Fast-Track ad-hoc bugfix workflow
-- `$spec`, `$feature`, `$fix`: Codex CLI invocation
+- `/feature <title>`: Fast-Track feature workflow (แนะนำ)
+- `/fix <bug-description>`: Fast-Track ad-hoc bugfix workflow (แนะนำ)
+- `/spec <title>` or `/spec IDEA-xxx`: Generic Fast-Track specification
+- `$feature`, `$fix`, `$spec`: Codex CLI invocation
 
 ## Fast-Track Mainline Workflow
 
 ```text
-/spec ──▶ /implement ──▶ /check ──▶ /complete
+/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-016-{slug}`).
-4. Identify Git branch naming:
-   - For features: `feature/{slug}-{RUNNING_ID}`
-   - For bug fixes: `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}] {Title} (Living Spec)
-
-> **Status**: In-Progress  
-> **Track**: Fast-Track (Blueprint Mode)  
-> **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`: `spec (Fast-Track -> Ready for /implement)`
-- `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}`)
+1. If the input describes a bug or hotfix, routes to `/fix` behavior.
+2. Otherwise, routes to `/feature` behavior.
+3. Allocates sequential Running ID (`RUN-xxx`), creates directory `devflow/runs/{RUNNING_ID}/`, and generates `spec.md` in **Thai (`th`)**.
+4. Updates `devflow/context/current-stage.md` and reports next step: `/implement`.

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

@@ -81,7 +81,7 @@ For browser and UI features, unit tests alone are insufficient:
 
 ## 6. Test Generation & Persistent Execution Reports
 
-When generating or logging test runs during `40-implement` or `50-verify`:
+When generating or logging test runs during `40-execute` or `50-verify`:
 - Save summary reports to `devflow/reports/{date}-test-report-{slug}.md`
 - Include: Target, Test Cases (Happy Path, Error, Edge Cases), Pass/Fail statistics, and gaps/risks.
 
@@ -90,5 +90,5 @@ When generating or logging test runs during `40-implement` or `50-verify`:
 ## Relationship To DevFlow 2.0
 
 - **Classification**: Companion command & Engineering standard
-- **Mainline stages**: `30-plan` (TDD decisions), `40-implement` (TDD execution), `50-verify` (QA gate)
+- **Mainline stages**: `30-plan` (TDD decisions), `40-execute` (TDD execution), `50-verify` (QA gate)
 - **Handoff**: `50-verify`, `Debug`, `autopilot`

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

@@ -8,7 +8,7 @@ description: "[Devflow] Generate human manual QA review walkthrough guide (where
 Where this sits in the workflow:
 
 ```text
-40-implement or 50-verify or 60-report  ->  [try]  ->  human review & verification
+40-execute or 50-verify or 60-report  ->  [try]  ->  human review & verification
 (work implemented / verified)                  (manual    (where to go,
                                                steps)     what to click)
 ```
@@ -36,7 +36,7 @@ Read:
 - `devflow/context/current-stage.md`
 - `devflow/context/project-overview.md`
 - `devflow/context/coding-standards.md`
-- Active run artifacts: `20-spec.md`, `30-plan.md`, `40-implement.md`, `50-verify.md` (or archived run artifacts)
+- Active run artifacts: `20-spec.md`, `30-plan.md`, `40-execute.md`, `50-verify.md` (or archived run artifacts)
 - Current git branch and status
 
 Do not dump the full spec. Extract only the concrete routes, screens, CLI commands, API endpoints, test data, and expected outcomes that a human needs to verify the feature.

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

@@ -48,7 +48,7 @@ Run planning as an evidence loop, not as a one-shot outline.
 - **Observation**: use concrete evidence such as file paths, existing patterns, package scripts, validation commands, and unresolved assumptions.
 - **Adjustment**: if evidence is missing, search/read more, recommend `Research` or `Agent codebase-explorer`, split the work, or route back to `20-spec` when the contract is not plan-ready.
 - **Stop Condition**: stop only when phases are ordered, subtasks are scoped, verification is explicit, test decisions are recorded, and any blockers are visible.
-- **Handoff**: `30-plan.md` must give `40-implement` enough context to select one scoped unit and execute it without inventing intent.
+- **Handoff**: `30-plan.md` must give `40-execute` enough context to select one scoped unit and execute it without inventing intent.
 
 ### 1. Read Task Artifacts
 
@@ -161,12 +161,12 @@ If validation fails, repair only what is necessary and keep `30-plan.md` aligned
 
 ### 7. Manual Review Soft Gate
 
-Before recommending `40-implement`, check whether the plan still shows pending review.
+Before recommending `40-execute`, check whether the plan still shows pending review.
 If `Approval Status` is still pending or major dependencies remain unresolved:
 
 - warn that implementation should wait for review
 - recommend human confirmation of sequencing, scope, and verification strategy
-- keep `40-implement` as a soft recommendation only
+- keep `40-execute` as a soft recommendation only
 
 ## Output Checklist
 
@@ -184,7 +184,7 @@ If `Approval Status` is still pending or major dependencies remain unresolved:
 
 - Classification: Mainline workflow
 - Previous state: `20-spec`
-- Next state: `40-implement` when execution steps and verification are clear
+- Next state: `40-execute` when execution steps and verification are clear
 - Common companion commands: `Research` or `Agent` when architecture, data flow, or external constraints still need investigation; support skills: `grill-with-docs`, `domain-modeling`, `codebase-design`, `tdd`, and `to-issues` for final design stress-testing, durable terminology capture, test planning, and issue packaging
 
 ## Sources
@@ -192,11 +192,11 @@ If `Approval Status` is still pending or major dependencies remain unresolved:
 - `AGENTS.md`
 - `docs/workspace-artifacts.md`
 - `.agent/resources/schemas/plan.template.md`
-- Related commands: `20-spec`, `Research`, `Agent`, `40-implement`
+- Related commands: `20-spec`, `Research`, `Agent`, `40-execute`
 
 ## Next Workflow Recommendation
 
-- **Primary**: `40-implement {ID}`
+- **Primary**: `40-execute {ID}`
 - **Why**: Approved planning is the gate before implementation in DevFlow 2.0.
 - **Alternatives**:
   - `Research` - choose this when the plan still depends on missing evidence.