@jakkrichm/create-nexus-devflow 2.0.8 → 2.0.10

package/template/.claude/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
@@ -70,8 +70,8 @@ Use the smallest durable destination:
 
 - stage artifacts when the lesson is specific to the current run
 - `devflow/lessons.md` for project-wide lessons
-- `/60-Report` for final narrative communication before release
-- `/70-Release` for release-facing notes and execution details
+- `60-report` for final narrative communication before release
+- `70-release` for release-facing notes and execution details
 
 For token/context learning, prefer the smallest concrete note:
 
@@ -104,22 +104,22 @@ If `post-mortem` was applied, include a short `Source Discipline` note crediting
 
 - Classification: Companion command
 - Mainline status: Knowledge capture command, not a numbered stage
-- Typical entry points: after `Debug`, `/50-Verify`, incident work, or review findings
-- Typical handoff targets: `Wiki`, `/60-Report`, `Help`
+- Typical entry points: after `Debug`, `50-verify`, incident work, or review findings
+- Typical handoff targets: `Wiki`, `60-report`, `Help`
 
 ## Sources
 
 - `AGENTS.md`
 - `.agent/resources/schemas/lessons.template.md`
-- Related commands: `Debug`, `/50-Verify`, `Wiki`, `/60-Report`, `Help`
+- Related commands: `Debug`, `50-verify`, `Wiki`, `60-report`, `Help`
 
 ## Next Workflow Recommendation
 
 - **Primary**: `Wiki project ingest {source}` when the insight is reusable project knowledge.
 - **Why**: `Insight` extracts lessons; `Wiki` compiles selected lessons into navigable knowledge pages.
 - **Alternatives**:
-  - `/60-Report {ID}` - choose this when the insight should become the final communication summary before release.
-  - `/70-Release {ID}` - choose this when the insight should shape release packaging or execution details.
+  - `60-report {ID}` - choose this when the insight should become the final communication summary before release.
+  - `70-release {ID}` - choose this when the insight should shape release packaging or execution details.
   - `Help {ID}` - choose this when the next route is unclear.
 
 ## Wiki Update Recommendation

package/template/.claude/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
@@ -20,7 +20,7 @@ This skill should reuse and align with:
 
 ## When to Use
 
-- after `/50-Verify`, release preparation, or a completed implementation run
+- after `50-verify`, release preparation, or a completed implementation run
 - after debugging, regression fixes, or incidents that deserve durable learning
 - when reusable project knowledge should move into lessons, wiki material, or final reporting
 
@@ -68,7 +68,7 @@ Prefer:
 - stage artifacts when the lesson is run-specific
 - `devflow/lessons.md` for project-wide knowledge
 - `Wiki` when the knowledge should become navigable team documentation
-- `/60-Report` when the lesson belongs in the final communication package before release
+- `60-report` when the lesson belongs in the final communication package before release
 
 When updating `devflow/lessons.md`, use `.agent/resources/schemas/lessons.template.md` and replace placeholder text completely.
 
@@ -81,4 +81,4 @@ Return:
 - approach outcome
 - recommendations
 - where the insight was recorded
-- whether `Wiki` or `/60-Report` should be the next handoff
+- whether `Wiki` or `60-report` should be the next handoff

package/template/.claude/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
 ---
 
@@ -25,7 +25,7 @@ When routing to support skills, follow `docs/skill-selection-policy.md`.
 
 ## Timeline Stages
 
-`/00-Discover -> /10-Define -> /20-Spec -> /30-Plan -> /40-Implement -> /50-Verify -> /60-Report -> /70-Release`
+`00-discover -> 10-define -> 20-spec -> 30-plan -> 40-implement -> 50-verify -> 60-report -> 70-release`
 
 ## Public Companion Commands
 
@@ -66,14 +66,14 @@ Use these agent mappings when expert judgment is the best next step:
 
 | User State | Recommended Route |
 |---|---|
-| new request, vague or clear | `/00-Discover`; it selects support inquiry and owns the delivery decision |
-| approved discovery needs one or more delivery boundaries | `/10-Define {discovery_id}` |
-| needs requirements and acceptance criteria | `/20-Spec` |
-| has a stable spec and needs execution plan | `/30-Plan` |
-| needs implementation work | `/40-Implement` |
-| needs testing, review, or validation evidence | `/50-Verify` |
-| needs packaging, commit, PR, or release handling | `/70-Release` |
-| needs the final summary or handoff narrative | `/60-Report` |
+| new request, vague or clear | `00-discover`; it selects support inquiry and owns the delivery decision |
+| approved discovery needs one or more delivery boundaries | `10-define {discovery_id}` |
+| needs requirements and acceptance criteria | `20-spec` |
+| has a stable spec and needs execution plan | `30-plan` |
+| needs implementation work | `40-implement` |
+| needs testing, review, or validation evidence | `50-verify` |
+| needs packaging, commit, PR, or release handling | `70-release` |
+| needs the final summary or handoff narrative | `60-report` |
 
 ## Routing Heuristics
 
