@jakkrichm/create-nexus-devflow 2.0.13 → 2.0.14

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/overview/SKILL.md

@@ -0,0 +1,114 @@
+---
+name: overview
+description: "[Devflow] Scan codebase architecture, data models, and shipped history to synthesize or refresh devflow/context/project-overview.md as the living source of truth."
+---
+
+# overview - Living Context Synthesis & Sync
+
+Where this sits in the workflow:
+
+```text
+codebase + devflow/history/HISTORY.md  ->  [overview]  ->  devflow/context/project-overview.md  ->  00-discover / 10-define / 20-spec
+(reality & shipped runs)                    (sync &         (living source of truth)             (informed planning)
+                                             synthesize)
+```
+
+`overview` is the context synchronization and synthesis engine for Nexus-DevFlow. It inspects the actual codebase (manifest, dependencies, directory layout, models/schemas, entry points) along with the completed delivery history (`devflow/history/HISTORY.md` and `devflow/runs/`) to build or refresh `devflow/context/project-overview.md`.
+
+It ensures that `project-overview.md` remains a **Living Source of Truth** that evolves alongside your software, rather than a stale artifact left behind after onboarding.
+
+## Usage
+
+```text
+/overview
+$overview
+overview
+```
+
+Use this when:
+- Multiple delivery runs (`RUN-xxx`) have shipped and `project-overview.md` needs to reflect newly added capabilities.
+- New database schemas, ORM models, or API boundaries were introduced.
+- Major dependencies or architectural patterns were added or modified.
+- After completing `70-release` to keep project context perfectly aligned.
+- Preparing for a new initiative or discovery pass.
+
+---
+
+## Process
+
+### Step 1 - Scan Reality (Codebase Survey)
+
+Inspect the actual codebase to establish hard facts:
+
+1. **Manifest & Tooling**:
+   - Read `package.json`, `pyproject.toml`, `go.mod`, `Cargo.toml`, `pom.xml`, or `Gemfile`.
+   - Identify language versions, primary framework, state management, and build tools.
+2. **Directory Architecture**:
+   - Map high-level directory layout (`src/`, `app/`, `api/`, `lib/`, `components/`, etc.).
+   - Identify major modules, entry points, and routing conventions.
+3. **Concrete Data Models & Schemas**:
+   - Search for ORM schemas (`schema.prisma`, Drizzle schemas, TypeORM entities, SQLAlchemy models, Zod schemas, or core TypeScript types).
+   - Extract entity names, core fields, relationships, and invariants.
+4. **Verified Commands**:
+   - Inspect package scripts (`dev`, `build`, `test`, `lint`, `check`, `verify`).
+
+---
+
+### Step 2 - Scan History (Delivered Capabilities)
+
+Inspect DevFlow history records:
+
+1. Read `devflow/history/HISTORY.md` for completed and released milestones.
+2. Scan completed delivery runs in `devflow/runs/` to extract shipped user-visible capabilities and core system features.
+
+---
+
+### Step 3 - Synthesize `project-overview.md`
+
+Write or update `devflow/context/project-overview.md` following standard structure:
+
+```markdown
+# Project Overview & Source of Truth
+
+> Living context artifact automatically synchronized with codebase reality and DevFlow delivery history.
+
+## 1. Project Purpose & Target Users
+- High-level summary of what the system does, who it serves, and the core problem it solves.
+
+## 2. Architecture & Directory Layout
+- Visual directory layout tree with short descriptions for major modules and boundaries.
+
+## 3. Technology Stack & Key Tooling
+- Frontend, Backend, Database, ORM, Testing frameworks, CI/CD, and Package Manager.
+
+## 4. Concrete Data Models & Entities
+- Field-level definitions of major entities, types, and relationships.
+
+## 5. Shipped Capabilities & Key Modules
+- Consolidated list of active features and subsystems verified in the codebase.
+
+## 6. Verified Commands & Developer Workflow
+- Exact commands for Dev, Build, Test, Lint, and Verify.
+
+## 7. Known Architectural Focus Areas
+- Known technical debt, active migrations, or upcoming architectural focus points.
+```
+
+---
+
+### Step 4 - Review & Report
+
+Present a concise summary of the sync:
+- Models or entities detected and added
+- Shipped capabilities refreshed from history
+- Stack and tooling updates
+- Any inconsistencies or gaps found between code and documentation
+
+---
+
+## Rules & Guardrails
+
+1. **Grounded in Reality**: Never invent non-existent packages, fictional data models, or unverified endpoints. Everything in `project-overview.md` must be traceable to real code or recorded history.
+2. **Preserve User Intent**: Do not erase custom business rules or user-written notes. Integrate new facts smoothly around existing intent.
+3. **Concrete Over Vague**: Provide actual model names, field types, and route paths rather than vague one-line summaries.
+4. **Non-Destructive**: `overview` only writes to `devflow/context/project-overview.md`. It never modifies source code, runs migrations, or touches git history.

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

