@jakkrichm/create-nexus-devflow 2.0.8 → 2.0.10

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

@@ -0,0 +1,131 @@
+---
+name: ci
+description: "[Devflow] Set up automated GitHub Actions CI workflow (.github/workflows/verify.yml) aligned with project verify command."
+---
+
+# ci - Automated GitHub Actions Pipeline Setup
+
+Where this sits in the workflow:
+
+```text
+onboard or adopt  ->  [ci]  ->  Verify locally  ->  GitHub Actions runs Verify on PR & Push
+(project setup)         (setup)    (same command)     (automated checks)
+```
+
+This skill connects local verification with automated GitHub checks using **one shared Verify recipe**:
+
+- **Verify is the recipe**: Runs the project's real checks (typecheck, tests, build) defined in `AGENTS.md`.
+- **GitHub Actions is the worker**: Executes the same recipe automatically on pull requests and pushes.
+- **Branch Protection / Ruleset is the gate**: Optionally requires the check to pass before merging.
+
+This skill configures the workflow file. It **never pushes to remote, changes remote repository rulesets, or publishes releases** without explicit permission.
+
+## Input
+
+No argument is required. A preferred package manager or branch name can be optionally provided.
+
+## Step 1 - Inspect Project Setup (Read-Only)
+
+Inspect the repository without modifying files:
+
+1. **Commands in `AGENTS.md`**: Look for existing `Verify`, `Test`, `Build`, and `Dev` commands.
+2. **Project Manifests**: `package.json`, `requirements.txt`, `pyproject.toml`, `go.mod`, `Cargo.toml`, etc.
+3. **Lockfiles & Package Manager**: `pnpm-lock.yaml` (pnpm), `package-lock.json` (npm), `yarn.lock` (yarn), `bun.lockb` (bun), `poetry.lock` (poetry), `Cargo.lock` (cargo).
+4. **Runtime Versions**: `.node-version`, `.nvmrc`, `package.json` engines, `.python-version`.
+5. **Existing Workflows**: Inspect `.github/workflows/` to check if a CI workflow already exists.
+6. **Git Default Branch**: Detect `main` or `master`.
+
+If a healthy and matching workflow already exists, report that CI is already in place and stop.
+
+## Step 2 - Define The Single Verify Command
+
+Build one combined Verify command from actual checks that exist in the project, in this standard order:
+
+1. **Typecheck** (e.g. `tsc --noEmit`, `mypy`, `pyright`, `go vet`)
+2. **Tests** (e.g. `npm test`, `pytest`, `go test ./...`, `cargo test`) - only if real tests exist
+3. **Build** (e.g. `npm run build`, `cargo build`)
+
+For JavaScript/TypeScript projects, ensure a `verify` or `check` script exists in `package.json` (or combine existing scripts: e.g. `npm run check:static && npm test && npm run build`).
+
+Record the exact command in the Commands section of `AGENTS.md`:
+
+```markdown
+## Commands
+- Verify: `npm run check` (or detected verify command)
+```
+
+## Step 3 - Generate `.github/workflows/verify.yml`
+
+Create `.github/workflows/verify.yml` with security and stability best practices:
+
+- **Trigger**: Pull requests to default branch + Pushes to default branch.
+- **Permissions**: Set least privilege `permissions: contents: read`.
+- **Concurrency**: Cancel in-progress runs on the same PR branch.
+- **Lockfile-Safe Install**: Use `npm ci`, `pnpm install --frozen-lockfile`, `yarn install --immutable`, or `cargo --locked`.
+- **Exact Verify Step**: Run the exact Verify command from `AGENTS.md`.
+
+### Standard GitHub Actions Template (Node.js Example):
+
+```yaml
+name: Verify
+
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  verify:
+    name: Run Verification Checks
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Code
+        uses: actions/checkout@v4
+
+      - name: Setup Runtime
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+
+      - name: Install Dependencies
+        run: npm ci
+
+      - name: Run Verify Checks
+        run: npm run check
+```
+
+## Step 4 - Verify Locally
+
+Execute the Verify command locally to confirm that it succeeds on clean code before recommending it:
+
+```bash
+npm run check
+```
+
+If local verification fails, report the failing check and assist in resolving it before claiming CI readiness.
+
+## Step 5 - Summary & Handoff
+
+Output a concise summary:
+
+- **Verify Command**: Documented command in `AGENTS.md`.
+- **Workflow File**: `.github/workflows/verify.yml` (created/updated).
+- **Trigger Events**: `pull_request` & `push`.
+- **Local Test**: Result of local execution.
+- **Next Steps**: Advise user to commit and push the workflow to activate GitHub Actions.
+
+## Rules
+
+- **Preserve Existing CI**: Never overwrite existing custom workflows without explicit user consent.
+- **No Dummy Tests**: Do not invent fake test commands or install unrequested test runners.
+- **Least Privilege Security**: Always specify `permissions: contents: read`.
+- **No Auto-Push**: Stop at local file creation; do not push to remote automatically.

