@jakkrichm/create-nexus-devflow 2.0.8 → 2.0.10

package/template/.claude/skills/test-execution-and-coverage/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: test-execution-and-coverage
-description: Generate missing tests, run existing tests, and summarize coverage and failures. Use when implementation or verification needs explicit testing evidence beyond a general TDD reminder.
+description: "[Devflow] Generate missing tests, run existing tests, and summarize coverage and failures. Use when implementation or verification needs explicit testing evidence beyond a general TDD reminder."
 ---
 
 # Test Execution And Coverage
@@ -11,8 +11,8 @@ This skill complements TDD by handling test generation, execution, and persisten
 
 ## When to Use
 
-- During `/40-Implement` when tests need to be added
-- During `/50-Verify` when the test suite must be run and summarized
+- During `40-implement` when tests need to be added
+- During `50-verify` when the test suite must be run and summarized
 - During `Debug` when a bug needs a reproduction test
 
 ## Process
@@ -41,8 +41,8 @@ Use `.agent/resources/schemas/test_report.template.md` when saving a reusable re
 
 ### 4. Route Back
 
-- `/50-Verify` when tests support formal verification
-- `/40-Implement` when missing or failing tests require code changes
+- `50-verify` when tests support formal verification
+- `40-implement` when missing or failing tests require code changes
 - `Debug` when failures need RCA
 
 ## Output

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

