@jakkrichm/create-nexus-devflow 2.0.8 → 2.0.9

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@jakkrichm/create-nexus-devflow",
-  "version": "2.0.8",
-  "description": "Install or update the agent-ready DevFlow 2.0 workflow layer into a scaffolded or existing project.",
+  "version": "2.0.9",
+  "description": "Installer package for Nexus-DevFlow agentic workflow layer.",
   "license": "MIT",
   "author": "Jakkrich",
   "homepage": "https://github.com/Jakkrich/nexus-devflow#readme",

package/template/.agents/skills/00-discover/SKILL.md

@@ -1,6 +1,6 @@
 ---name: 00-discover
 
-description: Discover stage in DevFlow 2.0 - explore a request, route supporting inquiry, and decide whether delivery work should begin without allocating a running ID.
+description: "[Devflow] Discover stage in DevFlow 2.0 - explore a request, route supporting inquiry, and decide whether delivery work should begin without allocating a running ID."
 argument-hint: "{title, request, or discovery-id}"
 ---
 

package/template/.agents/skills/10-define/SKILL.md

@@ -1,6 +1,6 @@
 ---name: 10-define
 
-description: Define stage in DevFlow 2.0 - turn an approved discovery into one or more bounded delivery runs with stable scope.
+description: "[Devflow] Define stage in DevFlow 2.0 - turn an approved discovery into one or more bounded delivery runs with stable scope."
 argument-hint: "{approved discovery-id, discovery path, running-id, or run path}"
 ---
 

package/template/.agents/skills/20-spec/SKILL.md

@@ -1,6 +1,6 @@
 ---name: 20-spec
 
-description: Spec stage in DevFlow 2.0 - write the formal markdown-first specification from a stable definition.
+description: "[Devflow] Spec stage in DevFlow 2.0 - write the formal markdown-first specification from a stable definition."
 argument-hint: "{running-id or workspace path}"
 ---
 

package/template/.agents/skills/30-plan/SKILL.md

@@ -1,6 +1,6 @@
 ---name: 30-plan
 
-description: Plan implementation in DevFlow 2.0 - transform `20-spec.md` into a markdown-first executable plan.
+description: "[Devflow] Plan stage in DevFlow 2.0 - transform 20-spec.md into an executable task breakdown with test decisions."
 ---
 # Phase 30: Plan Implementation
 

package/template/.agents/skills/40-implement/SKILL.md

@@ -1,6 +1,6 @@
 ---name: 40-implement
 
-description: Implement code in DevFlow 2.0 - execute one planned unit at a time with markdown-first implementation evidence.
+description: "[Devflow] Implement stage in DevFlow 2.0 - execute planned tasks incrementally with evidence and unit tests."
 ---
 # Phase 40: Implement Code
 

package/template/.agents/skills/50-verify/SKILL.md

@@ -1,6 +1,6 @@
 ---name: 50-verify
 
-description: Verify quality in DevFlow 2.0 - perform senior QA review, record evidence, and decide pass or return-to-implement.
+description: "[Devflow] Verify stage in DevFlow 2.0 - perform senior QA review, record evidence, and decide pass or return-to-implement."
 ---
 # Phase 50: Verify Quality
 

package/template/.agents/skills/60-report/SKILL.md

@@ -1,6 +1,6 @@
 ---name: 60-report
 
-description: Report stage in DevFlow 2.0 - produce the final standardized markdown and HTML summary for the full running flow.
+description: "[Devflow] Report stage in DevFlow 2.0 - produce standardized markdown and HTML summary report for the completed run."
 argument-hint: "{running-id or workspace path}"
 ---
 

package/template/.agents/skills/70-release/SKILL.md

@@ -1,6 +1,6 @@
 ---name: 70-release
 
-description: Release stage in DevFlow 2.0 - package verified work for delivery, merge, PR, deployment, or handoff.
+description: "[Devflow] Release stage in DevFlow 2.0 - package verified work for delivery, git merge, PR, or deployment."
 argument-hint: "{running-id or workspace path}"
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 name: adopt
-description: Bootstrap Nexus-DevFlow into an existing (brownfield) codebase. Surveys the real repository (read-only), interviews the user for intent, generates project-overview.md and coding-standards.md from existing code, tunes AGENTS.md commands, and seeds the initial Discovery or Run map. Use when the user runs adopt, /adopt, $adopt, is overlaying DevFlow onto an app that already has meaningful code, or asks to adopt DevFlow into an existing project. For freshly scaffolded or early projects, use onboard instead.
+description: "[Devflow] Survey existing brownfield codebase and bootstrap DevFlow context files."
 ---
 
 # adopt - Bootstrap Nexus-DevFlow from an Existing Codebase

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

