@jakkrichm/create-nexus-devflow 2.0.9 → 2.0.10

package/template/.claude/skills/release-git-operations/SKILL.md

@@ -27,8 +27,8 @@ This skill should reuse and align with:
 
 ## When to Use
 
-- After `/50-Verify` when verified work is ready for packaging
-- During `/70-Release` when the team needs commit, PR, merge, deployment, or changelog support after the report is already aligned
+- After `50-verify` when verified work is ready for packaging
+- During `70-release` when the team needs commit, PR, merge, deployment, or changelog support after the report is already aligned
 - When release communication must be built from markdown-first stage artifacts
 
 ## Supported Modes
@@ -83,9 +83,9 @@ Read the minimum required artifacts:
 
 ### 3. Route Back
 
-- return to `/70-Release` when packaging is still in progress
-- return to `/60-Report` when communication is the remaining task
-- return to `/40-Implement`, `/50-Verify`, or `PR-Followup` if release blockers are discovered
+- return to `70-release` when packaging is still in progress
+- return to `60-report` when communication is the remaining task
+- return to `40-implement`, `50-verify`, or `PR-Followup` if release blockers are discovered
 
 ## Output
 

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

@@ -30,12 +30,12 @@ Use `prototype` when the fastest reliable evidence is a runnable throwaway exper
 
 Preferred DevFlow 2.0 pairing:
 
-- from `/00-Discover`
-- from `/10-Define`
-- from `/20-Spec`
-- from `/50-Verify` when validating a claim or implementation choice
+- from `00-discover`
+- from `10-define`
+- from `20-spec`
+- from `50-verify` when validating a claim or implementation choice
 
-When invoked with a Discovery ID, link the research report to that discovery and return to `/00-Discover {discovery_id}` so Discover can synthesize the evidence and make the decision. Research must not allocate a Running ID.
+When invoked with a Discovery ID, link the research report to that discovery and return to `00-discover {discovery_id}` so Discover can synthesize the evidence and make the decision. Research must not allocate a Running ID.
 
 ---
 
@@ -125,19 +125,19 @@ Research whether this API version is compatible
 
 - Classification: Companion command
 - Mainline status: Not a numbered stage
-- Typical entry points: `/00-Discover`, `/10-Define`, `/20-Spec`, `/30-Plan`
+- Typical entry points: `00-discover`, `10-define`, `20-spec`, `30-plan`
 - Typical handoff targets: return to the stage that asked for the evidence
 
 ## Sources
 
 - `AGENTS.md`
 - `.agent/resources/schemas/research.template.md`
-- Related commands: `/00-Discover`, `/10-Define`, `/20-Spec`, `/30-Plan`, `Spec-Research`, `Agent`
+- Related commands: `00-discover`, `10-define`, `20-spec`, `30-plan`, `Spec-Research`, `Agent`
 - Support skills: `prototype`, `spec-research`, `competitor-analysis`, `insight-capture`
 
 ## Next Workflow Recommendation
 
-- Default: return to the stage that asked for evidence; for discovery-owned research this is `/00-Discover {discovery_id}`
-- Common routes: `/10-Define`, `/20-Spec`, `/30-Plan`, or `/50-Verify`
+- Default: return to the stage that asked for evidence; for discovery-owned research this is `00-discover {discovery_id}`
+- Common routes: `10-define`, `20-spec`, `30-plan`, or `50-verify`
 - Alternate: `Brainstorm` if the research opens multiple strategic options
 

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

@@ -1,11 +1,11 @@
 ---
 name: review
-description: "[Devflow] Two-axis review for changed work. Use inside /50-Verify or /70-Release when a branch, PR, or work-in-progress diff needs standards and spec review."
+description: "[Devflow] Two-axis review for changed work. Use inside 50-verify or 70-release when a branch, PR, or work-in-progress diff needs standards and spec review."
 ---
 
 # Review
 
