@jakkrichm/create-nexus-devflow 2.0.13 → 2.0.14

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

@@ -1,6 +1,6 @@
----name: 60-report
-
-description: "[Devflow] Report stage in DevFlow 2.0 - produce standardized markdown and HTML summary report for the completed run."
+---
+name: 60-report
+description: "[Devflow] Report stage in DevFlow 2.0 - produce standardized markdown summary report for the completed run."
 argument-hint: "{running-id or workspace path}"
 ---
 
@@ -8,7 +8,7 @@ argument-hint: "{running-id or workspace path}"
 
 $ARGUMENTS
 
-Produce the final human-friendly summary of the full running flow in both Markdown and HTML so the outcome is easy to communicate every time.
+Produce the final human-friendly summary of the full running flow in Markdown (`60-report.md`) so the outcome is easy to communicate every time.
 
 ## Usage
 
@@ -16,19 +16,12 @@ Produce the final human-friendly summary of the full running flow in both Markdo
 60-report {running-id or workspace path}
 ```
 
-Use this when:
-
-- verification is complete and the run is ready for a final standardized summary before release
-- the team needs a standardized summary for communication
-- non-technical readers should be able to understand what happened
-
 ## Markdown-First Contract
 
-Write the primary stage artifacts to:
+Write the primary stage artifact to:
 
 ```text