@@ -0,0 +1,108 @@
+---
+name: try
+description: "[Devflow] Generate human manual QA review walkthrough guide (where to go, what to click, what to expect)."
+---
+
+# try - Manual QA & Review Walkthrough Guide
+
+Where this sits in the workflow:
+
+```text
+40-implement or 50-verify or 60-report  ->  [try]  ->  human review & verification
+(work implemented / verified)                  (manual    (where to go,
+                                               steps)     what to click)
+```
+
+`50-verify` proves behavior from automated QA and test runs. `try` gives the user and testers an actionable, step-by-step manual walkthrough: start this command, open this route, click these controls, expect this result, and watch for these failure signs.
+
+It is always **read-only 100%**. It does not edit files, install dependencies, commit, merge, push, or run destructive commands.
+
+## Input
+
+Optional scope:
+
+- **no argument**: use the active run in `devflow/context/current-stage.md` (or the latest completed run under `devflow/runs/`)
+- `latest`: use the most recent completed run in `devflow/runs/`
+- a run ID or path: e.g. `try RUN-002-add-onboard-adopt-doctor-skills`
+- a specific route, endpoint, or CLI command: focus the walkthrough on that surface
+
+If there is no active run and no run history, ask what change or feature the user wants to test manually.
+
+## Step 1 - Find The Work To Explain
+
+Read:
+
+- `AGENTS.md` (Commands section)
+- `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)
+- 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.
+
+## Step 2 - Identify How To Run The App
+
+Check the Commands section in `AGENTS.md`. Adapt to the project type:
+
+- **Web app**: dev server command (e.g. `npm run dev`), local URL (e.g. `http://localhost:3000`), and specific route/screen.
+- **Server / API**: start command, base URL, endpoint, HTTP method, payload, and expected response shape.
+- **CLI**: exact CLI command, flags, arguments, and expected terminal output.
+- **Library / Module**: sample usage snippet, REPL call, or interactive test command.
+- **Fullstack / Microservices**: minimal combined startup commands (e.g. backend + frontend).
+
+If a startup command is missing or unclear in `AGENTS.md`, report that as a configuration gap rather than guessing.
+
+## Step 3 - Produce The Manual Walkthrough Guide
+
+Format the guide with these 5 standard sections:
+
+1. **1. Start** - exact command(s) to start the system and where to run them.
+2. **2. Open** - URL(s), screens, tabs, API endpoints, or terminal locations.
+3. **3. Do** - specific clicks, form inputs, toggles, selections, or arguments.
+4. **4. Expect** - expected visible UI change, response payload, state change, output, or absence of errors.
+5. **5. Watch For** - common failure symptoms, console errors, network 4xx/5xx errors, stale state, layout breakage, or safety warnings.
+
+### Example Walkthrough Style:
+
+```markdown
+### 1. Start
+Run `npm run dev` in the project root.
+
+### 2. Open
+Navigate to `http://localhost:3000/dashboard/reports`.
+
+### 3. Do
+1. Click the **"Export Report"** button in the top right.
+2. Select **"Format: HTML"** from the dropdown.
+3. Click **"Download"**.
+
+### 4. Expect
+- A new file `report.html` is downloaded.
+- The UI displays a green success toast: *"Report exported successfully"*.
+- The downloaded HTML file opens in the browser with full styling and charts.
+
+### 5. Watch For
+- Spinner hanging indefinitely without downloading.
+- Console error related to `Blob` or `URL.createObjectURL`.
+- Broken styling or unrendered Mermaid charts in the exported HTML.
+```
+
+## Step 4 - Include Confidence, Best Signal & Gaps
+
+Conclude with:
+
+- **Best Signal**: the single most critical action the user should try first to confirm functionality.
+- **Edge Cases & Error Flows**: optional secondary checks (e.g. invalid input, empty state, network failure).
+- **Gaps & Assumptions**: anything the guide cannot know for certain (e.g. seed credentials, third-party API keys, required database fixtures).
+
+## Rules
+
+- **Strictly Read-Only**: Never edit code, commit, push, install packages, or mutate repository state.
+- **Do Not Run Automatically**: Do not launch the server or run commands unless the user explicitly instructs you to do so in the chat.
+- **Be Concrete & Specific**: Provide exact URLs, button labels, and payloads.
+- **Acknowledge Uncertainty**: If a route or behavior is not specified in the spec, state it clearly as an assumption.
+
+## Output Formatting
+
+Follow the project conventions in `devflow/context/ai-interaction.md`: concise, scannable markdown with numbered steps and clear bold headers.

package/template/.claude/skills/type-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: type-design
-description: Analyzes type and interface design for encapsulation, invariant expression, usefulness, and enforcement. Use when introducing new types, reviewing PRs with type changes, or refactoring domain models.
+description: "[Devflow] Analyzes type and interface design for encapsulation, invariant expression, usefulness, and enforcement. Use when introducing new types, reviewing PRs with type changes, or refactoring domain models."
 ---
 
 # Type Design

package/template/.claude/skills/ui-ux-pro-max/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ui-ux-pro-max
-description: AI-powered design intelligence with 50+ styles, 95+ color palettes, and automated design system generation. Use when designing, building, or reviewing UI/UX.
+description: "[Devflow] AI-powered design intelligence with 50+ styles, 95+ color palettes, and automated design system generation. Use when designing, building, or reviewing UI/UX."
 ---
 
 # UI/UX Pro Max (Design Intelligence)

package/template/.claude/skills/using-agent-skills/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: using-agent-skills
-description: Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.
+description: "[Devflow] Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked."
 ---
 
 # Using Agent Skills

package/template/.claude/skills/verification-orchestration/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: verification-orchestration
-description: Coordinate multi-lane QA, specialist review, test planning, and verification follow-up. Use when /50-Verify needs more structure than a single pass and the team needs a QA matrix or specialist routing.
+description: "[Devflow] Coordinate multi-lane QA, specialist review, test planning, and verification follow-up. Use when 50-verify needs more structure than a single pass and the team needs a QA matrix or specialist routing."
 ---
 
 # Verification Orchestration
@@ -11,7 +11,7 @@ This skill structures complex verification work across multiple QA lanes without
 
 ## When to Use
 
-- `/50-Verify` is too broad for a single simple pass
+- `50-verify` is too broad for a single simple pass
 - the change needs correctness, regression, security, performance, and UX checks together
 - the team needs specialist routing for QA
 
@@ -54,8 +54,8 @@ Use `.agent/resources/schemas/qa_orchestration.template.md` when saving a reusab
 
 ### 5. Route Back
 
-- `/50-Verify` when the QA matrix strengthens verification evidence
-- `/40-Implement` when actionable fixes are required
+- `50-verify` when the QA matrix strengthens verification evidence
+- `40-implement` when actionable fixes are required
 - `Followup` when findings become new scope
 
 ## Output

package/template/.claude/skills/vulnerability-scanner/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: vulnerability-scanner
-description: Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.
+description: "[Devflow] Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization."
 allowed-tools: Read, Glob, Grep, Bash
 ---
 

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

@@ -1,6 +1,6 @@
 ---name: wiki
 
-description: DevFlow Wiki - Ingest, query, lint, and promote compiled project or framework knowledge.
+description: "[Devflow] Knowledge base management, ingestion, linting, and querying under devflow/wiki/."
 ---
 # Wiki
 
@@ -31,9 +31,9 @@ Use `Wiki` when:
 
 Preferred DevFlow 2.0 pairing:
 
-- after `/50-Verify`
-- after `/70-Release`
-- after `/60-Report`
+- after `50-verify`
+- after `70-release`
+- after `60-report`
 - after meaningful `Debug` or review output
 
 ## Process
@@ -131,7 +131,7 @@ Return:
 
 - Classification: Companion command
 - Mainline status: Knowledge system command, not a numbered stage
-- Typical entry points: after `/50-Verify`, `/60-Report`, `/70-Release`, `Debug`, `Insight`, `PR-Review`
+- Typical entry points: after `50-verify`, `60-report`, `70-release`, `Debug`, `Insight`, `PR-Review`
 - Typical handoff targets: return to the originating stage or finish as documentation-only work
 
 ## Sources
@@ -139,11 +139,11 @@ Return:
 - `AGENTS.md`
 - `.agent/resources/schemas/wiki_page.template.md`
 - `.agent/resources/schemas/wiki_project_index.template.md`
-- Related commands: `/50-Verify`, `/60-Report`, `/70-Release`, `Debug`, `Insight`, `PR-Review`, `Help`
+- Related commands: `50-verify`, `60-report`, `70-release`, `Debug`, `Insight`, `PR-Review`, `Help`
 
 ## Next Workflow Recommendation
 
 - **Primary**: return to the stage or artifact flow that produced the reusable knowledge
 - **Why**: `Wiki` compiles lessons after the source work is already validated
-- **Common routes**: `/60-Report`, `/70-Release`, or `/50-Verify`
+- **Common routes**: `60-report`, `70-release`, or `50-verify`
 

package/template/.claude/skills/workflow-documentation-sync/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: workflow-documentation-sync
-description: Enforces the synchronization and comprehensive update of documentation, manuals, usage guides, and examples whenever a new workflow is introduced or modified in the project. Use when introducing new workflows or changing existing ones.
+description: "[Devflow] Enforces the synchronization and comprehensive update of documentation, manuals, usage guides, and examples whenever a new workflow is introduced or modified in the project. Use when introducing new workflows or changing existing ones."
 ---
 
 # Workflow Documentation Sync
@@ -27,7 +27,7 @@ Whenever a workflow is added or modified, compile the list of documents that mus
 
 ### Step 2: Extract Workflow Metadata
 Identify the exact interface changes:
-- What is the **Command trigger**? (e.g., `/70-Release` or `Brainstorm`)
+- What is the **Command trigger**? (e.g., `70-release` or `Brainstorm`)
 - What are the **Arguments**? (e.g., Target Branch, default main)
 - What is the **Process flow**? (Pre-flight -> Execution -> Cleanup)
 - What are the **Mandatory Rules**? (e.g., Enforced branch checks)

package/template/AGENTS.md

@@ -25,10 +25,14 @@ Unused adapter families can be removed. Codex and Antigravity projects keep `.ag
 
 ### Universal Invocation & Agent Directives:
 
