@jakkrichm/create-nexus-devflow 2.0.6 → 2.0.9

package/template/.agents/skills/incremental-implementation/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: incremental-implementation
-description: Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
+description: "[Devflow] Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step."
 ---
 
 # Incremental Implementation

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

@@ -1,6 +1,6 @@
 ---name: insight
 
-description: Insight Extraction - Extract reusable lessons, file insights, patterns, gotchas, recommendations, and 9arm-skills/post-mortem learning from completed work.
+description: "[Devflow] Extract reusable lessons, patterns, file insights, and post-mortem learning from completed work."
 ---
 
 # Phase 54: Insight Extraction

package/template/.agents/skills/insight-capture/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: insight-capture
-description: Extract durable lessons, patterns, gotchas, and post-mortem knowledge from completed work. Use when implementation or verification work should become reusable team knowledge.
+description: "[Devflow] Extract durable lessons, patterns, gotchas, and post-mortem knowledge from completed work. Use when implementation or verification work should become reusable team knowledge."
 ---
 
 # Insight Capture

package/template/.agents/skills/intelligent-routing/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: intelligent-routing
-description: Automatic agent and stage routing for DevFlow 2.0. Use when deciding which active workflow, skill, or specialist should own the next step.
+description: "[Devflow] Automatic agent and stage routing for DevFlow 2.0. Use when deciding which active workflow, skill, or specialist should own the next step."
 version: 2.0.0
 ---
 

package/template/.agents/skills/issue-triage/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: issue-triage
-description: Issue-Triage workflow
+description: "[Devflow] Intake, categorize, and prioritize incoming issues and bug reports before delivery commitment."
 ---
 
 ---

package/template/.agents/skills/lint-and-validate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: lint-and-validate
-description: Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis.
+description: "[Devflow] Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis."
 allowed-tools: Read, Glob, Grep, Bash
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 name: mcp-builder
-description: MCP (Model Context Protocol) server building principles. Tool design, resource patterns, best practices.
+description: "[Devflow] MCP (Model Context Protocol) server building principles. Tool design, resource patterns, best practices."
 allowed-tools: Read, Write, Edit, Glob, Grep
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 name: md2html
-description: Convert long-form Markdown (plan, spec, system design, RFC, runbook, postmortem, brainstorm, notes) into a single self-contained HTML page with Mermaid diagrams, step timelines, callouts, sidebar TOC. Claude-orange light+dark theme. Multi-language. Portable across Claude Code / Codex / Antigravity / any AI agent.
+description: "[Devflow] Convert long-form Markdown (plan, spec, system design, RFC, runbook, postmortem, brainstorm, notes) into a single self-contained HTML page with Mermaid diagrams, step timelines, callouts, sidebar TOC. Claude-orange light+dark theme. Multi-language. Portable across Claude Code / Codex / Antigravity / any AI agent."
 trigger: /md2html
 ---
 

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

@@ -1,6 +1,6 @@
 ---name: merge
 
-description: PR Merge (Git Orchestration) - Safely merge the current feature branch into the base branch and clean up.
+description: "[Devflow] Safe PR branch merge into base branch, cleanup, and release readiness check."
 ---
 # Smart Merge (Git Orchestration)
 

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

@@ -1,6 +1,6 @@
 ---
 name: mobile-design
-description: Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps.
+description: "[Devflow] Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps."
 allowed-tools: Read, Glob, Grep, Bash
 ---
 

package/template/.agents/skills/nextjs-react-expert/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: react-best-practices
-description: React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations.
+description: "[Devflow] React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations."
 allowed-tools: Read, Write, Edit, Glob, Grep, Bash
 ---
 

package/template/.agents/skills/nodejs-best-practices/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: nodejs-best-practices
-description: Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.
+description: "[Devflow] Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying."
 allowed-tools: Read, Write, Edit, Glob, Grep
 ---
 

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