-Use this support skill as one verification lane. `/50-Verify` owns validation evidence; this skill reviews a diff from two separate angles.
+Use this support skill as one verification lane. `50-verify` owns validation evidence; this skill reviews a diff from two separate angles.
 
 ## Axes
 
@@ -22,7 +22,7 @@ Keep the axes separate so one does not hide the other.
    - Confirm the diff is non-empty.
 
 2. Identify the spec source.
-   - Prefer `devflow/runs/{ID}-*/20-spec.md`, `30-plan.md`, issue brief, PRD, or explicit user path.
+   - Prefer `devflow/runs/{ID}-*20-spec.md`, `30-plan.md`, issue brief, PRD, or explicit user path.
    - If no spec exists, mark the Spec axis as skipped.
 
 3. Identify standards sources.

package/template/.claude/skills/review-followup-routing/SKILL.md

@@ -83,9 +83,9 @@ For task follow-up, append the approved follow-up work directly into the relevan
 
 ### 5. Route Back
 
-- `/40-Implement` for immediate corrective work
-- `/50-Verify` when only verification needs another pass
-- `/10-Define` or `/20-Spec` when the follow-up becomes genuinely new scope
+- `40-implement` for immediate corrective work
+- `50-verify` when only verification needs another pass
+- `10-define` or `20-spec` when the follow-up becomes genuinely new scope
 
 ## Output
 

package/template/.claude/skills/roadmap-strategy/SKILL.md

@@ -23,7 +23,7 @@ This skill should reuse and align with:
 
 - when product direction, priority, or sequencing needs a dedicated roadmap pass
 - when competitor, PRD, research, or delivery insight should be consolidated into strategy
-- when roadmap work should stay outside the numbered mainline but still hand off cleanly into `PRD`, `/10-Define`, or `/20-Spec`
+- when roadmap work should stay outside the numbered mainline but still hand off cleanly into `PRD`, `10-define`, or `20-spec`
 
 ## Canonical Artifacts
 
@@ -79,8 +79,8 @@ Replace placeholder content fully and keep headings and tables intact so validat
 ### 5. Route Back
 
 - `PRD` when product framing needs to deepen
-- `/10-Define` when roadmap decisions should become bounded work
-- `/20-Spec` when one item is ready for delivery contract work
+- `10-define` when roadmap decisions should become bounded work
+- `20-spec` when one item is ready for delivery contract work
 - `Brainstorm` when strategy is still too fuzzy to lock
 
 ## Output

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

@@ -8,7 +8,7 @@ description: "[Devflow] Plan safe feature or run reversal with dependency and co
 Where this sits in the workflow:
 
 ```text
-completed run + git history  ->  [rollback]  ->  /40-implement (or fix run)  ->  /50-verify  ->  /70-release
+completed run + git history  ->  [rollback]  ->  40-implement (or fix run)  ->  50-verify  ->  70-release
 (run archive + commits)          (risk review    (reverse product diff)          (prove)      (log & finalize)
                                   + plan)
 ```
@@ -20,9 +20,9 @@ This skill **plans a rollback**. It does not silently alter product code, reset
 A completed run by Running ID, name, or run path, plus an optional reason. Examples:
 
 ```text
-/rollback RUN-002-add-onboard-adopt-doctor-skills
-/rollback "auth login" because OAuth provider changed
-/rollback devflow/runs/RUN-001-align-devflow-blueprint
+rollback RUN-002-add-onboard-adopt-doctor-skills
+rollback "auth login" because OAuth provider changed
+rollback devflow/runs/RUN-001-align-devflow-blueprint
 ```
 
 With no target, list recent completed runs from `devflow/runs/` and `devflow/context/current-stage.md` and ask the user to choose. Never silently guess the target. If the reason is missing, ask for one before finalizing the rollback plan.
@@ -98,7 +98,7 @@ Draft the rollback plan containing:
 Present the rollback plan to the user:
 
 - Summarize affected files and dependency risks.