-1. **Universal Command Names**: You can invoke workflows using plain stage names (`00-discover`, `10-define`, `20-spec`, `30-plan`, `40-implement`, `50-verify`, `60-report`, `70-release`, `devflow`), semantic aliases (`discover`, `define`, `spec`, `plan`, `implement`, `verify`, `report`, `release`, `status`), slash commands (`/00-discover`, `/devflow`), Codex skill format (`$00-discover`, `$spec`), or natural language intents (e.g., "start discovery", "write spec", "implement next step").
+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`.
 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` (or `/devflow`, `$devflow`) to automatically inspect `devflow/context/current-stage.md` and active runs in `devflow/runs/`.
+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.
 
 ## Timeline Workflow
 
@@ -38,52 +42,57 @@ Unused adapter families can be removed. Codex and Antigravity projects keep `.ag
 
 ### Mainline Stages:
 
-1. `00-discover` (alias: `discover`, `/00-discover`, `$00-discover`)
+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` (alias: `define`, `/10-define`, `$10-define`)
+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.
 
-3. `20-spec` (alias: `spec`, `/20-spec`, `$20-spec`)
+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.
 
-4. `30-plan` (alias: `plan`, `/30-plan`, `$30-plan`)
+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.
 
-5. `40-implement` (alias: `implement`, `/40-implement`, `$40-implement`)
+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` (alias: `verify`, `/50-verify`, `$50-verify`)
+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.
 
-7. `60-report` (alias: `report`, `/60-report`, `$60-report`)
+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.
 
-8. `70-release` (alias: `release`, `/70-release`, `$70-release`)
+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:
 
-- `devflow` (alias: `status`, `/devflow`, `$devflow`): Flagship interactive guide, state inspector, and intent router.
-- `onboard` (alias: `/onboard`, `$onboard`): Initial stack detection and baseline setup for fresh/scaffolded projects.
-- `adopt` (alias: `/adopt`, `$adopt`): Survey existing brownfield codebases and bootstrap DevFlow context.
-- `doctor` (alias: `/doctor`, `$doctor`): Read-only health check for context files, adapters, commands, and workflow drift.
+- `devflow`: Flagship interactive guide, state inspector, and intent router.
+- `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.
+- `try`: Step-by-step human manual QA review guide (where to go, what to click, what to expect).
+- `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.
 - `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.