-devflow/runs/{ID}-{slug}60-report.md
-devflow/runs/{ID}-{slug}60-report.html
+devflow/runs/{ID}-{slug}/60-report.md
 ```
 
 using:
@@ -39,6 +32,9 @@ using:
 
 Before writing `60-report.md`, read `artifact_language` from `report.template.md` and produce the markdown artifact in that language.
 
+> [!IMPORTANT]
+> **No Auto-Generated HTML**: ยกเลิกการสร้างไฟล์ `60-report.html` แบบอัตโนมัติในขั้นตอนนี้! ระบบจะสร้างเฉพาะ `60-report.md` เท่านั้น หากผู้ใช้หรือทีมต้องการสร้าง HTML Report สวยงาม ให้เรียกคำสั่งแยกต่างหาก: `/report:html` หรือ `npm run report:html`
+
 ## Required Section Content
 
 Before completing any generated artifact:
@@ -57,13 +53,13 @@ Before completing any generated artifact:
 
 Run reporting as an outcome-evidence loop, not as a dump of prior artifacts.
 
-- **Intent**: produce a final markdown and HTML summary that lets a reader understand the outcome, evidence, decisions, risks, and next actions without replaying the whole run.
+- **Intent**: produce a final markdown summary that lets a reader understand the outcome, evidence, decisions, risks, and next actions without replaying the whole run.
 - **Context**: read all relevant stage artifacts, checklist files, verify impact notes, release notes, validation output, and supporting artifacts that materially explain the result.
-- **Action**: summarize the problem, direction, completed work, validation outcome, checklist progress, final decision, open risks, and next actions, then render the HTML report.
+- **Action**: summarize the problem, direction, completed work, validation outcome, checklist progress, final decision, open risks, and next actions.
 - **Observation**: use concrete evidence such as checklist completion, blocked or skipped items, validation results, release state, impact notes, and unresolved follow-ups.
 - **Adjustment**: if evidence is missing, return to the owning stage; if the report must support continuation, use `handoff`; if the run produced reusable lessons, use `insight-capture` or `Wiki`.
-- **Stop Condition**: stop when `70-report.md` and `70-report.html` both exist, summarize the outcome accurately, include checklist and evidence snapshots, and name any remaining follow-up work.
-- **Handoff**: `70-report.md` must close the mainline run or tell the next reader exactly where follow-up work should continue.
+- **Stop Condition**: stop when `60-report.md` exists, summarizes the outcome accurately, includes checklist and evidence snapshots, and names any remaining follow-up work.
+- **Handoff**: `60-report.md` must close the mainline run or tell the next reader exactly where follow-up work should continue.
 
 ### 1. Gather Full Run Context
 
@@ -98,19 +94,9 @@ Explain:
 
 Write:
 
-- a readable Markdown report for contributors
-- a consistent HTML report for stakeholder sharing
-
-In phase 1, `artifact_language` governs the markdown report text. HTML output is derived directly from `60-report.md` through the shared markdown-to-html renderer.
+- a readable Markdown report (`60-report.md`) for contributors
 
-To render the HTML consistently from the markdown report, use one of:
-
-```text
-npm run report:html -- <workspace-path-or-running-id>
-npm run render:html -- --stage 60-report <workspace-path-or-running-id>
-```
-
-Keep checklist summaries and follow-up status inside `60-report.md` so they carry through into the rendered HTML.
+Keep checklist summaries and follow-up status inside `60-report.md`.
 
 Both outputs should summarize checklist state when checklist artifacts exist, including:
 
@@ -120,27 +106,6 @@ Both outputs should summarize checklist state when checklist artifacts exist, in
 - approval status, review blockers, and next allowed command when they still matter
 - remaining follow-up work
 
-The HTML should stay visually consistent across runs while preserving the report markdown as the source of truth.
-
-### 4. Keep The Audience In Mind
-
-Prefer clarity over internal detail.
-
-Do not bury the outcome inside implementation trivia. The report should help a reader understand the run without replaying the whole workflow.
-
-When checklists exist, use them as the most human-readable operational record of what actually happened.
-Use `handoff` when the report must support continued work, and `insight-capture` when the run produced lessons that should become reusable knowledge.
-
-### 5. Manual Review Soft Gate
-
-Use the report as the final visibility checkpoint before release.
-If any stage still shows unresolved approval, blockers, or deferred work:
-
-- surface that state clearly in `60-report.md`
-- pull the relevant signal forward from checklist approval sections when they exist
-- do not imply the phase is fully closed when review is still open
-- recommend the real next action, even if that means returning to an earlier stage
-
 ## Output
 
 Report:
@@ -148,37 +113,18 @@ Report:
 - what the run accomplished
 - checklist completion status and remaining items
 - important remaining follow-ups
-- where `60-report.md` and `60-report.html` were written
-- render command used or recommended:
-
-```text
-npm run report:html -- <workspace-path-or-running-id>
-```
+- where `60-report.md` was written
+- standalone HTML command tip: `/report:html` (if HTML view is desired)
 
 ## Relationship To DevFlow 2.0
 
 - Classification: Mainline workflow
 - Previous state: `50-verify`
 - Next state: `70-release` when the summary is aligned and release can proceed
-- Common companion commands: `Wiki` for durable knowledge capture, `Help` for routing or explanation
-- Support skills: `handoff`, `insight-capture`, and writing skills when final reporting must support continuation or reusable learning
-
-## Sources
-
-- `AGENTS.md`
-- `docs/workspace-artifacts.md`
-- `.agent/resources/schemas/report.template.md`
-- Related commands: `50-verify`, `70-release`, `Wiki`, `Help`
+- Common companion commands: `/report:html` for standalone HTML dashboard, `Wiki` for durable knowledge capture, `Help` for routing or explanation
 
 ## Next Workflow Recommendation
 
-- **Primary**: `70-release {ID}` after `60-report.md` and `60-report.html` reflect the verified state clearly.
-- **Render HTML**: `npm run report:html -- {ID}` after `60-report.md` is finalized so the standardized stakeholder HTML stays in sync
-- **Alternative**: `Wiki` when the completed run should be promoted into durable reusable knowledge before release packaging continues
-- **Additional Alternative**: `handoff` when another session or agent must continue from the completed run.
-
-## Nexus Event
-
-- Use `Wiki` when the final summary should become durable project or framework knowledge.
-- Use `Help` when approval signals, ownership, or route timing still feel ambiguous.
-- Return to `50-verify` when unresolved evidence, blockers, or review state mean the report should not advance yet.
+- **Primary**: `70-release {ID}` after `60-report.md` reflects the verified state clearly.
+- **Optional Standalone HTML**: `/report:html` (or `npm run report:html -- {ID}`) if an interactive HTML report is desired for stakeholder presentation.
+- **Alternative**: `Wiki` when the completed run should be promoted into durable reusable knowledge before release packaging continues.

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

@@ -148,7 +148,7 @@ Report:
 - 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`