@@ -0,0 +1,129 @@
+---
+name: onboard
+description: "[Devflow] Set up Nexus-DevFlow after overlaying it onto a freshly scaffolded or early-stage project."
+---
+
+# onboard - Finish the Nexus-DevFlow Setup for Fresh Projects
+
+Where this sits in the workflow:
+
+```text
+scaffold app  ->  overlay DevFlow  ->  [onboard]  ->  /00-discover or /10-define  ->  Mainline Loop
+(user/tool)       (create-nexus)       (tune setup)   (discovery / run scoping)      (20-spec -> 70-release)
+```
+
+`/onboard` is the fresh-project on-ramp for Nexus-DevFlow. It assumes the application was scaffolded first (e.g. via `create-next-app`, `create-vite`, `cargo new`, etc.) and DevFlow was overlaid after.
+
+Run `/onboard` before starting discovery or delivery runs. Its job is to make DevFlow fit the real project from day one: detecting commands, project name, coding conventions, ignore rules, and tool adapters.
+
+Use `/adopt` instead when the app already has substantial shipped code, working routes, and existing business logic.
+
+---
+
+## Input
+
+No argument is required. If the user provides context about the stack, database, authentication, or preferred tooling, use it as a hint and verify against files.
+
+---
+
+## Step 0 - Confirm Onboarding vs Adoption
+
+Inspect the repository and context files:
+
+- If the project is freshly scaffolded with minimal boilerplate, proceed.
+- If `devflow/context/project-overview.md` and `devflow/context/coding-standards.md` already contain rich, user-customized content, do not overwrite them without explicit confirmation.
+- If the repository already has substantial existing routes, controllers, or database models, stop and recommend `/adopt` instead.
+
+Never run a framework scaffolder. DevFlow is already overlaid.
+
+---
+
+## Step 1 - Survey the Project Facts
+
+Read only enough to identify the setup:
+
+- **Package Manager & Lockfile**: `pnpm-lock.yaml`, `package-lock.json`, `yarn.lock`, `bun.lockb`, `Cargo.lock`, `poetry.lock`, `go.sum`, etc.
+- **Manifest Scripts**: `package.json`, `pyproject.toml`, `go.mod`, `Cargo.toml`, etc.
+- **Framework & Configs**: `tsconfig.json`, `next.config.*`, `vite.config.*`, `astro.config.*`, `tailwind.config.*`, database configs, test configs.
+- **Source Layout**: `src/`, `app/`, `pages/`, `components/`, `lib/`, etc.
+- **Existing Git & Ignore Rules**: `.gitignore`, git branches.
+- **Project Name**: Extracted from manifest, root directory, or user.
+
+---
+
+## Step 2 - Update Entry Files (AGENTS.md & CLAUDE.md)
+
+1. **Update `AGENTS.md` Commands**:
+   - Fill in the actual commands found in the project:
+     - `Dev`: dev server command (e.g. `npm run dev`)
+     - `Build`: production build command (e.g. `npm run build`)
+     - `Test`: test runner command (e.g. `npm test`, `vitest`, `pytest`)
+     - `Lint / Typecheck`: linting and typechecking commands
+     - `Verify`: combined verification command if present (e.g. `npm run check` or `npm run typecheck && npm test && npm run build`)
+   - If no test command exists, state explicitly that testing is opt-in and not yet configured.
+
+2. **Update `CLAUDE.md`**:
+   - Replace any `# Project Name` placeholder with the real detected project name.
+   - Keep `@AGENTS.md` and `@devflow/context/...` imports intact.
+
+---
+
+## Step 3 - Tune Coding Standards
+
+Update `devflow/context/coding-standards.md` to match the detected stack:
+
+- Framework, rendering model, and component architecture
+- Package manager and runtime
+- Project directory conventions
+- Styling approach (Tailwind CSS, Vanilla CSS, CSS Modules)
+- Data fetching, state management, and API boundaries
+- Validation and error handling expectations
+- Testing expectations
+
+Keep core general rules (functional style, small focused functions, clear naming) and replace template placeholders with real patterns.
+
+---
+
+## Step 4 - Check AI Interaction Rules
+
+Review `devflow/context/ai-interaction.md` and adjust if needed:
+- Language preferences (`artifact_language: "th"` or `"en"`)
+- Branching conventions
+- Review checkpoint expectations
+
+---
+
+## Step 5 - Check Ignore Files, Visibility & Tool Adapters
+
+1. **Update `.gitignore`**: Ensure common build artifacts, dependencies, and environment files are ignored.
+2. **DevFlow Visibility**:
+   - By default, keep DevFlow files tracked in git for team collaboration.
+   - If local-only mode is requested, add `devflow/`, `.agents/`, `.claude/`, `CLAUDE.md` to `.gitignore` while keeping `AGENTS.md` public.
+3. **Tool Adapters**:
+   - Codex & Antigravity use `.agents/skills/`.
+   - Claude Code uses `.claude/skills/`.
+   - Both can coexist cleanly.
+
+---
+
+## Step 6 - Initialize Project Overview
+
+Populate `devflow/context/project-overview.md` with baseline information:
+- Project Name and One-line Summary
+- Tech Stack & Tooling Architecture
+- Initial Repository Structure
+- Available Verified Commands
+
+---
+
+## Step 7 - Handoff to Planning
+
+Present a concise onboarding summary report:
+
+- Stack, framework, and package manager detected
+- Commands configured in `AGENTS.md`
+- Files tuned during onboarding
+- Adapter status (`.agents/`, `.claude/`)
+- Recommended next step:
+  - Run `00-discover` (or `/00-discover`, `$00-discover`) to explore the first feature or product direction
+  - Run `10-define` (or `/10-define`, `$10-define`) if the initial delivery slice is already clear and ready for execution