package/template/.agents/skills/ci-cd-and-automation/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ci-cd-and-automation
-description: Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
+description: "[Devflow] Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies."
 ---
 
 # CI/CD and Automation
@@ -58,7 +58,7 @@ Pull Request Opened
 ### Basic CI Pipeline
 
 ```yaml
-# .github/workflows/ci.yml
+# .github/workflowsci.yml
 name: CI
 
 on:
@@ -127,11 +127,11 @@ jobs:
       - name: Run migrations
         run: npx prisma migrate deploy
         env:
-          DATABASE_URL: postgresql://ci_user:${{ secrets.CI_DB_PASSWORD }}@localhost:5432/testdb
+          DATABASE_URL: postgresql:/ci_user:${{ secrets.CI_DB_PASSWORD }}@localhost:5432/testdb
       - name: Integration tests
         run: npm run test:integration
         env:
-          DATABASE_URL: postgresql://ci_user:${{ secrets.CI_DB_PASSWORD }}@localhost:5432/testdb
+          DATABASE_URL: postgresql:/ci_user:${{ secrets.CI_DB_PASSWORD }}@localhost:5432/testdb
 ```
 
 > **Note:** Even for CI-only test databases, use GitHub Secrets for credentials rather than hardcoding values. This builds good habits and prevents accidental reuse of test credentials in other contexts.

package/template/.agents/skills/code-review-and-quality/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: code-review-and-quality
-description: Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
+description: "[Devflow] Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch."
 ---
 
 # Code Review and Quality

package/template/.agents/skills/code-simplification/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: code-simplification
-description: Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
+description: "[Devflow] Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity."
 ---
 
 # Code Simplification

package/template/.agents/skills/codebase-design/SKILL.md

@@ -1,20 +1,20 @@
 ---
 name: codebase-design
-description: Shared vocabulary for designing deep modules. Use when a DevFlow stage needs module/interface design, seam placement, testability review, or architecture simplification.
+description: "[Devflow] Shared vocabulary for designing deep modules. Use when a DevFlow stage needs module/interface design, seam placement, testability review, or architecture simplification."
 ---
 
 # Codebase Design
 
-Use this support skill when `/20-Spec`, `/30-Plan`, `/40-Implement`, or `/50-Verify` needs better module shape.
+Use this support skill when `20-spec`, `30-plan`, `40-implement`, or `50-verify` needs better module shape.
 
 Design deep modules: a lot of behavior behind a small interface, placed at a clean seam, and testable through that interface. The aim is leverage for callers, locality for maintainers, and behavior-focused tests.
 
 ## DevFlow Placement
 