+- 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
@@ -156,13 +156,14 @@ Report:
 - `AGENTS.md`
 - `docs/workspace-artifacts.md`
 - `.agent/resources/schemas/release.template.md`
-- Related commands: `60-report`, `Commit`, `PR`, `Deploy`, `Changelog`, `Merge`, `Wiki`
+- Related commands: `60-report`, `Commit`, `PR`, `Deploy`, `Changelog`, `Merge`, `Wiki`, `overview`
 
 ## Next Workflow Recommendation
 
-- **Primary**: End of Timeline flow
+- **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-implement` - choose this when additional fixes are needed before release can proceed.
@@ -170,7 +171,7 @@ Report:
 
 ## Nexus Event
 
-- Use `Commit`, `PR`, `Deploy`, `Merge`, or `Changelog` when release execution still needs a concrete lane.
+- 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-implement` when release readiness changes because unresolved issues are discovered.
 

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

@@ -0,0 +1,68 @@
+---
+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."
+argument-hint: "{running-id or workspace path}"
+---
+
+# Fast-Track: Check (Blueprint Mode)
+
+$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`).
+
+## Invocations & Aliases
+
+- `/check`: Run verification on current active run
+- `/check {running-id}`: Run verification on specified running ID
+- `$check`: 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 `## 1. Specification & Scope` (Acceptance Criteria) and `## 3. Implementation Checklist`.
+
+### 2. Multi-lane Verification Execution
+Execute the verification gates across all lanes:
+1. **Lane 1 (Type & Syntax Safety)**:
+   - Run typecheck and linting (e.g. `npm run typecheck`, `npm run lint`).
+2. **Lane 2 (Test Suites & Coverage)**:
+   - Run automated unit and integration tests (e.g. `npm test`).
+3. **Lane 3 (Manual / Scenario Proof)**:
+   - 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`)**:
+
+```markdown
+## 5. Verification Evidence
+- **Typecheck & Linter**: Passed (0 errors, 0 warnings)
+- **Automated Test Suites**: All tests passed (e.g. 12/12 passed, 0 failed)
+- **Acceptance Criteria Verification**:
+  - [x] AC-1: {ผลการตรวจสอบเงื่อนไขที่ 1 ผ่าน 100%}
+  - [x] AC-2: {ผลการตรวจสอบเงื่อนไขที่ 2 ผ่าน 100%}
+- **Manual Verification Guide**:
+  - *Where to go*: `http://localhost:3000/api/auth`
+  - *Action*: Send POST request with test credentials
+  - *Expected Result*: Received HTTP 200 with valid JWT token
+```
+
+### 4. Update Workspace Status
+Update `devflow/context/current-stage.md`:
+- `Current Stage`: `check (Fast-Track -> Verification Passed -> Ready for /complete)`
+
+### 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}`)

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

@@ -0,0 +1,73 @@
+---
+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."
+argument-hint: "{running-id or workspace path}"
+---
+
+# Fast-Track: Complete (Blueprint Mode)
+
+$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**.
+
+## Invocations & Aliases
+
+- `/complete`: Complete current active run
+- `/complete {running-id}`: Complete specified running ID
+- `$complete`: Codex CLI invocation
+
+## Fast-Track Mainline Workflow
+
+```text
+/spec ──▶ /implement ──▶ /check ──▶ /complete
+```
+
+## Behavior & Contract
+
+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`.
+3. Confirm:
+   - All checklist items in `## 3. Implementation Checklist` are marked `- [x]`.
+   - `## 5. Verification Evidence` contains passing verification results.
+
+### 2. Final Safety Pass & Changelog
+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`)**:
+
+```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.
+```
+Update header status in `spec.md`: `> **Status**: Completed`.
+
+### 4. 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. Close Active Run
+Update `devflow/context/current-stage.md`:
+- `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})`
+- `Last Updated`: `{YYYY-MM-DD}`
+
+### 7. Output Completion Report
+Report to the user:
+- Run successfully completed and merged
+- Living Spec path: `devflow/runs/{RUNNING_ID}/spec.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/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-implement` ➔ `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-implement {RUNNING_ID}`.
+     - If at `40-implement.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-implement` | `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-implement` - 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/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` ได้ทันที"