@@ -1,6 +1,6 @@
 ---name: agent
 
-description: Invoke Agent - Run a specialist persona on a file, folder, stage artifact, or codebase concern.
+description: "[Devflow] Invoke specialist persona or role-based agent on a target file, folder, stage artifact, or concern."
 ---
 # Phase 90: Invoke Agent
 

package/template/.agents/skills/api-and-interface-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: api-and-interface-design
-description: Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
+description: "[Devflow] Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend."
 ---
 
 # API and Interface Design

package/template/.agents/skills/app-builder/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: app-builder
-description: Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.
+description: "[Devflow] Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents."
 allowed-tools: Read, Write, Edit, Glob, Grep, Bash, Agent
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 name: architecture
-description: Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
+description: "[Devflow] Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design."
 allowed-tools: Read, Glob, Grep
 ---
 

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

@@ -0,0 +1,175 @@
+---
+name: autopilot
+description: "[Devflow] Optional explicit mode for one bounded spec/plan/implement/verify/report pass with checkpoint commits and review packet."
+---
+
+# autopilot - Autonomous Bounded DevFlow Loop
+
+Where this sits in the workflow:
+
+```text
+/devflow  ->  [autopilot]  ->  review packet  ->  /70-release
+(where        (spec, plan,     (human review,     (package, PR,
+ are we?)      build, verify,   walkthrough)       merge with approval)
+               report)
+```
+
+Autopilot is an explicit opt-in execution skill for Nexus-DevFlow 2.0. It runs a single bounded loop across the delivery lifecycle (**`20-spec` -> `30-plan` -> `40-implement` -> `50-verify` -> `60-report`**) without requiring human confirmation between every sub-step.
+
+It does **not** replace the normal step-by-step workflow. Mainline commands (`/20-spec`, `/30-plan`, `/40-implement`, `/50-verify`, `/60-report`, `/70-release`) remain the conservative default.
+
+Do not suggest Autopilot as the default next action. Use it only when the user explicitly asks for it.
+
+The explicit Autopilot request is permission to create checkpoint commits on the feature or fix branch after passing implementation steps. It is **not** permission to merge into `main`, push to remote, deploy, publish, delete data, or run destructive actions.
+
+## Input
+
+Common forms:
+
+- **No argument**: resume the active run in `devflow/context/current-stage.md`, or target the next planned run/feature in `devflow/context/project-overview.md`.
+- **Running ID or feature name**: target that run, e.g. `/autopilot RUN-004` or `/autopilot "add user authentication"`.
+- **`fix "<issue>"`**: write and execute an ad-hoc fix run.
+- **`resume`**: continue the current active run on its existing branch.
+
+If the requested target conflicts with a run already in progress, stop and ask which one should win. Do not overwrite active stage artifacts silently.
+
+> [!IMPORTANT]
+> Rollback is intentionally excluded from Autopilot. If the request is a rollback or the stage is marked Rollback, stop and direct the user to `/rollback` and reviewed `/40-implement`. Reversing completed work requires explicit dependency and human review gates.
+
+---
+
+## Step 1 - Preflight & Safety Check
+
+Read the project state:
+
+- `AGENTS.md` & `CLAUDE.md`
+- `devflow/context/project-overview.md`
+- `devflow/context/current-stage.md`
+- `devflow/context/coding-standards.md`
+- `devflow/context/ai-interaction.md`
+- `devflow/context/findings.md`
+- git branch, status, and recent log
+
+Stop before changing files when:
+
+1. The repo is not a git repository.
+2. The working tree is dirty with uncommitted changes unrelated to this run.
+3. `current-stage.md` has an active run and the user requested a different target without resolving conflict.
+4. The task requires architectural, financial, auth, billing, or destructive decisions not documented in the context.
+
+---
+
+## Step 2 - Choose or Write Specification (`20-spec`)
+
+1. If `devflow/runs/{running-id}-{slug}/20-spec.md` already exists, resume it.
+2. If no spec exists:
+   - Ensure `10-define.md` exists with locked scope and allocated Running ID.
+   - Write `20-spec.md` following the DevFlow specification schema.
+   - Critique and red-team the spec (edge cases, unhappy paths, testable criteria).
+   - Apply fixes to the spec.
+
+---
+
+## Step 3 - Branch Setup & Implementation Plan (`30-plan`)
+
+1. **Branch Management**:
+   - Feature: `feature/{slug}-{running-id}`
+   - Fix: `fix/{slug}-{running-id}`
+   - Switch to or create the working branch. Never run Autopilot directly on `main` or `master`.
+2. **Planning**:
+   - Write `devflow/runs/{running-id}-{slug}/30-plan.md`.
+   - Seed `checklists/implementation-checklist.md` and `checklists/verification-checklist.md`.
+
+---
+
+## Step 4 - Implement in Small Increments (`40-implement`)
+
+Work through the implementation checklist in order. Each step must remain reviewable.
+
+For every subtask:
+
+1. Implement only that scoped unit.
+2. Run relevant verification (unit tests, typecheck, lint, build).
+3. If UI is involved, inspect behavior, verify console errors and network calls.
+4. Self-review diff against `coding-standards.md`.
+5. Fix issues and rerun failed checks.
+6. Mark the task checked `[x]` in `checklists/implementation-checklist.md`.
+7. **Create a Checkpoint Commit** on the feature/fix branch for the passing step:
+   ```bash
+   git add <modified-files> devflow/runs/{running-id}-{slug}/checklists/implementation-checklist.md
+   git commit -m "feat({running-id}): checkpoint <concise step description>"
+   ```
+8. Write `devflow/runs/{running-id}-{slug}/40-implement.md`.
+
+---
+
+## Step 5 - Senior QA Verification (`50-verify`)
+
+1. Execute full project verification commands:
+   - Framework integrity (`npm run check` or equivalent)
+   - Static contracts (`npm run check:static` when applicable)
+   - Project test suite (Unit tests, integration tests)
+   - Build / Package smoke tests
+2. Update `checklists/verification-checklist.md` with concrete evidence.
+3. Write `devflow/runs/{running-id}-{slug}/50-verify.md` with QA verdict (`PASS` / `FAIL`).
+
+---
+
+## Step 6 - Targeted Quality Audit & Repair
+
+Review diffs and inspect `devflow/context/findings.md`:
+
+1. **Repair confirmed P0 and P1 findings** within the current run scope.
+2. Update finding status in `devflow/context/findings.md`.
+3. Rerun verification tests after repairs.
+4. Create a checkpoint commit for the fix.
+5. If a P0/P1 finding cannot be repaired within scope or fails twice consecutively, stop immediately and report.
+
+---
+
+## Step 7 - Delivery Digest & Review Packet (`60-report`)
+
+1. Write `devflow/runs/{running-id}-{slug}/60-report.md`.
+2. Render standalone HTML dashboard `devflow/runs/{running-id}-{slug}/60-report.html` (via `md2html` or report generator).
+3. Update `devflow/context/current-stage.md` to indicate ready for `/70-release`.
+4. Stop with a concise **Review Packet Dashboard** for human approval.
+
+---
+
+## 🛑 Strict Hard Stops (Never Exceed)
+
+Stop immediately and report to the user instead of continuing when Autopilot would need to:
+
+- Commit directly to `main` or `master`, merge branches, delete branches, or force push.
+- Run `git push` to remote repositories.
+- Deploy to staging/production or publish packages to npm/registries.
+- Delete data, drop databases, or run irreversible destructive migrations.
+- Make product, business, or architecture decisions not specified in the context.
+- Continue after two failed attempts to fix the same issue (Two-attempt hard stop).
+
+---
+
+## Output Review Packet Format
+
+When Autopilot finishes successfully, output a scannable review packet:
+
+```markdown
+### 🛸 Autopilot Execution Summary: [{running-id}]
+
+- **Branch**: `{branch-name}`
+- **Target Run**: `{running-id} - {title}`
+- **Artifacts Generated**:
+  - Spec: `devflow/runs/{id}/20-spec.md`
+  - Plan: `devflow/runs/{id}/30-plan.md`
+  - Implement Evidence: `devflow/runs/{id}/40-implement.md`
+  - QA Verify Report: `devflow/runs/{id}/50-verify.md`
+  - Digest Report: `devflow/runs/{id}/60-report.md`
+  - HTML Dashboard: `devflow/runs/{id}/60-report.html`
+- **Validation & Tests**: `All Passed (Green)`
+- **Checkpoint Commits**: `{count} commits created on {branch-name}`
+- **Manual QA Walkthrough**: Run `/try {running-id}` for human review guide
+
+---
+👉 **Next Recommended Action**:
+Inspect diffs and `/try` walkthrough, then run `/70-release {running-id}` to package, merge, or create PR.
+```