-- If approved, route to `/40-implement` (or allocate a dedicated Fix/Rollback Run) to safely execute the reversal steps behind review gates.
+- If approved, route to `40-implement` (or allocate a dedicated Fixrollback Run) to safely execute the reversal steps behind review gates.
 
 ## Rules
 

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

@@ -107,8 +107,8 @@ related_files: []
 
 ## 8. Next Allowed Command
 
-- `/40-Implement {running_id}` (if fail, for code remediation)
-- `/50-Verify {running_id}` (if pass, to verify execution correctness)
+- `40-implement {running_id}` (if fail, for code remediation)
+- `50-verify {running_id}` (if pass, to verify execution correctness)
 
 ## 9. Nexus Event
 
@@ -157,7 +157,7 @@ Evaluate high-severity risks including:
 
 - **Classification**: Companion command
 - **Mainline Status**: Not part of the linear Timeline. Can be run at any stage.
-- **Typical Entry Points**: Any stage, especially before `/50-Verify` or `/70-Release` to verify security health.
+- **Typical Entry Points**: Any stage, especially before `50-verify` or `70-release` to verify security health.
 
 ## Sources
 

package/template/.claude/skills/shipping-and-launch/SKILL.md

@@ -17,7 +17,7 @@ Ship with confidence. The goal is not just to deploy — it's to deploy safely,
 - Opening a beta or early access program
 - Any deployment that carries risk (all of them)
 
-In DevFlow 2.0, this skill most often supports `/70-Release` and assumes `/60-Report` is already aligned as the communication baseline.
+In DevFlow 2.0, this skill most often supports `70-release` and assumes `60-report` is already aligned as the communication baseline.
 
 ## The Pre-Launch Checklist
 

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

@@ -21,7 +21,7 @@ Treat this workflow file as a wrapper around that skill.
 
 Use this workflow when the code works but has grown harder to read, harder to change, or more general than necessary.
 
-In DevFlow 2.0, `Simplify` is a supporting implementation workflow. It usually pairs with `/40-Implement` and should end in `/50-Verify`.
+In DevFlow 2.0, `Simplify` is a supporting implementation workflow. It usually pairs with `40-implement` and should end in `50-verify`.
 
 ## Process
 
@@ -61,19 +61,19 @@ Return:
 
 - Classification: Companion command
 - Mainline status: Not a numbered stage
-- Typical entry points: `/40-Implement`, `/50-Verify`, `PR-Review`, `Agent`
-- Typical handoff targets: `/40-Implement`, `/50-Verify`, `PR-Review`
+- Typical entry points: `40-implement`, `50-verify`, `PR-Review`, `Agent`
+- Typical handoff targets: `40-implement`, `50-verify`, `PR-Review`
 
 ## Sources
 
 - `AGENTS.md`
 - `.agents/skills/code-simplification/SKILL.md`
 - `.agent/resources/schemas/refactoring.template.md`
-- Related commands: `/40-Implement`, `/50-Verify`, `PR-Review`, `Agent`
+- Related commands: `40-implement`, `50-verify`, `PR-Review`, `Agent`
 
 ## Next Workflow Recommendation
 
-- **Primary**: `/50-Verify`
+- **Primary**: `50-verify`
 - **Why**: simplification should finish with explicit proof that behavior did not regress
-- **Alternative**: `/40-Implement` when simplification exposed a deeper implementation change rather than a pure refactor
+- **Alternative**: `40-implement` when simplification exposed a deeper implementation change rather than a pure refactor
 

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

@@ -48,8 +48,8 @@ Route proportionally:
 - `Research` or `Spec-Research` for external or technical proof
 - `Competitor` for market context
 - `PRD` for product framing
-- `/10-Define` for scope and decision locking
-- `/20-Spec` for delivery contract writing
+- `10-define` for scope and decision locking
+- `20-spec` for delivery contract writing
 
 Do not stack every support surface by default.
 
@@ -76,9 +76,9 @@ Use `.agent/resources/schemas/spec_orchestration.template.md` and replace placeh
 
 ### 5. Route Back To Mainline
 