-- `/20-Spec`: use when requirements depend on a stable module or interface contract.
-- `/30-Plan`: use when planning needs file-level architecture, seams, or dependency strategy.
-- `/40-Implement`: use when implementation reveals shallow modules or awkward test seams.
-- `/50-Verify`: use when review finds code that is hard to test, hard to change, or too spread out.
+- `20-spec`: use when requirements depend on a stable module or interface contract.
+- `30-plan`: use when planning needs file-level architecture, seams, or dependency strategy.
+- `40-implement`: use when implementation reveals shallow modules or awkward test seams.
+- `50-verify`: use when review finds code that is hard to test, hard to change, or too spread out.
 
 ## Vocabulary
 

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

@@ -1,6 +1,6 @@
 ---name: commit
 
-description: Smart Commit (Git Orchestration) - Stage files intelligently and write a concise, imperative commit message according to project standards.
+description: "[Devflow] Smart Commit (Git Orchestration) - Stage files intelligently and write a concise, imperative commit message according to project standards."
 ---
 # ๐Ÿ’พ Smart Commit (Git Orchestration)
 
@@ -50,14 +50,14 @@ You are an orchestrator. Your goal is to call the specialized Git Committer agen
 
 - Classification: Companion command
 - Mainline status: Release support command, not a numbered stage
-- Typical entry points: `/70-Release` after the report is aligned and release execution is ready
-- Typical handoff targets: `PR`, `Deploy`, `/70-Release`
+- Typical entry points: `70-release` after the report is aligned and release execution is ready
+- Typical handoff targets: `PR`, `Deploy`, `70-release`
 
 ## Sources
 
 - `AGENTS.md`
 - `.agents/skills/release-git-operations/SKILL.md`
 - `.agents/skills/git-workflow-and-versioning/SKILL.md`
-- Related commands: `/70-Release`, `PR`, `Deploy`, `Merge`
+- Related commands: `70-release`, `PR`, `Deploy`, `Merge`
 
 

package/template/.agents/skills/competitor-analysis/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: competitor-analysis
-description: Research competitors, market alternatives, user pain points, and differentiation opportunities. Use when product framing, roadmap decisions, or strategic positioning need source-backed external context.
+description: "[Devflow] Research competitors, market alternatives, user pain points, and differentiation opportunities. Use when product framing, roadmap decisions, or strategic positioning need source-backed external context."
 ---
 
 # Competitor Analysis
@@ -51,9 +51,9 @@ Use `.agent/resources/schemas/competitor_analysis.template.md` when saving a reu
 ### 5. Route Back
 
 - `PRD` for product framing
-- `/10-Define` for scope and decision shaping
+- `10-define` for scope and decision shaping
 - `Roadmap` for prioritization
-- `/20-Spec` when a selected opportunity becomes actionable
+- `20-spec` when a selected opportunity becomes actionable
 
 ## Output
 

package/template/.agents/skills/context-engineering/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: context-engineering
-description: Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
+description: "[Devflow] Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project."
 ---
 
 # Context Engineering

package/template/.agents/skills/database-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: database-design
-description: Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
+description: "[Devflow] Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases."
 allowed-tools: Read, Write, Edit, Glob, Grep
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 name: debug
-description: Debug workflow
+description: "[Devflow] Root cause investigation and diagnostic loop before or during implementation without editing code. Use when encountering broken behavior, test failures, or bugs."
 ---
 
 ---
@@ -27,11 +27,11 @@ Use it when:
 
 Preferred DevFlow 2.0 pairing:
 
-- from `/00-Discover` when a new request begins with a failure whose root cause is unknown
-- from `/40-Implement`
-- from `/50-Verify`
+- from `00-discover` when a new request begins with a failure whose root cause is unknown
+- from `40-implement`
+- from `50-verify`
 
-When invoked with a Discovery ID, link the RCA report to that discovery and return to `/00-Discover {discovery_id}` for the delivery decision. Do not allocate a Running ID for an unapproved fix during Debug.
+When invoked with a Discovery ID, link the RCA report to that discovery and return to `00-discover {discovery_id}` for the delivery decision. Do not allocate a Running ID for an unapproved fix during Debug.
 
 ## Source Discipline
 
@@ -114,18 +114,18 @@ Debug unexpected duplicate records
 
 - Classification: Companion command
 - Mainline status: Not a numbered stage