@@ -0,0 +1,45 @@
+---
+name: report-html
+description: "[Devflow] Standalone HTML Report Generator - render an interactive standalone HTML dashboard from spec.md or 60-report.md on demand."
+argument-hint: "{running-id or workspace path}"
+---
+
+# Standalone: Report HTML
+
+$ARGUMENTS
+
+Standalone companion command to generate an interactive, self-contained HTML report dashboard on demand from either a Fast-Track `spec.md` or a Deep-Track `60-report.md`.
+
+> [!NOTE]
+> HTML reports are **never automatically generated** during normal mainline stages (`/complete` or `60-report`). Use this command whenever you or stakeholders wish to view or share an interactive web report.
+
+## Invocations & Aliases
+
+- `/report:html`: Generate HTML report for the active or most recent run
+- `/report:html {running-id}`: Generate HTML report for the specified running ID
+- `npm run report:html -- {running-id}`: CLI npm script invocation
+- `$report:html`: Codex CLI invocation
+
+## Behavior & Contract
+
+When invoked:
+
+### 1. Identify Target Run
+1. Locate target run directory in `devflow/runs/{running-id}` from argument or `devflow/context/current-stage.md`.
+2. Check for either:
+   - Fast-Track Living Spec: `devflow/runs/{RUNNING_ID}/spec.md` (or `blueprint.md`)
+   - Deep-Track Report Digest: `devflow/runs/{RUNNING_ID}/60-report.md`
+
+### 2. Render Interactive HTML Dashboard
+Execute the HTML generation engine:
+```bash
+npm run report:html -- {RUNNING_ID}
+```
+Or execute the renderer to transform Markdown into a styled, standalone HTML document:
+- Path: `devflow/runs/{RUNNING_ID}/report.html`
+
+### 3. Output
+Provide:
+- Generated HTML file path: `file:///devflow/runs/{RUNNING_ID}/report.html`
+- Summary of sections rendered (Spec, Plan, Progress, QA Evidence, Release Notes)
+- Instructions to open the file in any browser

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

@@ -0,0 +1,105 @@
+---
+name: spec
+description: "[Devflow] Fast-Track Spec stage in DevFlow (Blueprint Mode) - define, spec, plan, and create the single living spec.md contract."
+argument-hint: "{feature title, bug description, IDEA-xxx, or running-id}"
+---
+
+# Fast-Track: Spec (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`).
+
+## 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
+
+## Fast-Track Mainline Workflow
+
+```text
+/spec ──▶ /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}`)

package/template/AGENTS.md

@@ -1,10 +1,14 @@
-# Nexus-DevFlow 2.0 (Blueprint-Style Model)
+# Nexus-DevFlow 2.0 (Dual-Track Blueprint & Architect Model)
 
 Instructions for AI coding agents working in this project. This is the cross-tool entry point: Codex, Google Antigravity, Cursor, GitHub Copilot, Gemini CLI, Aider, Zed, Windsurf, and others read `AGENTS.md`. Claude Code reads `CLAUDE.md`, which imports this file (`@AGENTS.md`), so there is a single source of truth.
 
 ## What this is
 
-This project uses **Nexus-DevFlow**, an agentic stage-based workflow layer. To start a new project, scaffold the application first in an empty folder, then run `npx @jakkrichm/create-nexus-devflow` to overlay DevFlow onto your codebase.
+This project uses **Nexus-DevFlow**, an agentic workflow layer supporting **Dual-Track Delivery**:
+1. **🏎️ Fast-Track (Blueprint Mode - 4 Steps)**: High-velocity spec-driven loop driven by a **Single Living Spec (`spec.md`)**.
+2. **🏗️ Deep-Track (Architect Mode - 8 Steps)**: Full-lifecycle delivery pipeline with modular stage artifacts (`00-70`).
+
+To start a new project, scaffold the application first in an empty folder, then run `npx @jakkrichm/create-nexus-devflow` to overlay DevFlow onto your codebase.
 
 ## Read these for full context
 
