@jakkrichm/create-nexus-devflow 2.0.6 → 2.0.9

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

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,6 +1,6 @@
 ---
 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

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)
 

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

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."
 ---
 
 ---

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)
 

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, 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,78 +9,97 @@ Use this skill to guide the user on what to do next, inspect current workspace s
 
 ## Input
 
-- **No argument (`/devflow`)**: Inspect current workspace state (active run in `devflow/runs/` or `devflow/context/current-stage.md`, active discovery in `devflow/discoveries/`, open findings in `devflow/context/findings.md`, and project overview in `devflow/context/project-overview.md`) and recommend the exact next action.
-- **With user request (`/devflow "<request>"`)**: Classify the user's intent and guide them to the matching DevFlow 2.0 stage or companion command path.
+- **No argument (`devflow`, `/devflow`, `$devflow`, or `status`)**: Inspect current workspace state (active run in `devflow/runs/` or `devflow/context/current-stage.md`, active discovery in `devflow/discoveries/`, 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. **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`).
-2. **Active Discovery**: Check `devflow/discoveries/` for open discovery notes.
-3. **Audit Findings Ledger**: Check `devflow/context/findings.md` for open high-severity findings.
-4. **Project Overview**: Read `devflow/context/project-overview.md` for overall stack and context.
+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.
 
 ### State-Based Recommendation Rules
 
-- If a run is at `10-define.md` -> Recommend `/20-spec {RUNNING_ID}`.
-- If a run is at `20-spec.md` -> Recommend `/30-plan {RUNNING_ID}`.
-- If a run is at `30-plan.md` -> Recommend `/40-implement {RUNNING_ID}`.
-- 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}`.
-- 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 `Brainstorm`.
-- If no run is active and open P0/P1 findings exist -> Recommend `Security-Review` or `Debug`.
+- If context is empty/unconfigured -> Recommend `onboard` (for fresh project) or `adopt` (for brownfield codebase).
+- If a run is at `10-define.md` -> Recommend `20-spec {RUNNING_ID}` (or `/20-spec`, `$20-spec`, `spec`).
+- If a run is at `20-spec.md` -> Recommend `30-plan {RUNNING_ID}` (or `/30-plan`, `$30-plan`, `plan`).
+- If a run is at `30-plan.md` -> Recommend `40-implement {RUNNING_ID}` (or `/40-implement`, `$40-implement`, `implement`).
+- If a run is at `40-implement.md` with incomplete tasks -> Recommend `40-implement {RUNNING_ID}`.
+- If a run is at `40-implement.md` with all tasks done -> Recommend `50-verify {RUNNING_ID}` (or `/50-verify`, `$50-verify`, `verify`).
+- If a run passed `50-verify.md` -> Recommend `60-report {RUNNING_ID}` then `70-release {RUNNING_ID}`.
+- If no run is active and user wants to explore an idea -> Recommend `00-discover` (or `discover`, `Brainstorm`).
+- If no run is active and open P0/P1 findings exist -> Recommend `security-review` or `debug`.
+- If user asks to check system health or configuration -> Recommend `doctor` (or `/doctor`, `$doctor`).
 
 ## Intent Classification & Skill Routing
 
 When the user specifies a request, map it to the matching DevFlow 2.0 stage or companion command:
 
-| User Intent / Request Type | Recommended Skill | Lifecycle Path |
-| --- | --- | --- |
-| "Explore a new request / idea" | `/00-discover` | `/00-discover` -> `/10-define` -> `/20-spec` -> ... |
-| "Define delivery boundaries and ID" | `/10-define` | `/10-define` -> `/20-spec` -> `/30-plan` |
-| "Write formal markdown specification" | `/20-spec` | `/20-spec` -> `/30-plan` -> `/40-implement` |
-| "Break down spec into actionable plan" | `/30-plan` | `/30-plan` -> `/40-implement` -> `/50-verify` |
-| "Execute code implementation" | `/40-implement` | `/40-implement` -> `/50-verify` |
-| "Verify code quality & QA review" | `/50-verify` | `/50-verify` -> `/60-report` -> `/70-release` |
-| "Generate summary HTML/MD report" | `/60-report` | `/60-report` -> `/70-release` |
-| "Package for PR merge or deployment" | `/70-release` | `/70-release` |
-| "High-level goal or long-running task" | `Goal` | `Goal` -> `/00-discover` |
-| "Brainstorm ideas without allocating ID" | `Brainstorm` | `Brainstorm` -> `/00-discover` |
-| "Deep codebase or web research" | `Research` | `Research` |
-| "Investigate failure or root cause" | `Debug` | `Debug` -> `/40-implement` or `/10-define` |
-| "Product framing & PRD creation" | `PRD` | `PRD` -> `/00-discover` |
-| "Intake and triage incoming bugs" | `Issue-Triage` | `Issue-Triage` -> `Debug` or `/10-define` |
-| "High-severity security audit" | `Security-Review` | `Security-Review` |
-| "Manage project knowledge base" | `Wiki` | `Wiki` |
-| "Verify or update DevFlow setup" | `Check-For-Updates` | `Check-For-Updates` |
+| User Intent / Request Type | Recommended Skill | Normal Name / Alias | Lifecycle Path |
+| :--- | :--- | :--- | :--- |
+| "Setup DevFlow on fresh/new project" | `onboard` | `onboard` / `setup` | `onboard` -> `00-discover` or `10-define` |
+| "Adopt DevFlow on existing codebase" | `adopt` | `adopt` / `bootstrap` | `adopt` -> `00-discover` or `10-define` |
+| "Check setup health & diagnostics" | `doctor` | `doctor` / `health` | `doctor` |
+| "Explore a new request / idea" | `00-discover` | `discover` | `00-discover` -> `10-define` -> `20-spec` -> ... |
+| "Define delivery boundaries and ID" | `10-define` | `define` | `10-define` -> `20-spec` -> `30-plan` |
+| "Write formal markdown specification" | `20-spec` | `spec` | `20-spec` -> `30-plan` -> `40-implement` |
+| "Break down spec into actionable plan" | `30-plan` | `plan` | `30-plan` -> `40-implement` -> `50-verify` |
+| "Execute code implementation" | `40-implement` | `implement` | `40-implement` -> `50-verify` |
+| "Verify code quality & QA review" | `50-verify` | `verify` | `50-verify` -> `60-report` -> `70-release` |
+| "Generate summary HTML/MD report" | `60-report` | `report` | `60-report` -> `70-release` |
+| "Package for PR merge or deployment" | `70-release` | `release` | `70-release` |
+| "Human manual QA walkthrough guide" | `try` | `try` | `try` (after implement or verify) |
+| "Safely plan feature or run reversal" | `rollback` | `rollback` | `rollback` -> `40-implement` |
+| "Set up automatic GitHub Actions CI" | `ci` | `ci` | `ci` (after onboard or adopt) |
+| "Pre-check scope & risks before spec" | `brief` | `brief` | `brief` -> `20-spec` |
+| "Run autonomous bounded delivery loop"| `autopilot` | `autopilot` | `autopilot` -> `70-release` |
+| "High-level goal or long-running task" | `goal` | `goal` | `goal` -> `00-discover` |
+| "Brainstorm ideas without allocating ID" | `brainstorm` | `brainstorm` | `brainstorm` -> `00-discover` |
+| "Deep codebase or web research" | `research` | `research` | `research` |
+| "Investigate failure or root cause" | `debug` | `debug` | `debug` -> `40-implement` or `10-define` |
+| "Product framing & PRD creation" | `prd` | `prd` | `prd` -> `00-discover` |
+| "Intake and triage incoming bugs" | `issue-triage` | `issue-triage` | `issue-triage` -> `debug` or `10-define` |
+| "High-severity security audit" | `security-review` | `security-review` | `security-review` |
+| "Manage project knowledge base" | `wiki` | `wiki` | `wiki` |
+| "Verify or update DevFlow setup" | `check-for-updates` | `check-for-updates` | `check-for-updates` |
 
 ## Available Skills Sitemap
 
 Always provide a clean summary of available Nexus-DevFlow skills grouped by lifecycle stage:
 
 ### 1. Mainline Lifecycle Stages (Linear Order)
-- `/00-discover` - Explore request, route inquiries, go/no-go under Discovery ID
-- `/10-define` - Lock delivery boundaries and allocate Running ID (`devflow/runs/{ID}`)
-- `/20-spec` - Formalize markdown-first specifications and acceptance criteria
-- `/30-plan` - Transform spec into executable task breakdown
-- `/40-implement` - Execute planned tasks incrementally with evidence
-- `/50-verify` - Senior QA review, validation checks, and pass/fail gate
-- `/60-report` - Generate standardized markdown and HTML summary report
-- `/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
-- `Goal` - Route broad goals before Discovery
-- `Brainstorm` - Ideate without allocating running IDs
-- `Research` - Conduct codebase or web research
-- `Debug` - Root cause investigation before or during implementation
-- `PRD` - Product framing before delivery commitment
-- `Issue-Triage` - Intake and triage incoming bug reports
-- `Security-Review` - High-severity security review
-- `Wiki` - Knowledge base management under `devflow/wiki/`
-- `Check-For-Updates` - Verify or upgrade DevFlow setup
-- `Help` - Process assistance and stage routing
+- `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
+- `debug` - Root cause investigation before or during implementation
+- `prd` - Product framing before delivery commitment
+- `issue-triage` - Intake and triage incoming bug reports
+- `security-review` - High-severity security review
+- `wiki` - Knowledge base management under `devflow/wiki/`
+- `check-for-updates` - Verify or upgrade DevFlow setup
+- `help` - Process assistance and stage routing
 
 ### 3. Engineering & Specialist Skills
 - **Frontend & UI**: `frontend-ui-engineering`, `nextjs-react-expert`, `tailwind-patterns`, `ui-ux-pro-max`, `mobile-design`

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

@@ -1,6 +1,6 @@
 ---
 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

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

@@ -0,0 +1,84 @@
+---
+name: doctor
+description: "[Devflow] Read-only DevFlow health check and diagnostics for context files, adapters, commands, and workflow drift."
+---
+
+# doctor - Read-Only DevFlow Health Check & Diagnostics
+
+Where this sits in the workflow:
+
+```text
+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.
+
+---
+
+## Input
+
+No argument is required.
+
+---
+
+## Diagnostics Checklist
+
+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`)
+  - `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)
+  - `findings.md` (Check if ledger exists)
+
+### Check 2: Tool Adapters Parity
+- Check if `.agents/skills/` exists and contains core lifecycle skills (`00-discover` through `70-release`, `devflow`, `onboard`, `adopt`, `doctor`).
+- Check if `.claude/skills/` is in sync with `.agents/skills/`.
+
+### Check 3: Commands & Script Verification
+- Inspect the Commands section in `AGENTS.md`.
+- Cross-reference with project manifest (`package.json`, `pyproject.toml`, `Cargo.toml`, etc.):
+  - Does the `Dev` command exist in scripts?
+  - Does the `Build` command exist in scripts?
+  - Does the `Test` command exist in scripts?
+  - Does the `Verify` command exist in scripts?
+
+### Check 4: Active Runs & Workflow Drift Detection
+- Inspect `devflow/runs/`:
+  - Are there active runs?
+  - Is `current-stage.md` consistent with the latest stage artifact in the active run?
+  - Are checklists (`checklists/implementation-checklist.md`, `checklists/verification-checklist.md`) properly tracked?
+  - Detect stage skips or workflow drift (e.g. jumping from `10-define` directly to `40-implement` without `20-spec` and `30-plan`).
+
+### Check 5: Findings Ledger Inspection
+- Inspect `devflow/context/findings.md`:
+  - Are there open P0 or P1 findings that block release?
+  - Are resolved findings properly closed?
+
+---
+
+## Output Format
+
+Present a clean, scannable diagnostic report:
+
+```markdown
+# 🩺 Nexus-DevFlow Health Report
+
+## Overall Status: [HEALTHY | WARNING | ACTION REQUIRED]
+
+| Component | Status | Details |
+| :--- | :--- | :--- |
+| **Context Files** | [PASS / WARN] | project-overview.md, coding-standards.md status |
+| **Tool Adapters** | [PASS / WARN] | .agents and .claude parity |
+| **Configured Commands**| [PASS / WARN] | dev, build, test, verify alignment |
+| **Active Runs & Drift**| [PASS / WARN] | active run status, stage progression |
+| **Findings Ledger** | [PASS / WARN] | open P0/P1 issues count |
+
+### Recommended Remediation Actions:
+1. [Action item if any warning or failure detected]
+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."
 ---
 
 ---

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

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