@@ -97,20 +106,27 @@ Unused adapter families can be removed. Codex and Antigravity projects keep `.ag
 
 ## Invocation Reference
 
-| Stage / Command | Normal Name | Semantic Alias | OpenAI Codex | Slash Command | Natural Language |
-| :--- | :--- | :--- | :--- | :--- | :--- |
-| **Setup (Fresh)**| `onboard` | `setup` | `$onboard`, `$setup` | `/onboard` | "onboard project", "setup devflow" |
-| **Adopt (Exist)**| `adopt` | `bootstrap` | `$adopt`, `$bootstrap` | `/adopt` | "adopt codebase", "bootstrap devflow" |
-| **Diagnostics** | `doctor` | `health` | `$doctor`, `$health` | `/doctor` | "doctor check", "diagnose devflow" |
-| **Stage 00** | `00-discover` | `discover` | `$00-discover`, `$discover` | `/00-discover` | "start discovery", "explore request" |
-| **Stage 10** | `10-define` | `define` | `$10-define`, `$define` | `/10-define` | "define run scope", "allocate run" |
-| **Stage 20** | `20-spec` | `spec` | `$20-spec`, `$spec` | `/20-spec` | "write spec", "create delivery contract" |
-| **Stage 30** | `30-plan` | `plan` | `$30-plan`, `$plan` | `/30-plan` | "plan tasks", "breakdown plan" |
-| **Stage 40** | `40-implement` | `implement` | `$40-implement`, `$implement` | `/40-implement` | "implement step", "build task" |
-| **Stage 50** | `50-verify` | `verify` | `$50-verify`, `$verify` | `/50-verify` | "verify QA", "run validation" |
-| **Stage 60** | `60-report` | `report` | `$60-report`, `$report` | `/60-report` | "generate report", "summarize run" |
-| **Stage 70** | `70-release` | `release` | `$70-release`, `$release` | `/70-release` | "package release", "prepare PR/deploy" |
-| **Router** | `devflow` | `status` | `$devflow`, `$status` | `/devflow` | "what to do next", "check progress" |
+> **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).
+
+| Stage / 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 |
+| **Router** | `devflow` | `/devflow` | `$devflow` | Interactive guide, state inspector, and intent router |
 
 ## Mainline Rules