@@ -97,9 +97,9 @@ Use these agent mappings when expert judgment is the best next step:
 
 If `grill-with-docs` is available in the current environment, prefer it as an optional internal support skill for:
 
-- `/10-Define` when scope or terminology is unstable
-- `/20-Spec` when acceptance criteria or rules are ambiguous
-- `/30-Plan` when architecture or verification choices are still reversible but unclear
+- `10-define` when scope or terminology is unstable
+- `20-spec` when acceptance criteria or rules are ambiguous
+- `30-plan` when architecture or verification choices are still reversible but unclear
 
 Do not use deep questioning by default in every stage. Collect only the information that affects the current Timeline-stage decision.
 
@@ -111,9 +111,9 @@ Do not use deep questioning by default in every stage. Collect only the informat
 
 If `grill-with-docs` is available in the current environment, prefer it as an optional internal support skill for:
 
-- `/10-Define` when scope or terminology is unstable
-- `/20-Spec` when acceptance criteria or rules are ambiguous
-- `/30-Plan` when architecture or verification choices are still reversible but unclear
+- `10-define` when scope or terminology is unstable
+- `20-spec` when acceptance criteria or rules are ambiguous
+- `30-plan` when architecture or verification choices are still reversible but unclear
 
 Do not use deep questioning by default in every stage. Collect only the information that affects the current stage decision.
 
@@ -145,18 +145,18 @@ Key conflict defaults:
 | `grilling` vs `grill-with-docs` | `grill-with-docs` when a codebase or durable docs matter |
 | `grill-with-docs` vs `domain-modeling` | `grill-with-docs` interviews; `domain-modeling` records confirmed glossary terms or ADRs |
 | `to-prd` vs `PRD` | `PRD` owns the public surface; `to-prd` is an internal synthesis method |
-| `to-issues` vs `/30-Plan` | `/30-Plan` owns work breakdown; `to-issues` packages slices when issue tracker output is needed |
-| `implement` vs `/40-Implement` | `/40-Implement` owns implementation |
-| `review` vs `/50-Verify` | `/50-Verify` owns verification; `review` is one lane |
+| `to-issues` vs `30-plan` | `30-plan` owns work breakdown; `to-issues` packages slices when issue tracker output is needed |
+| `implement` vs `40-implement` | `40-implement` owns implementation |
+| `review` vs `50-verify` | `50-verify` owns verification; `review` is one lane |
 
 ## Examples
 
 | User Request | Route |
 |---|---|
-| "I have an idea but not the shape yet" | `/00-Discover`, likely `Brainstorm`, then return to Discover |
-| "Turn this stable new goal into requirements" | `/00-Discover`, then `/10-Define {discovery_id}` before `/20-Spec {running_id}` |
-| "Fix this newly reported broken auth flow" | `/00-Discover`, likely `Debug`, then return to Discover before Define |
-| "Review this implementation for risks" | `/50-Verify` or `Agent code-reviewer ...` |
+| "I have an idea but not the shape yet" | `00-discover`, likely `Brainstorm`, then return to Discover |
+| "Turn this stable new goal into requirements" | `00-discover`, then `10-define {discovery_id}` before `20-spec {running_id}` |
+| "Fix this newly reported broken auth flow" | `00-discover`, likely `Debug`, then return to Discover before Define |
+| "Review this implementation for risks" | `50-verify` or `Agent code-reviewer ...` |
 | "Install or upgrade Nexus-DevFlow on this machine" | `Check-For-Updates` |
 | "Help me figure out which command to use" | `Help` |
 

package/template/.claude/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."
 ---
 
 ---
@@ -84,8 +84,8 @@ Use:
 - `Debug` for confirmed bugs needing root cause work
 - `Research` or `Spec-Research` for external dependency uncertainty
 - `PRD` for product-level feature requests that need problem framing
-- `/10-Define` for actionable work that still needs scope decisions
-- `/20-Spec` for work that is already stable enough to become a delivery contract
+- `10-define` for actionable work that still needs scope decisions
+- `20-spec` for work that is already stable enough to become a delivery contract
 - `Help` when the issue is not actionable yet
 
 ## Output Triage Recommendation
