@jakkrichm/create-nexus-devflow 2.0.8 → 2.0.10

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

@@ -1,6 +1,6 @@
 ---
 name: goal
-description: Goal workflow
+description: "[Devflow] High-level goal routing and open-ended request intake before entering the 00-discover stage."
 ---
 
 ---
@@ -48,11 +48,11 @@ The Boss first classifies the request into one of these paths:
 
 | Flow | Use When | Typical Next Step |
 | :--- | :--- | :--- |
-| DevFlow Mainline | New feature, bug, test, docs, migration, or refactor requests. | `/00-Discover`, which owns the delivery decision |
-| PRD / Spec Orchestration | Product ideas or requirement-heavy planning before a Discovery ID exists. | `/00-Discover`, likely routing to `PRD` |
-| Brainstorm Flow | Early ambiguous ideas that need options and tradeoff analysis. | `/00-Discover`, likely routing to `Brainstorm` |
-| Research Flow | External facts, docs, codebase evidence, or feasibility proof are needed. | `/00-Discover`, likely routing to `Research` |
-| RCA / Debug Flow | Failures, errors, regressions, or investigation-heavy bug reports. | `/00-Discover`, likely routing to `Debug` |
+| DevFlow Mainline | New feature, bug, test, docs, migration, or refactor requests. | `00-discover`, which owns the delivery decision |
+| PRD / Spec Orchestration | Product ideas or requirement-heavy planning before a Discovery ID exists. | `00-discover`, likely routing to `PRD` |
+| Brainstorm Flow | Early ambiguous ideas that need options and tradeoff analysis. | `00-discover`, likely routing to `Brainstorm` |
+| Research Flow | External facts, docs, codebase evidence, or feasibility proof are needed. | `00-discover`, likely routing to `Research` |
+| RCA / Debug Flow | Failures, errors, regressions, or investigation-heavy bug reports. | `00-discover`, likely routing to `Debug` |
 
 ## Process
 
@@ -124,22 +124,22 @@ Report:
 - Classification: Companion command
 - Mainline status: Not a numbered stage
 - Typical entry points: broad goals before a Discovery ID exists
-- Typical handoff target: `/00-Discover`, with a likely companion route recorded as guidance rather than executed outside Discover
+- Typical handoff target: `00-discover`, with a likely companion route recorded as guidance rather than executed outside Discover
 
 ## Sources
 
 - `AGENTS.md`
 - `.agent/scripts/goal-runner.mjs`
-- Related commands: `/00-Discover`, `Brainstorm`, `Research`, `PRD`, `Spec-Orchestrate`, `Debug`
+- Related commands: `00-discover`, `Brainstorm`, `Research`, `PRD`, `Spec-Orchestrate`, `Debug`
 
 ## Next Workflow Recommendation
 
 - **Primary**: the first command listed in `recommended_commands`
 - **Why**: `Goal` exists to route broad intent into the correct DevFlow 2.0 entry point
 - **Alternatives**:
-  - `/00-Discover "{goal}"` for all new work; Discover chooses Brainstorm, PRD, Research, Debug, or direct decision
-  - `/10-Define {discovery_id}` only after an approved Proceed decision
-  - `/20-Spec {running_id}` only for an existing approved delivery run
+  - `00-discover "{goal}"` for all new work; Discover chooses Brainstorm, PRD, Research, Debug, or direct decision
+  - `10-define {discovery_id}` only after an approved Proceed decision
+  - `20-spec {running_id}` only for an existing approved delivery run
 
 ## Wiki Update Recommendation
 

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

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

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

@@ -1,6 +1,6 @@
 ---name: help
 
-description: DevFlow 2.0 Help and routing guide. Transitional file while Help moves from numbered workflow to companion command.
+description: "[Devflow] DevFlow 2.0 help, routing guide, workflow sitemap, and process navigation."
 argument-hint: [optional: question, running id, stage, or issue]
 ---
 
@@ -77,14 +77,14 @@ Help Summary:
 Environment: All OK
 
 Active Runs:
-- 010-auth-refactor: stage=40-implement | approval=Pending | next=/50-Verify 010 | warnings: manual review open
-- 011-billing-phase-1: stage=20-spec | approval=Approved | next=/30-Plan 011
-- 012-admin-console: stage=50-verify | approval=Approved | next=/60-Report 012 | warnings: not ready for release
+- 010-auth-refactor: stage=40-implement | approval=Pending | next=50-verify 010 | warnings: manual review open
+- 011-billing-phase-1: stage=20-spec | approval=Approved | next=30-plan 011
+- 012-admin-console: stage=50-verify | approval=Approved | next=60-report 012 | warnings: not ready for release
 
 Recommended Next Action:
-- 010 -> /50-Verify 010
-- 011 -> /20-Spec 011
-- 012 -> /40-Implement 012
+- 010 -> 50-verify 010
+- 011 -> 20-spec 011
+- 012 -> 40-implement 012
 ```
 
 ### Phase C: Manual Review Soft Gate
@@ -108,13 +108,13 @@ Typical warning shape:
 ```text
 Manual Review Warning:
 - 014 -> 20-spec.md still shows Approval Status: Pending
-- Recommended action: review 20-spec.md and confirm the next allowed command before moving to /30-Plan 014
+- Recommended action: review 20-spec.md and confirm the next allowed command before moving to 30-plan 014
 ```
 
 ## DevFlow 2.0 Mainline
 
 ```text
-/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
@@ -163,38 +163,38 @@ These files still exist because their prompt bodies contain useful behavior, but
 
 ### 1. If the user is just starting
 
-Recommend `/00-Discover`. Discover selects `Brainstorm`, `PRD`, `Research`, `Debug`, or direct decision and owns the return synthesis.
+Recommend `00-discover`. Discover selects `Brainstorm`, `PRD`, `Research`, `Debug`, or direct decision and owns the return synthesis.
 If the request is large, high-risk, multi-phase, or requirement-heavy, explain that the run should use the manual review flow with explicit human approval at each stage.
 
 ### 2. If an approved discovery needs delivery boundaries
 
-Recommend `/10-Define {discovery_id}` so Define can create one or more Running IDs.
+Recommend `10-define {discovery_id}` so Define can create one or more Running IDs.
 
-If the go/no-go decision is not approved, return to `/00-Discover {discovery_id}` instead.
+If the go/no-go decision is not approved, return to `00-discover {discovery_id}` instead.
 
 ### 3. If the task is already defined and needs requirements
 
-Recommend `/20-Spec`.
+Recommend `20-spec`.
 
 ### 4. If requirements already exist and implementation planning is next
 
-Recommend `/30-Plan`.
+Recommend `30-plan`.
 
 ### 5. If planning is done and work should begin
 
-Recommend `/40-Implement`.
+Recommend `40-implement`.
 
 ### 6. If implementation exists and needs checking
 
-Recommend `/50-Verify`.
+Recommend `50-verify`.
 
 ### 7. If work is done and needs a final human-friendly summary before release
 
-Recommend `/60-Report`.
+Recommend `60-report`.
 
 ### 8. If the work needs packaging or release handling after the report is aligned
 
-Recommend `/70-Release`.
+Recommend `70-release`.
 
 ## General Q And A Role
 

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

@@ -1,6 +1,6 @@
 ---
 name: human-review-decisions
-description: Handle human approval, feedback, rejection, and recheck decisions around verified work. Use when a task needs a human gate after verification and the result must route cleanly back into the DevFlow 2.0 lifecycle.
+description: "[Devflow] Handle human approval, feedback, rejection, and recheck decisions around verified work. Use when a task needs a human gate after verification and the result must route cleanly back into the DevFlow 2.0 lifecycle."
 ---
 
 # Human Review Decisions
@@ -18,7 +18,7 @@ This skill handles the human review loop after implementation and verification.
 
 ## When to Use
 
-- After `/50-Verify` when a human must decide whether the work is acceptable
+- After `50-verify` when a human must decide whether the work is acceptable
 - When verified work needs non-blocking feedback
 - When review fails and the task must be sent back with explicit action items
 - When a read-only re-evaluation is needed before the human chooses a decision
@@ -42,23 +42,23 @@ Read only what is necessary to understand the review question and evidence.
 
 - confirm the task is genuinely review-ready
 - record approval in the current review-facing artifact
-- route to `/60-Report` first, then `/70-Release` when release execution is the remaining step
+- route to `60-report` first, then `70-release` when release execution is the remaining step
 
 #### Feedback
 
 - record requested improvements without treating them as hard rejection
 - preserve the feedback round and source
-- route to `/40-Implement` or `/30-Plan` if the feedback changes scope
+- route to `40-implement` or `30-plan` if the feedback changes scope
 
 #### Reject
 
 - record rejection reason and concrete action items
-- route to `/40-Implement`, `/30-Plan`, or `Debug` depending on the issue
+- route to `40-implement`, `30-plan`, or `Debug` depending on the issue
 
 #### Recheck
 
 - keep the action read-only unless the user explicitly asks to record it
-- evaluate the evidence and recommend `approve`, `feedback`, `reject`, or `/50-Verify`
+- evaluate the evidence and recommend `approve`, `feedback`, `reject`, or `50-verify`
 
 ### 3. Record Reusable Lessons
 

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

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

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

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

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
@@ -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/.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
@@ -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/.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
 ---
 
@@ -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/.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."
 ---
 
 ---
@@ -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/.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)
 
@@ -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/.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

@@ -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/.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
 ---
 
@@ -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/.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
@@ -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.