package/template/.agents/skills/package-json-generator/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: package-json-generator
-description: Generates or updates a package.json file with standardized npm scripts for the project. Automatically migrates tasks from .vscode/tasks.json if present. Use when initializing npm scripts, migrating from VS Code tasks, or setting up a centralized task runner.
+description: "[Devflow] Generates or updates a package.json file with standardized npm scripts for the project. Automatically migrates tasks from .vscode/tasks.json if present. Use when initializing npm scripts, migrating from VS Code tasks, or setting up a centralized task runner."
 ---
 
 # Package JSON Generator

package/template/.agents/skills/parallel-agents/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: parallel-agents
-description: Multi-agent orchestration patterns for the current DevFlow 2.0 specialist set. Use when multiple independent analyses or implementation perspectives can run in parallel.
+description: "[Devflow] Multi-agent orchestration patterns for the current DevFlow 2.0 specialist set. Use when multiple independent analyses or implementation perspectives can run in parallel."
 allowed-tools: Read, Glob, Grep
 ---
 

package/template/.agents/skills/performance-optimization/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: performance-optimization
-description: Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.
+description: "[Devflow] Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing."
 ---
 
 # Performance Optimization

package/template/.agents/skills/planning-and-task-breakdown/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: planning-and-task-breakdown
-description: Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
+description: "[Devflow] Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible."
 ---
 
 # Planning and Task Breakdown

package/template/.agents/skills/powershell-windows/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: powershell-windows
-description: PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.
+description: "[Devflow] PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling."
 allowed-tools: Read, Write, Edit, Glob, Grep, Bash
 ---
 

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

@@ -1,6 +1,6 @@
 ---name: pr
 
-description: Create Pull Request (Git Orchestration) - Create a well-formatted pull request from the current branch with a clear summary of changes and linked artifacts.
+description: "[Devflow] Pull Request creation with automated change summaries, verification evidence, and linked stage artifacts."
 ---
 # Create Pull Request (Git Orchestration)
 

package/template/.agents/skills/pr-review/SKILL.md

@@ -1,6 +1,6 @@
 ---name: pr-review
 
-description: PR Review Addon - Review a pull request using GitHub review prompt patterns and the credited 9arm-skills/scrutinize discipline.
+description: "[Devflow] PR Review Addon - Review a pull request using GitHub review prompt patterns and the credited 9arm-skills/scrutinize discipline."
 ---
 
 # Phase 55: PR Review Addon

package/template/.agents/skills/pr-review-analysis/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pr-review-analysis
-description: Review pull requests or local diffs with structured finding discipline, selective review lanes, and Nexus-DevFlow report templates. Use when the team needs a substantial review without turning review into a numbered workflow stage.
+description: "[Devflow] Review pull requests or local diffs with structured finding discipline, selective review lanes, and Nexus-DevFlow report templates. Use when the team needs a substantial review without turning review into a numbered workflow stage."
 ---
 
 # PR Review Analysis

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