@@ -103,13 +103,13 @@ Return:
 - Classification: Companion command
 - Mainline status: Intake support command, not a numbered stage
 - Typical entry points: issue intake before scope or implementation begins
-- Typical handoff targets: `Debug`, `PRD`, `/10-Define`, `Research`, `Help`
+- Typical handoff targets: `Debug`, `PRD`, `10-define`, `Research`, `Help`
 
 ## Sources
 
 - `AGENTS.md`
 - `.agent/resources/schemas/triage.template.md`
-- Related commands: `Debug`, `PRD`, `/10-Define`, `Research`, `Help`
+- Related commands: `Debug`, `PRD`, `10-define`, `Research`, `Help`
 - Support skills: `triage`, `to-issues`, `domain-modeling`
 
 

package/template/.claude/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/.claude/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/.claude/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/.claude/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)
 
@@ -59,18 +59,18 @@ You are an orchestrator. Your goal is to safely integrate code and clean up loca
 - Classification: Companion command
 - Mainline status: Release support command, not a numbered stage
 - Typical entry points: after `PR` and review gates are complete
-- Typical handoff targets: `/70-Release`, `Wiki`
+- Typical handoff targets: `70-release`, `Wiki`
 
 ## Sources
 
 - `AGENTS.md`
 - `.agents/skills/release-git-operations/SKILL.md`
 - `.agents/skills/git-workflow-and-versioning/SKILL.md`
-- Related commands: `PR`, `PR-Review`, `PR-Followup`, `/60-Report`, `/70-Release`
+- Related commands: `PR`, `PR-Review`, `PR-Followup`, `60-report`, `70-release`
 
 ## Next Workflow Recommendation
 
-- **Primary**: `/70-Release`
+- **Primary**: `70-release`
 - **Why**: after merge, the remaining work is usually release execution, deployment coordination, or final packaging against the already aligned report.
-- **Alternative**: `/60-Report` if merge outcomes changed the story enough that the final summary must be refreshed first.
+- **Alternative**: `60-report` if merge outcomes changed the story enough that the final summary must be refreshed first.
 

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

@@ -1,6 +1,6 @@
 ---
 name: onboard
-description: Set up Nexus-DevFlow after overlaying it onto a freshly scaffolded or early project. Detects the stack, tunes AGENTS.md commands and conventions, customizes coding-standards.md, checks .gitignore and tool adapters, initializes project-overview.md, and guides the user to /00-discover or /10-define. Use when the user runs onboard, /onboard, $onboard, just installed DevFlow into a new project, or asks what to do after installation. For an existing app with meaningful shipped features, use adopt instead.
+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
@@ -8,15 +8,15 @@ description: Set up Nexus-DevFlow after overlaying it onto a freshly scaffolded
 Where this sits in the workflow:
 
 ```text
-scaffold app  ->  overlay DevFlow  ->  [onboard]  ->  /00-discover or /10-define  ->  Mainline Loop
+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.
+`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.
+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.
+Use `adopt` instead when the app already has substantial shipped code, working routes, and existing business logic.
 
 ---
 
@@ -32,7 +32,7 @@ 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.
+- 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.
 
@@ -125,5 +125,5 @@ Present a concise onboarding summary report:
 - 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
+  - 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/.claude/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/.claude/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
 ---
 
@@ -24,7 +24,7 @@ Before parallelizing:
 2. identify the lifecycle owner
 3. split the work into independent questions
 
-If those conditions are missing, return first to `/00-Discover`, `/20-Spec`, or `/30-Plan`.
+If those conditions are missing, return first to `00-discover`, `20-spec`, or `30-plan`.
 
 ## Basic Invocation Patterns
 

package/template/.claude/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/.claude/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
@@ -24,7 +24,7 @@ Decompose work into small, verifiable tasks with explicit acceptance criteria. G
 - You need to communicate scope to a human
 - The implementation order isn't obvious
 
-In DevFlow 2.0, this skill primarily supports `/30-Plan`.
+In DevFlow 2.0, this skill primarily supports `30-plan`.
 
 **When NOT to use:** Single-file changes with obvious scope, or when the spec already contains well-defined tasks.
 

package/template/.claude/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/.claude/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)
 
@@ -16,7 +16,7 @@ Primary behavior now lives in:
 
 Treat this workflow file as a compatibility wrapper around that skill in `pr` mode.
 
-In DevFlow 2.0, this is a release-adjacent workflow. It usually follows `/60-Report` and pairs naturally with `/70-Release` once the final summary is aligned.
+In DevFlow 2.0, this is a release-adjacent workflow. It usually follows `60-report` and pairs naturally with `70-release` once the final summary is aligned.
 
 ---
 
