@jakkrichm/create-nexus-devflow 2.0.6 → 2.0.9

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

@@ -1,6 +1,6 @@
 ---
 name: test
-description: Test workflow
+description: "[Devflow] Test execution, missing test generation, and coverage analysis across unit, integration, and smoke test suites."
 ---
 
 ---

package/template/.agents/skills/test-driven-development/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: test-driven-development
-description: Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
+description: "[Devflow] Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality."
 ---
 
 # Test-Driven Development

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

@@ -1,6 +1,6 @@
 ---
 name: test-execution-and-coverage
-description: Generate missing tests, run existing tests, and summarize coverage and failures. Use when implementation or verification needs explicit testing evidence beyond a general TDD reminder.
+description: "[Devflow] Generate missing tests, run existing tests, and summarize coverage and failures. Use when implementation or verification needs explicit testing evidence beyond a general TDD reminder."
 ---
 
 # Test Execution And Coverage

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

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

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

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

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

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

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

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

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

@@ -1,6 +1,6 @@
 ---
 name: verification-orchestration
-description: Coordinate multi-lane QA, specialist review, test planning, and verification follow-up. Use when /50-Verify needs more structure than a single pass and the team needs a QA matrix or specialist routing.
+description: "[Devflow] Coordinate multi-lane QA, specialist review, test planning, and verification follow-up. Use when /50-Verify needs more structure than a single pass and the team needs a QA matrix or specialist routing."
 ---
 
 # Verification Orchestration

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

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

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

@@ -1,6 +1,6 @@
 ---name: wiki
 
-description: DevFlow Wiki - Ingest, query, lint, and promote compiled project or framework knowledge.
+description: "[Devflow] Knowledge base management, ingestion, linting, and querying under devflow/wiki/."
 ---
 # Wiki
 

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

@@ -1,6 +1,6 @@
 ---
 name: workflow-documentation-sync
-description: Enforces the synchronization and comprehensive update of documentation, manuals, usage guides, and examples whenever a new workflow is introduced or modified in the project. Use when introducing new workflows or changing existing ones.
+description: "[Devflow] Enforces the synchronization and comprehensive update of documentation, manuals, usage guides, and examples whenever a new workflow is introduced or modified in the project. Use when introducing new workflows or changing existing ones."
 ---
 
 # Workflow Documentation Sync

package/template/.claude/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/.claude/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/.claude/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/.claude/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/.claude/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/.claude/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/.claude/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/.claude/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/.claude/skills/adopt/SKILL.md

@@ -0,0 +1,95 @@
+---
+name: adopt
+description: "[Devflow] Survey existing brownfield codebase and bootstrap DevFlow context files."
+---
+
+# adopt - Bootstrap Nexus-DevFlow from an Existing Codebase
+
+Where this sits in the workflow:
+
+```text
+existing codebase  ->  [adopt]  ->  project-overview + coding-standards  ->  /00-discover or /10-define
+(already has code)     (survey +    (seeded from the real code;               (first feature / refactoring
+                        interview)   shipped architecture documented)          delivery lifecycle)
+```
+
+Standard onboarding assumes a freshly scaffolded, near-empty app. That does not fit a codebase that already has thousands of lines of working code.
+
+`/adopt` is the brownfield on-ramp for Nexus-DevFlow: it reads what is already there, asks only for what the code cannot reveal (the *intent*, the *why*, and the *upcoming roadmap*), and produces the exact context files the rest of the DevFlow lifecycle expects (`project-overview.md`, `coding-standards.md`, `AGENTS.md` commands).
+
+---
+
+## Input
+
+A description of what the project is, if provided. Otherwise, inspect the repository directly. No argument is required.
+
+---
+
+## Step 0 - Confirm Brownfield Safety
+
+Inspect `devflow/context/project-overview.md` and `devflow/context/coding-standards.md`:
+
+- If they contain default placeholders or empty templates, proceed.
+- If they already hold rich, user-owned content, stop and inform the user; offer to refresh specific sections rather than overwriting existing context without confirmation.
+
+Never run a framework scaffolder (DevFlow is an overlay, never a generator).
+
+---
+
+## Step 1 - Survey the Codebase (Read-Only)
+
+Read the repository to establish the facts. Change nothing in this step:
+
+- **Stack & Tooling**: Languages, frameworks, and versions from manifest files (`package.json`, `requirements.txt`, `pyproject.toml`, `go.mod`, `Cargo.toml`, etc.). Note the active package manager from lockfiles.
+- **Commands**: Real dev, build, test, lint, and verify scripts.
+- **Conventions in Practice**: Directory layout, component naming, state management, styling, data-fetching, error handling, validation. Read what the code *actually does*.
+- **Testing Reality**: Inspect existing test suites, runners, and coverage. Be honest about test status.
+- **Shipped Capabilities & Architecture**: Inferred from routes, pages, controllers, database schemas, and entry points.
+
+Keep structured notes for generation in Step 3.
+
+---
+
+## Step 2 - Interview for Intent
+
+The code reveals *what* and *how*, but not *why* or *what next*. Ask a short set of 3-4 questions to fill the gaps:
+
+1. **Purpose & Users**: What is the core problem this project solves, and who are the target users?
+2. **Architecture Status**: Is the current structure and stack intentional, or are there legacy parts/technical debt the team wants to change or refactor?
+3. **Upcoming Roadmap**: What are the top priorities to build, fix, or refactor next?
+4. **Clarifications**: Anything the survey got wrong or missed?
+
+*(If the user already provided this context in the prompt, skip questions that are already answered).*
+
+---
+
+## Step 3 - Generate the Context Artifacts
+
+Write the baseline context files drawn from the survey (facts) and interview (intent):
+
+1. **`devflow/context/project-overview.md`**:
+   - Project Name, Purpose, and Target Users
+   - Architecture summary and directory layout
+   - Shipped capabilities and existing major modules
+   - Key technical stack components and verified commands
+   - Known technical debt or architectural focus areas
+
+2. **`devflow/context/coding-standards.md`**:
+   - Rewrite defaults to reflect the project's *actual* conventions discovered in Step 1
+   - Framework patterns, state management, error handling, styling, and test rules based on real code
+
+3. **`AGENTS.md` Commands Section**:
+   - Fill in the real dev, build, test, lint, and verify commands found during survey.
+
+---
+
+## Step 4 - Review Gate and Handoff
+
+Present the adoption summary for review:
+
+- Shipped features and architectural baseline recorded
+- Inferred conventions and coding standards
+- Available verified commands in `AGENTS.md`
+- Recommended next step:
+  - Run `00-discover` (or `/00-discover`, `$00-discover`) to explore the next major initiative or feature
+  - Run `10-define` (or `/10-define`, `$10-define`) to immediately scope a delivery run for known roadmap items

package/template/.claude/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/.claude/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/.claude/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/.claude/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/.claude/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/.claude/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/.claude/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/.claude/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