@@ -1,6 +1,6 @@
 ---
 name: prd
-description: PRD workflow
+description: "[Devflow] Product Requirements Document drafting, user story mapping, and feature scoping before delivery commitment."
 ---
 
 ---

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

@@ -1,6 +1,6 @@
 ---
 name: preview
-description: Preview workflow
+description: "[Devflow] Local preview server management, smoke-check, and temporary runtime inspection before formal verification."
 ---
 
 ---

package/template/.agents/skills/preview-local-check/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: preview-local-check
-description: Manage local preview, smoke-check, and temporary runtime verification before formal verification. Use when implementation needs a quick visual or runtime check, when a reviewer needs a local URL, or when a change should be inspected before /50-Verify.
+description: "[Devflow] Manage local preview, smoke-check, and temporary runtime verification before formal verification. Use when implementation needs a quick visual or runtime check, when a reviewer needs a local URL, or when a change should be inspected before /50-Verify."
 ---
 
 # Preview Local Check

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

@@ -1,6 +1,6 @@
 ---
 name: prototype
-description: Build a throwaway prototype to answer a design question during Discover, Define, Spec, Research, or Plan.
+description: "[Devflow] Build a throwaway prototype to answer a design question during Discover, Define, Spec, Research, or Plan."
 disable-model-invocation: true
 ---
 

package/template/.agents/skills/python-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: python-patterns
-description: Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.
+description: "[Devflow] Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying."
 allowed-tools: Read, Write, Edit, Glob, Grep
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 name: release-git-operations
-description: Handle commit, pull request, merge, deployment, and changelog work around Release. Use when packaging verified work for sharing, integration, deployment, or release communication.
+description: "[Devflow] Handle commit, pull request, merge, deployment, and changelog work around Release. Use when packaging verified work for sharing, integration, deployment, or release communication."
 ---
 
 # Release Git Operations

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

@@ -1,6 +1,6 @@
 ---
 name: research
-description: Research workflow
+description: "[Devflow] Deep codebase or web research with source-backed citations to support discovery and spec stages."
 ---
 
 ---

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

@@ -1,6 +1,6 @@
 ---
 name: review
-description: Two-axis review for changed work. Use inside /50-Verify or /70-Release when a branch, PR, or work-in-progress diff needs standards and spec review.
+description: "[Devflow] Two-axis review for changed work. Use inside /50-Verify or /70-Release when a branch, PR, or work-in-progress diff needs standards and spec review."
 ---
 
 # Review

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

@@ -1,6 +1,6 @@
 ---
 name: review-followup-routing
-description: Classify review comments, extend existing work safely, and route corrective or future work back into the right DevFlow 2.0 stage. Use for PR follow-up and post-review follow-up planning.
+description: "[Devflow] Classify review comments, extend existing work safely, and route corrective or future work back into the right DevFlow 2.0 stage. Use for PR follow-up and post-review follow-up planning."
 ---
 
 # Review Follow-up Routing

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

@@ -1,6 +1,6 @@
 ---
 name: roadmap-strategy
-description: Create or refresh product roadmap direction using markdown-first discovery and roadmap artifacts. Use when strategic planning should stay outside the mainline but still follow DevFlow 2.0 contracts.
+description: "[Devflow] Create or refresh product roadmap direction using markdown-first discovery and roadmap artifacts. Use when strategic planning should stay outside the mainline but still follow DevFlow 2.0 contracts."
 ---
 
 # Roadmap Strategy

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