@@ -31,7 +31,7 @@ You are an orchestrator. Your goal is to call the specialized Git PR Maker agent
 - Ensure the branch is not `main` or `master`.
 - Check for unpushed commits.
 - Verify the working directory is clean enough for PR submission.
-- Confirm the implementation has already passed the expected verification gate. If it has not, route back to `/50-Verify` first.
+- Confirm the implementation has already passed the expected verification gate. If it has not, route back to `50-verify` first.
 
 ### Phase 2: Context And Template
 
@@ -75,19 +75,19 @@ Verify that the workflow returns:
 
 - Classification: Companion command
 - Mainline status: Release support command, not a numbered stage
-- Typical entry points: `/70-Release`, `Commit`
-- Typical handoff targets: `PR-Review`, `PR-Followup`, `Merge`, `/70-Release`
+- Typical entry points: `70-release`, `Commit`
+- Typical handoff targets: `PR-Review`, `PR-Followup`, `Merge`, `70-release`
 
 ## Sources
 
 - `AGENTS.md`
 - `.agents/skills/release-git-operations/SKILL.md`
 - `.agents/skills/git-workflow-and-versioning/SKILL.md`
-- Related commands: `Commit`, `PR-Review`, `PR-Followup`, `Merge`, `/60-Report`, `/70-Release`
+- Related commands: `Commit`, `PR-Review`, `PR-Followup`, `Merge`, `60-report`, `70-release`
 
 ## Next Workflow Recommendation
 
-- **Primary**: `/70-Release`
+- **Primary**: `70-release`
 - **Why**: after PR creation, release execution and handoff details should stay consistent with the approved report.
-- **Alternative**: `PR-Review` for structured review before broader sharing, or `/60-Report` when the final communication summary still needs to be refreshed first.
+- **Alternative**: `PR-Review` for structured review before broader sharing, or `60-report` when the final communication summary still needs to be refreshed first.
 

package/template/.claude/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
@@ -9,7 +9,7 @@ description: PR Review Addon - Review a pull request using GitHub review prompt
 
 Use this workflow when you need a structured PR review without creating or changing the PR. It can review a local diff, a PR URL or number, or a task-linked branch.
 
-In DevFlow 2.0, this remains a supporting review workflow. It should feed corrective work back into `/40-Implement` or clear the path toward `/60-Report` and then `/70-Release`.
+In DevFlow 2.0, this remains a supporting review workflow. It should feed corrective work back into `40-implement` or clear the path toward `60-report` and then `70-release`.
 
 Primary behavior now lives in the `pr-review-analysis` skill. Keep this workflow as the compatibility wrapper and user-facing review prompt surface.
 
@@ -123,21 +123,21 @@ devflow/runs/{ID}-*/pr_review.md
 
 - Classification: Companion command
 - Mainline status: Verification and release support command, not a numbered stage
-- Typical entry points: `/50-Verify`, `PR`, `Agent code-reviewer`
-- Typical handoff targets: `PR-Followup`, `/60-Report`, `/70-Release`, `Wiki`
+- Typical entry points: `50-verify`, `PR`, `Agent code-reviewer`
+- Typical handoff targets: `PR-Followup`, `60-report`, `70-release`, `Wiki`
 
 ## Sources
 
 - `AGENTS.md`
 - `.agent/resources/schemas/pr_review.template.md`
-- Related commands: `/50-Verify`, `PR`, `PR-Followup`, `Agent`, `/60-Report`, `/70-Release`, `Wiki`
+- Related commands: `50-verify`, `PR`, `PR-Followup`, `Agent`, `60-report`, `70-release`, `Wiki`
 
 ## Next Workflow Recommendation
 
-- **Primary**: `/40-Implement {ID}` when review finds required fixes, or `/60-Report {ID}` when the review is clean and the run needs the final summary refreshed before release execution.
+- **Primary**: `40-implement {ID}` when review finds required fixes, or `60-report {ID}` when the review is clean and the run needs the final summary refreshed before release execution.
 - **Why**: PR review either creates corrective implementation work or clears the path toward final summary alignment and release-facing packaging.
 - **Alternatives**:
-  - `/70-Release` when the report is already aligned and only release execution remains
+  - `70-release` when the report is already aligned and only release execution remains
   - `Wiki` when the review establishes a durable convention or risk pattern
   - `PR-Followup {target}` when the PR already has comments that need classification and response
 