@@ -25,66 +29,70 @@ Unused adapter families can be removed. Codex and Antigravity projects keep `.ag
 
 ### Universal Invocation & Agent Directives:
 
-1. **Canonical Command Names & AI Provider Invocation**: Each workflow stage and companion tool has exactly **one Canonical Name** (e.g. `00-discover`, `10-define`, `20-spec`, `30-plan`, `40-implement`, `50-verify`, `60-report`, `70-release`, `devflow`, `onboard`, `adopt`, `doctor`, `try`, `rollback`, `ci`, `brief`, `autopilot`). The way you invoke commands depends on your AI Provider / Tool:
-   - **Canonical Name (Plain text)**: Directly invoke or prompt the command by its standard name (e.g., `00-discover`, `devflow`).
-   - **Slash Prefix (`/`)**: For tools supporting slash commands (Claude Code, Google Antigravity, Gemini CLI), e.g., `/00-discover`, `/devflow`.
-   - **Dollar Prefix (`$`)**: For OpenAI Codex CLI or skill-invocation tools, e.g., `$00-discover`, `$devflow`.
+1. **Canonical Command Names & AI Provider Invocation**: Each workflow stage and companion tool has exactly **one Canonical Name** (e.g. `spec`, `implement`, `check`, `complete`, `00-discover`, `10-define`, `20-spec`, `30-plan`, `40-implement`, `50-verify`, `60-report`, `70-release`, `report-html`, `devflow`, `onboard`, `adopt`, `doctor`, `try`, `rollback`, `ci`, `brief`, `autopilot`). The way you invoke commands depends on your AI Provider / Tool:
+   - **Canonical Name (Plain text)**: Directly invoke or prompt the command by its standard name (e.g., `spec`, `devflow`).
+   - **Slash Prefix (`/`)**: For tools supporting slash commands (Claude Code, Google Antigravity, Gemini CLI), e.g., `/spec`, `/feature`, `/fix`, `/devflow`.
+   - **Dollar Prefix (`$`)**: For OpenAI Codex CLI or skill-invocation tools, e.g., `$spec`, `$devflow`.
 2. **OpenAI Codex & Non-Native CLI Tools**: In environments without automatic background skill discovery (such as OpenAI Codex CLI, Aider, or generic terminals), **you MUST use your file reading tool to inspect `.agents/skills/<skill>/SKILL.md` before executing the stage** to strictly follow its schema, artifact contract, and quality gates.
 3. **Google Antigravity & Claude Code**: Native skill engines automatically discover and surface `.agents/skills/` and `.claude/skills/`.
 4. **State-Aware Inspection**: When unsure what to do next, invoke `devflow` to automatically inspect `devflow/context/current-stage.md` and active runs in `devflow/runs/`.
-5. **Default Artifact & Communication Language (Thai)**: All generated markdown stage artifacts (`00-discover.md`, `10-define.md`, `20-spec.md`, `30-plan.md`, `40-implement.md`, `50-verify.md`, `60-report.md`, `70-release.md`) and user communication MUST default to **Thai (`th`)**, while code, technical terms, file paths, and identifiers remain in English.
+5. **Default Artifact & Communication Language (Thai)**: All generated markdown stage artifacts (`spec.md`, `00-discover.md`...`70-release.md`) and user communication MUST default to **Thai (`th`)**, while code, technical terms, file paths, and identifiers remain in English.
+
+---
+
+## 🏎️ Track 1: Fast-Track (Blueprint Mode - 4 Steps)
 
-## Timeline Workflow
+Recommended for 85% of daily work (features, bug fixes, UI improvements, iterative tasks):
 
 ```text