package/template/.agents/skills/bash-linux/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bash-linux
-description: Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.
+description: "[Devflow] Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems."
 allowed-tools: Read, Write, Edit, Glob, Grep, Bash
 ---
 

package/template/.agents/skills/behavioral-modes/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: behavioral-modes
-description: AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.
+description: "[Devflow] AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type."
 allowed-tools: Read, Glob, Grep
 ---
 

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

@@ -1,6 +1,6 @@
 ---name: brainstorm
 
-description: Structured brainstorming for projects and features. Transitional compatibility path for the Brainstorm companion command in DevFlow 2.0.
+description: "[Devflow] Structured divergent and convergent ideation for features and ideas without allocating running IDs."
 ---
 
 # Brainstorm - Structured Idea Exploration

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

@@ -0,0 +1,77 @@
+---
+name: brief
+description: "[Devflow] Read-only scope, dependency, and risk pre-briefing before speccing a run."
+---
+
+# brief - Scope, Dependency & Risk Pre-Check
+
+Where this sits in the workflow:
+
+```text
+10-define or project-overview.md  ->  [brief]  ->  /20-spec  ->  /30-plan  ->  /40-implement
+(proposed scope & context)            (read-only   (write        (break down)  (build it)
+                                      explainer)    contract)
+```
+
+This skill answers one essential question: ***"What does this upcoming feature or run actually involve before I commit to writing a full specification?"***
+
+It inspects the relevant context files and provides a concise briefing so the team can decide whether to spec it now, split it into smaller runs, reorder priorities, or clear an architectural blocker first.
+
+It is **strictly read-only 100%**. It never writes specs, creates directories, branches, or commits code.
+
+## Input
+
+- **no argument**: briefs the active run in `devflow/context/current-stage.md` (or the first planned feature in `devflow/context/project-overview.md`).
+- **running ID or feature name**: e.g. `/brief RUN-003`, `/brief "OAuth Login"`.
+- **topic / concern**: e.g. `/brief "database migration"`.
+
+If there is no active run and the overview does not list planned features, plainly report that context is needed and recommend `/00-discover` or `/10-define`.
+
+## Step 1 - Read Context (Read-Only)
+
+Gather and synthesize:
+
+1. **Active/Target Scope**: Target Running ID, `10-define.md`, or roadmap feature item.
+2. **Project Context**: `devflow/context/project-overview.md` (Data models, architecture layout, primary stack, existing shipped capabilities).
+3. **Existing Codebase State**: Inspect existing directory structures, schemas, and routes touching this feature.
+4. **Dependencies**: What previously completed runs (`devflow/runs/`) or modules must be in place first.
+
+## Step 2 - Analyze & Assess
+
+Evaluate:
+
+- **What It Is**: Core capability and user-visible or system-visible outcome.
+- **Depends On**: Required upstream models, tables, APIs, environment variables, or sibling runs.
+- **Unblocks**: Downstream features or workflows that this run enables.
+- **Touches**: Files, modules, API routes, database tables, or UI components likely to change.
+- **Estimated Size**: Small (S), Medium (M), Large (L), or Extra-Large (XL - recommend splitting in `/10-define`).
+- **Open Questions & Risks**: Ambiguous requirements, missing external APIs, or complex migrations.
+
+## Step 3 - Output Structured Briefing
+
+Produce a short, scannable briefing:
+
+```markdown
+### 📋 Feature Briefing: [Feature / Run Name]
+
+- **What**: Brief summary of the core outcome.
+- **Depends On**: Prerequisite modules, runs, or infrastructure.
+- **Unblocks**: Downstream capabilities enabled by this feature.
+- **Touches**: Anticipated files, schemas, endpoints, and UI views.
+- **Estimated Scope & Size**: `[S / M / L / XL]` (and split recommendation if XL).
+- **Key Risks & Open Questions**: Technical or product unknowns that must be settled in `/20-spec`.
+
+---
+👉 **Next Recommended Action**: `/20-spec {running-id}` (or resolve prerequisite blocker first).
+```
+
+## Rules
+
+- **Always Read-Only**: Never edit any workspace file, never allocate running IDs, never commit or execute scripts.
+- **Explain, Don't Spec**: Focus on scope, architectural dependencies, and size estimation. The formal delivery contract is the responsibility of `/20-spec`.
+- **Ground In Reality**: Trace all assertions back to `project-overview.md` or actual codebase facts. Do not invent non-existent packages or fictional architecture.
+- **Highlight Blockers Early**: Flagging a missing prerequisite before speccing is the primary value of this command.
+
+## Output Formatting
+
+Follow the project conventions in `devflow/context/ai-interaction.md`: concise, scannable markdown with bold labels and actionable bullet points.

package/template/.agents/skills/browser-testing-with-devtools/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: browser-testing-with-devtools
-description: Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP.
+description: "[Devflow] Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP."
 ---
 
 # Browser Testing with DevTools

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

@@ -1,6 +1,6 @@
 ---name: changelog
 
-description: Update CHANGELOG.md - Automatically gather changes from specs, git history, or current state to update the project changelog.
+description: "[Devflow] Update CHANGELOG.md automatically from specs, git commits, and stage report history."
 ---
 # Phase 53: Update Changelog
 

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