package/template/.claude/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
@@ -20,7 +20,7 @@ This skill should reuse and align with:
 
 ## When to Use
 
-- after `/50-Verify` when the change needs structured review before `/60-Report` and `/70-Release`
+- after `50-verify` when the change needs structured review before `60-report` and `70-release`
 - when a local diff, branch, or pull request needs findings-first analysis
 - when the user wants review without directly editing code
 
@@ -86,4 +86,4 @@ Return:
 - open questions or assumptions
 - residual risks or test gaps
 - where the review report was saved
-- the recommended next route such as `/40-Implement`, `/70-Release`, or `PR-Followup`
+- the recommended next route such as `40-implement`, `70-release`, or `PR-Followup`

package/template/.claude/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."
 ---
 
 ---
@@ -12,9 +12,9 @@ description: Strategic PRD Generator (Orchestration) - Transform a product or fe
 
 Transform a product or feature idea into a problem-first, hypothesis-driven Product Requirements Document (PRD).
 
-In DevFlow 2.0, this is a supporting workflow, not part of the numbered mainline state path. Use it when the idea is still too product-shaped for `/10-Define` or `/20-Spec` to proceed cleanly.
+In DevFlow 2.0, this is a supporting workflow, not part of the numbered mainline state path. Use it when the idea is still too product-shaped for `10-define` or `20-spec` to proceed cleanly.
 Use `to-prd` when existing conversation, discovery, or codebase context is already sufficient and the job is synthesis rather than another interview.
-When invoked from `/00-Discover`, link the PRD to the Discovery ID and return to `/00-Discover {discovery_id}` for the final `Proceed`, `Defer`, or `Reject` decision. PRD does not create Running IDs.
+When invoked from `00-discover`, link the PRD to the Discovery ID and return to `00-discover {discovery_id}` for the final `Proceed`, `Defer`, or `Reject` decision. PRD does not create Running IDs.
 
 ---
 
@@ -56,7 +56,7 @@ You are an orchestrator. Your goal is to call the specialized PRD Architect agen
   - explicit assumptions
   - open questions
   - risks that should remain visible before delivery planning
-- Do not let the PRD silently drift into implementation detail that belongs in `/20-Spec` or `/30-Plan`.
+- Do not let the PRD silently drift into implementation detail that belongs in `20-spec` or `30-plan`.
 
 ### Phase 4: Output Generation
 
@@ -84,10 +84,10 @@ devflow/prds/{date}-{slug}.prd.md
 
 Convert the PRD into explicit next steps for the Timeline flow:
 
-- `/00-Discover {discovery_id}` when the PRD belongs to an active discovery
-- `/10-Define` when product framing was created outside Discover and delivery has already been approved
-- `/20-Spec` when the delivery contract is ready to be locked
-- `/30-Plan {ID}` only after the spec is execution-ready
+- `00-discover {discovery_id}` when the PRD belongs to an active discovery
+- `10-define` when product framing was created outside Discover and delivery has already been approved
+- `20-spec` when the delivery contract is ready to be locked
+- `30-plan {ID}` only after the spec is execution-ready
 
 The user should still approve the transition into execution work. Do not treat PRD generation as automatic task creation.
 
@@ -110,18 +110,18 @@ Return:
 - Classification: Companion command
 - Mainline status: Not a numbered stage
 - Typical entry points: product framing before implementation-ready scope exists
-- Typical handoff targets: `/00-Discover {discovery_id}`, `/10-Define`, `/20-Spec`, `Roadmap`, `Spec-Orchestrate`
+- Typical handoff targets: `00-discover {discovery_id}`, `10-define`, `20-spec`, `Roadmap`, `Spec-Orchestrate`
 
 ## Sources
 
 - `AGENTS.md`
 - `.agent/resources/schemas/prd.template.md`
-- Related commands: `Brainstorm`, `Research`, `/10-Define`, `/20-Spec`, `Roadmap`, `Spec-Orchestrate`
+- Related commands: `Brainstorm`, `Research`, `10-define`, `20-spec`, `Roadmap`, `Spec-Orchestrate`
 - Support skills: `to-prd`, `grill-with-docs`, `domain-modeling`
 
 ## Next Workflow Recommendation
 
-- **Primary**: `/00-Discover {discovery_id}` when invoked from discovery; otherwise `/10-Define`
+- **Primary**: `00-discover {discovery_id}` when invoked from discovery; otherwise `10-define`
 - **Why**: PRD shapes product intent, while Discover owns the delivery decision and Define owns Running ID creation.
 - **Alternative**: `Research` when technical feasibility or external dependencies are still unresolved.