-00-discover -> 10-define -> 20-spec -> 30-plan -> 40-implement -> 50-verify -> 60-report -> 70-release
+/spec (or /feature, /fix) ──▶ /implement ──▶ /check ──▶ /complete
 ```
 
-### Mainline Stages:
+1. **`spec` (`/spec`, `/feature`, `/fix`)**:
+   - **Purpose**: Combines Discover, Define, Spec, and Plan into one unified step. Allocates sequential Running ID (`RUN-xxx`) and creates the **Single Living Spec (`spec.md`)**.
+   - **Artifact**: `devflow/runs/{running-id}-{slug}/spec.md`
+2. **`implement` (`/implement`)**:
+   - **Purpose**: Incrementally executes checklist tasks with TDD discipline and appends progress to `spec.md`.
+3. **`check` (`/check`)**:
+   - **Purpose**: Senior QA review, multi-lane verification matrix (Typecheck, Lint, Test suites, manual proof), and records evidence into `spec.md`.
+4. **`complete` (`/complete`)**:
+   - **Purpose**: Final safety pass, records Release Digest in `spec.md`, performs git merge, and closes the run without auto HTML generation.
 
-1. `00-discover`
-   - **Purpose**: Explore a request before delivery commitment without allocating a running ID.
-   - **Artifact**: `devflow/discoveries/{discovery-id}-{slug}/00-discover.md`
-   - **Gate**: Produces `Proceed`, `Defer`, or `Reject` decision.
+---
 
-2. `10-define`
-   - **Purpose**: Turn an approved discovery into one or more bounded delivery runs with stable scope and sequential Running IDs.
-   - **Artifact**: `devflow/runs/{running-id}-{slug}/10-define.md`
-   - **Gate**: Approved run map and explicit in-scope / out-of-scope boundaries.
+## 🏗️ Track 2: Deep-Track (Architect Mode - 8 Steps)
 
-3. `20-spec`
-   - **Purpose**: Formalize markdown-first delivery contract and testable acceptance criteria from a stable definition.
-   - **Artifact**: `devflow/runs/{running-id}-{slug}/20-spec.md`
-   - **Gate**: Unambiguous acceptance criteria and hard constraints.
+Recommended for large architectural epics, database migrations, and multi-agent coordination:
+
+```text
+00-discover ──▶ 10-define ──▶ 20-spec ──▶ 30-plan ──▶ 40-implement ──▶ 50-verify ──▶ 60-report ──▶ 70-release
+```
 
-4. `30-plan`
-   - **Purpose**: Transform `20-spec.md` into phased executable tasks with explicit test decisions (Required / Manual / Not Required).
-   - **Artifacts**: `30-plan.md`, `checklists/implementation-checklist.md`, `checklists/verification-checklist.md`
-   - **Gate**: Ordered dependencies, scoped subtasks, and TDD decisions.
+1. `00-discover`: Explore request before delivery commitment without allocating running ID (`00-discover.md`).
+2. `10-define`: Turn approved discovery into bounded delivery run(s) with sequential Running IDs (`10-define.md`).
+3. `20-spec`: Formalize markdown-first delivery contract & acceptance criteria (`20-spec.md`).
+4. `30-plan`: Breakdown spec into executable tasks with test decisions (`30-plan.md` + checklists).
+5. `40-implement`: Incremental task implementation behind review gates (`40-implement.md`).
+6. `50-verify`: Senior QA review & multi-lane verification checks (`50-verify.md`).
+7. `60-report`: Standardized markdown delivery digest (`60-report.md`).
+8. `70-release`: Release packaging, release notes, git merge, and deployment (`70-release.md`).
 
-5. `40-implement`
-   - **Purpose**: Execute planned tasks incrementally one scoped unit at a time behind review gates.
-   - **Artifact**: `40-implement.md` (and updated checklists)
-   - **Gate**: Code changes tested, verification recorded, deviations documented.
+---
 
-6. `50-verify`
-   - **Purpose**: Senior QA review and multi-lane validation check across functionality, regressions, and quality standards.
-   - **Artifact**: `50-verify.md` (optional `50-verify-impact.md`)
-   - **Gate**: Pass or return-to-implement decision with evidence.
+## 🌐 Standalone HTML Reporting Policy
 
-7. `60-report`
-   - **Purpose**: Produce the standardized final markdown and self-contained HTML summary report for the completed run.
-   - **Artifacts**: `60-report.md`, `60-report.html`
-   - **Gate**: Completed delivery digest ready for stakeholder review.
+> [!IMPORTANT]
+> **No Auto-Generated HTML**: Mainline flows (`/complete` and `60-report`) strictly output Markdown only.
+> When an interactive web dashboard is desired for presentation or sharing, invoke the standalone companion command:
+> `/report:html` (or `npm run report:html -- {RUNNING_ID}`).
 
-8. `70-release`
-   - **Purpose**: Package verified work for delivery, git merge, pull request, changelog update, or deployment.
-   - **Artifact**: `70-release.md`
-   - **Gate**: Safe handoff, release notes, and deployment readiness.
+---
 
-### Public Companion Commands:
+## Public Companion Commands
 
 - `devflow`: Flagship interactive guide, state inspector, and intent 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`: Initial stack detection and baseline setup for fresh/scaffolded projects.
 - `adopt`: Survey existing brownfield codebases and bootstrap DevFlow context.
 - `doctor`: Read-only health check for context files, adapters, commands, and workflow drift.