-- `/10-Define` when the idea still needs scope decisions
-- `/20-Spec` when enough evidence exists to write the delivery contract
-- `/30-Plan` only when the spec is already solid
+- `10-define` when the idea still needs scope decisions
+- `20-spec` when enough evidence exists to write the delivery contract
+- `30-plan` only when the spec is already solid
 
 ## Output
 

package/template/.claude/skills/specialist-agent-routing/SKILL.md

@@ -76,13 +76,13 @@ Use `.agent/resources/schemas/agent_report.template.md` unless the invoking work
 
 Return to the owning step:
 
-- `/10-Define`
-- `/20-Spec`
-- `/30-Plan`
-- `/40-Implement`
-- `/50-Verify`
-- `/70-Release`
-- `/60-Report`
+- `10-define`
+- `20-spec`
+- `30-plan`
+- `40-implement`
+- `50-verify`
+- `70-release`
+- `60-report`
 - `PR-Review`
 - `Research`
 

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

@@ -69,14 +69,14 @@ Display an organized output listing Passed/Failed files, and explicitly show the
 
 - Classification: Companion command
 - Mainline status: Verification support command, not a numbered stage
-- Typical entry points: `/40-Implement`, `/50-Verify`, `Debug`
-- Typical handoff targets: `/50-Verify`, `Debug`, `QA-Orchestrate`
+- Typical entry points: `40-implement`, `50-verify`, `Debug`
+- Typical handoff targets: `50-verify`, `Debug`, `QA-Orchestrate`
 
 ## Sources
 
 - `AGENTS.md`
 - `.agents/skills/test-execution-and-coverage/SKILL.md`
 - `.agent/resources/schemas/test_report.template.md`
-- Related commands: `/40-Implement`, `/50-Verify`, `Debug`, `QA-Orchestrate`
+- Related commands: `40-implement`, `50-verify`, `Debug`, `QA-Orchestrate`
 
 

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

@@ -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

@@ -8,12 +8,12 @@ description: "[Devflow] Generate human manual QA review walkthrough guide (where
 Where this sits in the workflow:
 
 ```text
-/40-implement or /50-verify or /60-report  ->  [try]  ->  human review & verification
+40-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.
+`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.
 
@@ -23,7 +23,7 @@ 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 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.

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

@@ -1,6 +1,6 @@
 ---
 name: verification-orchestration
-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."
+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/wiki/SKILL.md

@@ -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

@@ -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,13 @@ 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
@@ -39,57 +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.
-- `try` (alias: `/try`, `$try`): Step-by-step human manual QA review guide (where to go, what to click, what to expect).
-- `rollback` (alias: `/rollback`, `$rollback`): Safe feature/run reversal planner with dependency and commit risk analysis.
-- `ci` (alias: `/ci`, `$ci`): Automatic GitHub Actions workflow (`.github/workflows/verify.yml`) setup and alignment.
-- `brief` (alias: `/brief`, `$brief`): Read-only scope, dependency, and size pre-briefing before speccing a run.
-- `autopilot` (alias: `/autopilot`, `$autopilot`): Optional explicit mode for one bounded spec/plan/implement/verify/report pass with checkpoint commits and review packet.
+- `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.
@@ -103,25 +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" |
-| **Manual QA** | `try` | `manual-test` | `$try` | `/try` | "how to try", "where to click", "manual test guide" |
-| **Reversal** | `rollback` | `revert` | `$rollback` | `/rollback` | "rollback run", "undo feature", "plan reversal" |
-| **CI Setup** | `ci` | `github-actions`| `$ci` | `/ci` | "setup ci", "create github actions", "add verify workflow" |
-| **Pre-Check** | `brief` | `preview-scope`| `$brief` | `/brief` | "brief feature", "check next scope", "preview run" |
-| **Autopilot** | `autopilot` | `auto-loop` | `$autopilot` | `/autopilot` | "run autopilot", "autopilot feature", "start auto loop" |
-| **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