-- Typical entry points: `/00-Discover`, `/40-Implement`, `/50-Verify`, `Issue-Triage`, production failure analysis
-- Typical handoff targets: `/00-Discover {discovery_id}` for discovery-owned RCA, `/40-Implement`, `/50-Verify`, `Insight`, `Wiki`
+- Typical entry points: `00-discover`, `40-implement`, `50-verify`, `Issue-Triage`, production failure analysis
+- Typical handoff targets: `00-discover {discovery_id}` for discovery-owned RCA, `40-implement`, `50-verify`, `Insight`, `Wiki`
 
 ## Sources
 
 - `AGENTS.md`
 - `.agent/resources/schemas/rca.template.md`
-- Related commands: `/40-Implement`, `/50-Verify`, `Test`, `Insight`, `Wiki`, `Agent`
+- Related commands: `40-implement`, `50-verify`, `Test`, `Insight`, `Wiki`, `Agent`
 
 ## Next Workflow Recommendation
 
-- Default: return to `/00-Discover {discovery_id}` when the failure entered through discovery; otherwise return to `/40-Implement` when a tracked fix already exists
-- Alternate: `/30-Plan` if the fix needs planning changes
-- Alternate: `/50-Verify` when the issue is resolved and needs re-checking
+- Default: return to `00-discover {discovery_id}` when the failure entered through discovery; otherwise return to `40-implement` when a tracked fix already exists
+- Alternate: `30-plan` if the fix needs planning changes
+- Alternate: `50-verify` when the issue is resolved and needs re-checking
 

package/template/.agents/skills/debugging-and-error-recovery/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: debugging-and-error-recovery
-description: Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
+description: "[Devflow] Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing."
 ---
 
 # Debugging and Error Recovery

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

@@ -1,6 +1,6 @@
 ---name: deploy
 
-description: Production Deployment (Auto-Deploy) - Perform pre-flight checks, deployment execution, and verification for production releases.
+description: "[Devflow] Production deployment pre-flight checks, smoke validation, and deployment execution."
 ---
 # ๐Ÿš€ Phase 52: Production Deployment (Auto-Deploy)
 
@@ -76,8 +76,8 @@ Generate an Error summary detailing:
 
 - Classification: Companion command
 - Mainline status: Release support command, not a numbered stage
-- Typical entry points: `/70-Release` after the report is aligned and packaging is ready to execute
-- Typical handoff targets: `/60-Report`, `Changelog`, `Wiki`
+- Typical entry points: `70-release` after the report is aligned and packaging is ready to execute
+- Typical handoff targets: `60-report`, `Changelog`, `Wiki`
 
 ## Sources
 
@@ -86,6 +86,6 @@ Generate an Error summary detailing:
 - `.agents/skills/shipping-and-launch/SKILL.md`
 - `.agents/skills/deployment-procedures/SKILL.md`
 - `.agent/resources/schemas/deploy_report.template.md`
-- Related commands: `/70-Release`, `Commit`, `PR`, `Changelog`, `/60-Report`
+- Related commands: `70-release`, `Commit`, `PR`, `Changelog`, `60-report`
 
 

package/template/.agents/skills/deployment-procedures/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: deployment-procedures
-description: Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
+description: "[Devflow] Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts."
 allowed-tools: Read, Glob, Grep, Bash
 ---
 

package/template/.agents/skills/deprecation-and-migration/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: deprecation-and-migration
-description: Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
+description: "[Devflow] Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code."
 ---
 
 # Deprecation and Migration

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

@@ -1,6 +1,6 @@
 ---
 name: devflow
-description: Flagship interactive guide, intent router, workspace state inspector, and sitemap for Nexus-DevFlow workflows. Inspects current workspace state, maps natural language requests to matching stages/commands, and provides a cheat sheet of all available DevFlow skills. Use when the user runs devflow, /devflow, $devflow, status, asks how to use devflow, asks what command to run next, or needs guidance on DevFlow lifecycle paths.
+description: "[Devflow] Flagship interactive guide, state inspector, and intent router for DevFlow workflows."
 ---
 
 # devflow - Interactive Workflow Guide & Intent Router for Nexus-DevFlow