@@ -1,6 +1,6 @@
 ---
 name: goal
-description: Goal workflow
+description: "[Devflow] High-level goal routing and open-ended request intake before entering the 00-discover stage."
 ---
 
 ---

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

@@ -1,6 +1,6 @@
 ---
 name: handoff
-description: Compact active context into a handoff note. Use when a DevFlow run must continue in another session, agent, or report without duplicating existing artifacts.
+description: "[Devflow] Compact active context into a handoff note. Use when a DevFlow run must continue in another session, agent, or report without duplicating existing artifacts."
 disable-model-invocation: true
 ---
 

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

@@ -1,6 +1,6 @@
 ---name: help
 
-description: DevFlow 2.0 Help and routing guide. Transitional file while Help moves from numbered workflow to companion command.
+description: "[Devflow] DevFlow 2.0 help, routing guide, workflow sitemap, and process navigation."
 argument-hint: [optional: question, running id, stage, or issue]
 ---
 

package/template/.agents/skills/human-review-decisions/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: human-review-decisions
-description: Handle human approval, feedback, rejection, and recheck decisions around verified work. Use when a task needs a human gate after verification and the result must route cleanly back into the DevFlow 2.0 lifecycle.
+description: "[Devflow] Handle human approval, feedback, rejection, and recheck decisions around verified work. Use when a task needs a human gate after verification and the result must route cleanly back into the DevFlow 2.0 lifecycle."
 ---
 
 # Human Review Decisions

package/template/.agents/skills/i18n-localization/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: i18n-localization
-description: Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
+description: "[Devflow] Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support."
 allowed-tools: Read, Glob, Grep
 ---
 

package/template/.agents/skills/idea-refine/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: idea-refine
-description: Refines ideas iteratively. Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.
+description: "[Devflow] Refines ideas iteratively. Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger."
 ---
 
 # Idea Refine