@@ -92,49 +100,38 @@ Unused adapter families can be removed. Codex and Antigravity projects keep `.ag
 - `rollback`: Safe feature/run reversal planner with dependency and commit risk analysis.
 - `ci`: Automatic GitHub Actions workflow (`.github/workflows/verify.yml`) setup and alignment.
 - `brief`: Read-only scope, dependency, and size pre-briefing before speccing a run.
-- `autopilot`: Optional explicit mode for one bounded spec/plan/implement/verify/report pass with checkpoint commits and review packet.
+- `autopilot`: Optional explicit mode for one bounded spec/plan/implement/verify/report pass.
 - `goal`: Route broad, open-ended goals before Discovery.
 - `brainstorm`: Structured divergent & convergent ideation without creating running IDs.
 - `research`: Conduct deep codebase or web research with source-backed citations.
 - `debug`: Root cause investigation before or during implementation without editing code.
-- `prd`: Product Requirements Document drafting before delivery commitment.
-- `issue-triage`: Intake, categorize, and prioritize incoming issues and bug reports.
-- `security-review`: High-severity vulnerability and security review.
-- `wiki`: Knowledge base management and ingestion under `devflow/wiki/`.
+- `overview`: Refresh `devflow/context/project-overview.md`.
+- `wiki`: Knowledge base management under `devflow/wiki/`.
 - `check-for-updates`: Verify or upgrade DevFlow setup.
 - `help`: Routing and process assistance across DevFlow workflows.
 
-## Invocation Reference
+---
 
-> **Note on AI Providers**: Commands use a single Canonical Name. Use the prefix appropriate for your tool (`/` for Claude/Antigravity, `$` for Codex, or plain text).
+## Invocation Reference
 
-| Stage / Category | Canonical Name | Claude / Antigravity (`/`) | OpenAI Codex (`$`) | Purpose / Action |
+| Track / Category | Canonical Name | Claude / Antigravity (`/`) | OpenAI Codex (`$`) | Purpose / Action |
 | :--- | :--- | :--- | :--- | :--- |
-| **Setup (Fresh)** | `onboard` | `/onboard` | `$onboard` | Detect tech stack and establish initial project baseline |
-| **Adopt (Exist)** | `adopt` | `/adopt` | `$adopt` | Adopt existing brownfield codebase into DevFlow |
-| **Diagnostics** | `doctor` | `/doctor` | `$doctor` | Read-only health check for configs, tools, and drift |
-| **Manual QA** | `try` | `/try` | `$try` | Step-by-step manual testing guide for human verification |
-| **Reversal** | `rollback` | `/rollback` | `$rollback` | Reversal planner with dependency & commit risk analysis |
-| **CI Setup** | `ci` | `/ci` | `$ci` | Generate GitHub Actions automated verify workflow |
-| **Pre-Check** | `brief` | `/brief` | `$brief` | Read-only scope, dependency, and size pre-briefing |
-| **Autopilot** | `autopilot` | `/autopilot` | `$autopilot` | Bounded autonomous spec/plan/implement/verify pass |
-| **Stage 00** | `00-discover` | `/00-discover` | `$00-discover` | Explore request and decide Proceed, Defer, or Reject |
-| **Stage 10** | `10-define` | `/10-define` | `$10-define` | Turn approved discovery into bounded delivery run(s) |
-| **Stage 20** | `20-spec` | `/20-spec` | `$20-spec` | Formal markdown delivery contract & acceptance criteria |
-| **Stage 30** | `30-plan` | `/30-plan` | `$30-plan` | Breakdown spec into executable tasks with test decisions |
-| **Stage 40** | `40-implement` | `/40-implement` | `$40-implement` | Implement tasks in small reviewable increments |
-| **Stage 50** | `50-verify` | `/50-verify` | `$50-verify` | Senior QA review & multi-lane verification checks |
-| **Stage 60** | `60-report` | `/60-report` | `$60-report` | Standalone markdown & HTML summary report |
-| **Stage 70** | `70-release` | `/70-release` | `$70-release` | Package for delivery, git merge, PR, or deployment |
+| **Fast: Spec** | `spec` | `/spec` / `/feature` / `/fix` | `$spec` / `$feature` / `$fix` | 4-step Fast-Track spec & living spec creation (supports `IDEA-xxx`) |
+| **Fast: Implement** | `implement` | `/implement` | `$implement` | Fast-Track incremental execution with TDD |
+| **Fast: Check** | `check` | `/check` | `$check` | Fast-Track QA review & multi-lane verification |
+| **Fast: Complete** | `complete` | `/complete` | `$complete` | Fast-Track safety pass, release digest & git merge |
+| **Idea Capture** | `idea` | `/idea` | `$idea` | Quick idea capture and AI feasibility enrichment |
+| **HTML Report** | `report-html` | `/report:html` | `$report:html` | Standalone interactive HTML dashboard generator |
+| **Deep: 00** | `00-discover` | `/00-discover` | `$00-discover` | Explore request and decide Proceed, Defer, or Reject |
+| **Deep: 10** | `10-define` | `/10-define` | `$10-define` | Turn approved discovery into bounded delivery run(s) |
+| **Deep: 20** | `20-spec` | `/20-spec` | `$20-spec` | Formal markdown delivery contract & acceptance criteria |
+| **Deep: 30** | `30-plan` | `/30-plan` | `$30-plan` | Breakdown spec into executable tasks with test decisions |
+| **Deep: 40** | `40-implement` | `/40-implement` | `$40-implement` | Implement tasks in small reviewable increments |
+| **Deep: 50** | `50-verify` | `/50-verify` | `$50-verify` | Senior QA review & multi-lane verification checks |
+| **Deep: 60** | `60-report` | `/60-report` | `$60-report` | Standalone markdown summary report |
+| **Deep: 70** | `70-release` | `/70-release` | `$70-release` | Package for delivery, git merge, PR, or deployment |
 | **Router** | `devflow` | `/devflow` | `$devflow` | Interactive guide, state inspector, and intent router |
 
-## Mainline Rules
-
-1. Numbered workflows exist only for the linear mainline.
-2. Mainline numbers must move from lower to higher with no backward jump.
-3. If a command is not a true mainline state, do not give it a number.
-4. Companion commands may be suggested by a mainline workflow but do not replace that workflow.
-
 ## Commands
 
 - Dev Server: `npm run dev`

package/template/devflow/context/ai-interaction.md

@@ -32,3 +32,4 @@
 - Run `/20-Spec` and `/30-Plan` to establish formal delivery specifications and execution plans.
 - Run `/40-Implement` for step-by-step code implementation with evidence.
 - Run `/50-Verify`, `/60-Report`, and `/70-Release` for quality verification, reporting, and release packaging.
+- Use **Fast-Track / Quick-Fix mode** for minor hotfixes to skip heavy ceremony while keeping test evidence.

package/template/devflow/context/coding-standards.md

@@ -1,27 +1,40 @@
-# Coding Standards
+# Coding Standards & Guidelines
 
-> Project conventions and rules to follow during development.
-> Run `/onboard` (or `/adopt` for existing codebases) to tune these standards to your specific stack.
+General engineering standards for code, tests, and documentation in Nexus-DevFlow.
 
-## Architecture and Conventions
+## 1. Code Quality & Architecture
 
-- Write clean, modular, and maintainable code with clear single responsibilities.
-- Prefer TypeScript and explicit interfaces where available.
-- Keep dependencies lean and justified.
+- Write clear, self-documenting code with single-responsibility functions.
+- Avoid unnecessary complexity (prefer simple solutions over indirect abstractions).
+- Maintain type safety and static validation across module boundaries.
+- Treat `project-overview.md` as the single source of truth for concrete data models and entity definitions.
 
-## Code Organization & Style
+## 2. Testing & Empirical Proof Standards
 
-- Structure source code following framework-native conventions.
-- Keep functions focused and avoid deeply nested logic.
-- Use consistent naming conventions (camelCase for functions/variables, PascalCase for components/types).
+- **Unit Test Mandate**: Any logic modification or bug fix must be accompanied by new or updated unit tests.
+- **Empirical Proof Contract**: Never claim "passed", "verified", or "working" without citing exact command outputs, test run reports, route responses, logs, or screenshots.
+- **Manual Try Guide**: Every delivery run must provide a human-testable Try Guide ("Where to go", "What to click", "What to expect") for manual validation.
 
-## Error Handling & Security
+## 3. Findings Ledger & Quality Gates (`findings.md`)
 
-- Handle errors explicitly and provide meaningful error messages.
-- Never hardcode credentials, secrets, or API keys in source code.
-- Sanitize and validate all user inputs.
+- All audit, security, and verification issues must be tracked in `devflow/context/findings.md`.
+- **Finding State Machine**:
+  - `open`: Confirmed defect not yet repaired.
+  - `fixed`: Repaired in code, pending verification.
+  - `closed`: Verified in `50-verify` as completely resolved without regressions.
+  - `accepted`: Waived with recorded user rationale.
+  - `invalid`: Proven non-issue with concrete evidence.
+- **P0/P1 Blockers**: P0 and P1 findings in `open` or `fixed` status block `70-release` unconditionally. `fixed` status must be promoted to `closed` via `50-verify` re-examination.
 
-## Testing & Quality
+## 4. Git Workflow & Release Safety
+ 
+- Commit messages follow conventional/imperative format (e.g., `feat(RUN-007): ...`).
+- Feature branches follow `feature/{slug}-{running-id}` or `fix/{slug}-{running-id}`.
+- **2-Stage Release Approvals**: Explicit consent to merge into `main` is strictly separate from consent to `git push` to remote repositories or deploy to production.
 
-- Follow the TDD workflow for behavior-changing code units.
-- Run tests and linting before completing features or fixes.
+## 5. Fast-Track & Quick-Fix Guidelines (Lean Mode)
+
+- For trivial bug fixes, typo corrections, or single-file non-architectural changes, developers and agents may use the **Quick-Fix Fast-Track**:
+  - Consolidate Discovery, Define, and Spec into an inline fix brief (`devflow/runs/{fix-id}/fix-brief.md`).
+  - Jump directly to `40-implement` (with reproduction unit test) ➔ `50-verify` ➔ `70-release`.
+  - Avoid creating heavy redundant documentation for changes under 20 lines of code while preserving Empirical Proof and Unit Test requirements.

package/template/devflow/context/current-stage.md

@@ -2,6 +2,6 @@
 
 - **Active Discovery ID**: None
 - **Active Running ID**: None
-- **Current Stage**: Idle
-- **Last Completed Run**: None
-- **Last Updated**: -
+- **Current Stage**: Ready for new work (Fast-Track: `/spec`, `/feature`, `/fix`, or Deep-Track: `00-discover`, Idea: `/idea`)
+- **Last Completed Run**: RUN-016-idea-capture-inbox-and-status-integration (2026-08-20)
+- **Last Updated**: 2026-08-20

package/template/devflow/context/findings.md

@@ -1,9 +1,13 @@
-# Findings Ledger
+# Audit Findings Ledger
 
-> Review findings raised by `/security-review` or QA audits.
-> Resolved findings are tracked with durable IDs.
+Summary of audit findings, quality checks, security bugs, and debt tracked across DevFlow runs.
 
-- **Total Open P0/P1**: 0
-- **Total Tracked**: 0
+## Open Findings
 
-_No findings recorded._
+| ID | Severity | Category | Title | Discovered Run | Status |
+| :- | :--- | :--- | :--- | :--- | :--- |
+
+## Resolved Findings
+
+| ID | Severity | Category | Title | Resolved Run | Date |
+| :- | :--- | :--- | :--- | :--- | :--- |