@@ -0,0 +1,108 @@
+---
+name: rollback
+description: "[Devflow] Plan safe feature or run reversal with dependency and commit risk analysis."
+---
+
+# rollback - Safe Feature Reversal & Rollback Planner
+
+Where this sits in the workflow:
+
+```text
+completed run + git history  ->  [rollback]  ->  /40-implement (or fix run)  ->  /50-verify  ->  /70-release
+(run archive + commits)          (risk review    (reverse product diff)          (prove)      (log & finalize)
+                                  + plan)
+```
+
+This skill **plans a rollback**. It does not silently alter product code, reset branches destructively, force-push, or mutate repository history. It identifies the completed run and its exact git commit, analyzes what changed afterward, drafts a guarded rollback specification, and stops for human review before execution.
+
+## Input
+
+A completed run by Running ID, name, or run path, plus an optional reason. Examples:
+
+```text
+/rollback RUN-002-add-onboard-adopt-doctor-skills
+/rollback "auth login" because OAuth provider changed
+/rollback devflow/runs/RUN-001-align-devflow-blueprint
+```
+
+With no target, list recent completed runs from `devflow/runs/` and `devflow/context/current-stage.md` and ask the user to choose. Never silently guess the target. If the reason is missing, ask for one before finalizing the rollback plan.
+
+## Step 0 - Preflight Check
+
+Read `AGENTS.md`, `devflow/context/current-stage.md`, `devflow/context/project-overview.md`, completed run archives under `devflow/runs/`, and git state.
+
+Stop before planning when:
+
+- The directory is not a git repository.
+- There is uncommitted active work in the working tree (unless the user asks to inspect it).
+- The target run cannot be identified unambiguously in `devflow/runs/` or Git history.
+
+Do not discard, force-reset, switch branches, or destroy untracked files automatically.
+
+## Step 1 - Resolve Target Run & Commits
+
+Match the requested ID or name against `devflow/runs/` and git commit history:
+
+```bash
+git log --grep="RUN-002" --oneline
+```
+
+Identify:
+
+- Exact commit SHA(s) introducing the feature.
+- Parent commit before the feature was introduced.
+- Associated stage artifacts (`20-spec.md`, `40-implement.md`, `70-release.md`).
+
+## Step 2 - Separate Product Changes From DevFlow History
+
+Inspect the files touched by the target commit(s).
+
+**Protected Workflow Paths (Never Revert Automatically):**
+- `.agents/**`
+- `.claude/**`
+- `devflow/**` (preserve run records, schemas, and historical reports)
+- `AGENTS.md` / `CLAUDE.md` (unless explicitly intended to update commands)
+- `.nexus/**`
+
+The rollback must preserve DevFlow's durable history while isolating the **Product Code Diff** (application code, UI components, backend APIs, configuration).
+
+## Step 3 - Review Later-Commit Risk (Dependency Risk Analysis)
+
+Inspect every commit after the target commit through `HEAD` that touches any of the product files.
+
+Classify the risk into one of 4 standard categories:
+
+| Risk Level | Meaning | Action |
+| :--- | :--- | :--- |
+| **No Overlap** | No subsequent commits touched these product files. | Clean reversal is safe and straightforward. |
+| **Overlap, Compatible** | Later edits touched the same files, but the target code can be cleanly extracted without breaking newer behavior. | Plan selective reverse-patching. |
+| **Dependency Risk** | Subsequent features or bugfixes directly depend on types, APIs, tables, or exports introduced by the target. | Explicitly warn that dependent features will be affected; plan compatibility shims. |
+| **Blocked** | Reversing the target would cause data loss, break database schema, or require a cascading rollback of multiple runs. | Stop and present the blocker to the user for explicit architectural guidance. |
+
+## Step 4 - Produce The Guarded Rollback Plan
+
+Draft the rollback plan containing:
+
+1. **Target Run & Rationale**: Running ID, original commit SHA, author, and reason for reversal.
+2. **Product Files to Revert**: Exact list of application files to modify/delete/restore.
+3. **Protected Paths**: Explicit declaration of preserved history files.
+4. **Risk Classification**: Dependency analysis findings and required compatibility repairs.
+5. **Step-by-Step Reversal Steps**:
+   - Step 1: Apply reverse product diff.
+   - Step 2: Apply compatibility fixes for downstream dependencies.
+   - Step 3: Run project verify command (`npm test`, `npm run check`).
+6. **Acceptance & Verification Criteria**: How to prove the removed behavior is truly gone without breaking existing unaffected features.
+
+## Step 5 - Stop For Human Confirmation
+
+Present the rollback plan to the user:
+
+- Summarize affected files and dependency risks.
+- If approved, route to `/40-implement` (or allocate a dedicated Fix/Rollback Run) to safely execute the reversal steps behind review gates.
+
+## Rules
+
+- **Preserve History**: Never delete run folders under `devflow/runs/`. Historical reports must remain intact.
+- **No Destructive Git Commands**: Never execute `git reset --hard HEAD~N` or `git push --force`. All reversals must be applied as forward commits.
+- **One Target Per Rollback**: Avoid bundling multiple unrelated rollbacks into one pass.
+- **Explicit Human Gate**: Always wait for user approval before applying any reverse diffs to code.