@@ -9,14 +9,14 @@ Use this skill to guide the user on what to do next, inspect current workspace s
 
 ## 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.
+- **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.
 
 ## 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).
+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`).
 3. **Active Discovery**: Check `devflow/discoveries/` for open discovery notes.
 4. **Audit Findings Ledger**: Check `devflow/context/findings.md` for open high-severity findings.
@@ -24,15 +24,15 @@ When invoked without an argument (or when determining the next step), inspect:
 ### State-Based Recommendation Rules
 
 - 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 `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 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`).
+- If user asks to check system health or configuration -> Recommend `doctor` (or `doctor`, `$doctor`).
 
 ## Intent Classification & Skill Routing
 
@@ -51,6 +51,11 @@ When the user specifies a request, map it to the matching DevFlow 2.0 stage or c
 | "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` |
@@ -66,20 +71,25 @@ When the user specifies a request, map it to the matching DevFlow 2.0 stage or c
 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
+- `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
+- `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
 - `brainstorm` - Ideate without allocating running IDs
 - `research` - Conduct codebase or web research

package/template/.agents/skills/diagnosing-bugs/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: diagnosing-bugs
-description: Diagnosis loop for hard bugs and performance regressions. Use inside Debug, /40-Implement, or /50-Verify when behavior is broken, throwing, failing, flaky, or slow.
+description: "[Devflow] Diagnosis loop for hard bugs and performance regressions. Use inside Debug, 40-implement, or 50-verify when behavior is broken, throwing, failing, flaky, or slow."
 ---
 
 # Diagnosing Bugs
 
 Use this support skill when the active DevFlow owner needs a disciplined root-cause loop.
 
-Do not let this skill replace `Debug`, `/40-Implement`, or `/50-Verify`. It supplies the method; the owning workflow records the artifact.
+Do not let this skill replace `Debug`, `40-implement`, or `50-verify`. It supplies the method; the owning workflow records the artifact.
 
 ## Phase 1: Build A Tight Feedback Loop
 
@@ -79,7 +79,7 @@ When a correct test seam exists:
 4. Watch it pass.
 5. Re-run the original feedback loop.
 
-If no correct seam exists, record that architecture finding and route to `codebase-design` or `/30-Plan` after the bug is fixed.
+If no correct seam exists, record that architecture finding and route to `codebase-design` or `30-plan` after the bug is fixed.
 
 ## Phase 6: Cleanup And Post-Mortem
 

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

@@ -1,6 +1,6 @@
 ---
 name: doctor
-description: Read-only DevFlow health check and diagnostics. Inspects DevFlow setup, tool adapters, context files integrity, AGENTS.md commands validity, active runs in devflow/runs/, checklist completeness, and detects workflow drift. Use when the user runs doctor, /doctor, $doctor, asks to diagnose DevFlow, or wants to check project workflow health.
+description: "[Devflow] Read-only DevFlow health check and diagnostics for context files, adapters, commands, and workflow drift."
 ---
 
 # doctor - Read-Only DevFlow Health Check & Diagnostics