package/template/.agents/skills/security-and-hardening/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: security-and-hardening
-description: Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.
+description: "[Devflow] Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services."
 ---
 
 # Security and Hardening

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

@@ -1,6 +1,6 @@
 ---name: security-review
 
-description: High-severity security code review for folders, projects, files, or diffs with English Markdown output contract.
+description: "[Devflow] High-severity security code review and vulnerability audit for folders, projects, files, or diffs."
 argument-hint: "[target folder, project path, file list, or git diff] [--lang=en]"
 ---
 

package/template/.agents/skills/seo-fundamentals/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: seo-fundamentals
-description: SEO fundamentals, E-E-A-T, Core Web Vitals, and Google algorithm principles.
+description: "[Devflow] SEO fundamentals, E-E-A-T, Core Web Vitals, and Google algorithm principles."
 allowed-tools: Read, Glob, Grep
 ---
 

package/template/.agents/skills/server-management/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: server-management
-description: Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.
+description: "[Devflow] Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands."
 allowed-tools: Read, Write, Edit, Glob, Grep, Bash
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 name: shipping-and-launch
-description: Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
+description: "[Devflow] Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy."
 ---
 
 # Shipping and Launch

package/template/.agents/skills/silent-failure-audit/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: silent-failure-audit
-description: Audits error handling, logging, fallbacks, and observability for silent failures. Use after adding catch blocks, fallback logic, retry handling, optional chaining, or user-facing failure paths.
+description: "[Devflow] Audits error handling, logging, fallbacks, and observability for silent failures. Use after adding catch blocks, fallback logic, retry handling, optional chaining, or user-facing failure paths."
 ---
 
 # Silent Failure Audit

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

@@ -1,6 +1,6 @@
 ---
 name: simplify
-description: Simplify workflow
+description: "[Devflow] Code simplification and refactoring for clarity and maintainability without altering runtime behavior."
 ---
 
 ---

package/template/.agents/skills/skill-development/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: skill-development
-description: Guides the creation and maintenance of agent skills. Use when building new skills or modifying existing ones to ensure they follow the PRP framework standards.
+description: "[Devflow] Guides the creation and maintenance of agent skills. Use when building new skills or modifying existing ones to ensure they follow the PRP framework standards."
 ---
 
 # Skill Development (Skill Anatomy)

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

@@ -1,6 +1,6 @@
 ---
 name: spec-driven-development
-description: Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
+description: "[Devflow] Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea."
 ---
 
 # Spec-Driven Development

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

@@ -1,6 +1,6 @@
 ---
 name: spec-orchestration
-description: Coordinate Brainstorm, Research, PRD, competitor context, and spec critique before the work re-enters the numbered mainline. Use when a broad idea needs orchestration rather than a straight pass.
+description: "[Devflow] Coordinate Brainstorm, Research, PRD, competitor context, and spec critique before the work re-enters the numbered mainline. Use when a broad idea needs orchestration rather than a straight pass."
 ---
 
 # Spec Orchestration

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

@@ -1,6 +1,6 @@
 ---
 name: specialist-agent-routing
-description: Route a request to the right specialist agent and preserve the DevFlow 2.0 stage-first contract. Use when the user wants direct specialist judgment on a file, folder, workspace, or concern.
+description: "[Devflow] Route a request to the right specialist agent and preserve the DevFlow 2.0 stage-first contract. Use when the user wants direct specialist judgment on a file, folder, workspace, or concern."
 ---
 
 # Specialist Agent Routing

package/template/.agents/skills/tailwind-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: tailwind-patterns
-description: Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.
+description: "[Devflow] Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture."
 allowed-tools: Read, Write, Edit, Glob, Grep
 ---