@@ -12,7 +12,7 @@ Any time during development -> [doctor] -> Health Report & Actionable Fixes
 (read-only inspection)          (diagnostics)    (remediation recommendations)
 ```
 
-`/doctor` is a safe, read-only diagnostic skill that verifies whether your repository's Nexus-DevFlow configuration, context files, tool adapters, commands, and active runs are healthy and aligned.
+`doctor` is a safe, read-only diagnostic skill that verifies whether your repository's Nexus-DevFlow configuration, context files, tool adapters, commands, and active runs are healthy and aligned.
 
 ---
 
@@ -29,7 +29,7 @@ Run through these 5 health checks:
 ### Check 1: Core Framework & Context Files Integrity
 - Check if [AGENTS.md](AGENTS.md) and [CLAUDE.md](CLAUDE.md) exist and are populated.
 - Check required context files under `devflow/context/`:
-  - `project-overview.md` (Check if still empty/placeholder -> recommend `/onboard` or `/adopt`)
+  - `project-overview.md` (Check if still empty/placeholder -> recommend `onboard` or `adopt`)
   - `coding-standards.md` (Check if customized for stack)
   - `ai-interaction.md` (Check if rules are configured)
   - `current-stage.md` (Check if active run matches filesystem)
@@ -80,5 +80,5 @@ Present a clean, scannable diagnostic report:
 
 ### Recommended Remediation Actions:
 1. [Action item if any warning or failure detected]
-2. [Suggested next command, e.g. /devflow, /onboard, /adopt, etc.]
+2. [Suggested next command, e.g. devflow, onboard, adopt, etc.]
 ```

package/template/.agents/skills/documentation-and-adrs/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: documentation-and-adrs
-description: Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
+description: "[Devflow] Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase."
 ---
 
 # Documentation and ADRs

package/template/.agents/skills/domain-modeling/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: domain-modeling
-description: Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
+description: "[Devflow] Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model."
 ---
 
 # Domain Modeling

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

@@ -1,6 +1,6 @@
 ---
 name: followup
-description: Followup workflow
+description: "[Devflow] Followup task tracking, post-verification iteration, and routing unresolved items to subsequent runs."
 ---
 
 ---
@@ -33,11 +33,11 @@ Preserve existing phases, subtasks, statuses, logs, QA results, and completed co
 
 Read:
 
-- `devflow/runs/{ID}-*/10-define.md`
-- `devflow/runs/{ID}-*/20-spec.md`
-- `devflow/runs/{ID}-*/30-plan.md`
-- `devflow/runs/{ID}-*/40-implement.md`
-- `devflow/runs/{ID}-*/50-verify.md` if present
+- `devflow/runs/{ID}-*10-define.md`
+- `devflow/runs/{ID}-*20-spec.md`
+- `devflow/runs/{ID}-*30-plan.md`
+- `devflow/runs/{ID}-*40-implement.md`
+- `devflow/runs/{ID}-*50-verify.md` if present
 
 ### 2. Classify The Follow-Up
 
@@ -57,7 +57,7 @@ Append the follow-up scope directly to the relevant stage markdown files for the
 
 ### 4. Ask For Confirmation
 
-After adding or proposing follow-up subtasks, ask the user to confirm before `/40-Implement`.
+After adding or proposing follow-up subtasks, ask the user to confirm before `40-implement`.
 
 ## Output
 
@@ -66,18 +66,18 @@ Return:
 - follow-up category
 - new phase/subtask plan
 - validation result
-- next command: `/40-Implement {ID}`
+- next command: `40-implement {ID}`
 
 ## Relationship To DevFlow 2.0
 
 - Classification: Companion command
 - Mainline status: Not a numbered stage
 - Typical entry points: after review, triage, or release follow-up work is identified
-- Typical handoff targets: `/10-Define`, `/20-Spec`, `/30-Plan`, `/40-Implement`
+- Typical handoff targets: `10-define`, `20-spec`, `30-plan`, `40-implement`
 
 ## Sources
 
 - `AGENTS.md`
-- Related commands: `PR-Followup`, `Issue-Triage`, `Human-Feedback`, `/10-Define`, `/20-Spec`, `/40-Implement`
+- Related commands: `PR-Followup`, `Issue-Triage`, `Human-Feedback`, `10-define`, `20-spec`, `40-implement`
 
 

package/template/.agents/skills/frontend-ui-engineering/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: frontend-ui-engineering
-description: Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
+description: "[Devflow] Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated."
 ---
 
 # Frontend UI Engineering

package/template/.agents/skills/git-workflow-and-versioning/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: git-workflow-and-versioning
-description: Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.
+description: "[Devflow] Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams."
 ---
 
 # Git Workflow and Versioning