@jakkrichm/create-nexus-devflow 2.0.8 → 2.0.10

package/template/.claude/skills/debug/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: debug
-description: Debug workflow
+description: "[Devflow] Root cause investigation and diagnostic loop before or during implementation without editing code. Use when encountering broken behavior, test failures, or bugs."
 ---
 
 ---
@@ -27,11 +27,11 @@ Use it when:
 
 Preferred DevFlow 2.0 pairing:
 
-- from `/00-Discover` when a new request begins with a failure whose root cause is unknown
-- from `/40-Implement`
-- from `/50-Verify`
+- from `00-discover` when a new request begins with a failure whose root cause is unknown
+- from `40-implement`
+- from `50-verify`
 
-When invoked with a Discovery ID, link the RCA report to that discovery and return to `/00-Discover {discovery_id}` for the delivery decision. Do not allocate a Running ID for an unapproved fix during Debug.
+When invoked with a Discovery ID, link the RCA report to that discovery and return to `00-discover {discovery_id}` for the delivery decision. Do not allocate a Running ID for an unapproved fix during Debug.
 
 ## Source Discipline
 
@@ -114,18 +114,18 @@ Debug unexpected duplicate records
 
 - Classification: Companion command
 - Mainline status: Not a numbered stage
-- Typical entry points: `/00-Discover`, `/40-Implement`, `/50-Verify`, `Issue-Triage`, production failure analysis
-- Typical handoff targets: `/00-Discover {discovery_id}` for discovery-owned RCA, `/40-Implement`, `/50-Verify`, `Insight`, `Wiki`
+- Typical entry points: `00-discover`, `40-implement`, `50-verify`, `Issue-Triage`, production failure analysis
+- Typical handoff targets: `00-discover {discovery_id}` for discovery-owned RCA, `40-implement`, `50-verify`, `Insight`, `Wiki`
 
 ## Sources
 
 - `AGENTS.md`
 - `.agent/resources/schemas/rca.template.md`
-- Related commands: `/40-Implement`, `/50-Verify`, `Test`, `Insight`, `Wiki`, `Agent`
+- Related commands: `40-implement`, `50-verify`, `Test`, `Insight`, `Wiki`, `Agent`
 
 ## Next Workflow Recommendation
 
-- Default: return to `/00-Discover {discovery_id}` when the failure entered through discovery; otherwise return to `/40-Implement` when a tracked fix already exists
-- Alternate: `/30-Plan` if the fix needs planning changes
-- Alternate: `/50-Verify` when the issue is resolved and needs re-checking
+- Default: return to `00-discover {discovery_id}` when the failure entered through discovery; otherwise return to `40-implement` when a tracked fix already exists
+- Alternate: `30-plan` if the fix needs planning changes
+- Alternate: `50-verify` when the issue is resolved and needs re-checking
 

package/template/.claude/skills/debugging-and-error-recovery/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: debugging-and-error-recovery
-description: Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
+description: "[Devflow] Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing."
 ---
 
 # Debugging and Error Recovery

package/template/.claude/skills/deploy/SKILL.md

@@ -1,6 +1,6 @@
 ---name: deploy
 
-description: Production Deployment (Auto-Deploy) - Perform pre-flight checks, deployment execution, and verification for production releases.
+description: "[Devflow] Production deployment pre-flight checks, smoke validation, and deployment execution."
 ---
 # ๐Ÿš€ Phase 52: Production Deployment (Auto-Deploy)
 
@@ -76,8 +76,8 @@ Generate an Error summary detailing:
 
 - Classification: Companion command
 - Mainline status: Release support command, not a numbered stage
-- Typical entry points: `/70-Release` after the report is aligned and packaging is ready to execute
-- Typical handoff targets: `/60-Report`, `Changelog`, `Wiki`
+- Typical entry points: `70-release` after the report is aligned and packaging is ready to execute
+- Typical handoff targets: `60-report`, `Changelog`, `Wiki`
 
 ## Sources
 
@@ -86,6 +86,6 @@ Generate an Error summary detailing:
 - `.agents/skills/shipping-and-launch/SKILL.md`
 - `.agents/skills/deployment-procedures/SKILL.md`
 - `.agent/resources/schemas/deploy_report.template.md`
-- Related commands: `/70-Release`, `Commit`, `PR`, `Changelog`, `/60-Report`
+- Related commands: `70-release`, `Commit`, `PR`, `Changelog`, `60-report`
 
 

package/template/.claude/skills/deployment-procedures/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: deployment-procedures
-description: Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
+description: "[Devflow] Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts."
 allowed-tools: Read, Glob, Grep, Bash
 ---
 

package/template/.claude/skills/deprecation-and-migration/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: deprecation-and-migration
-description: Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
+description: "[Devflow] Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code."
 ---
 
 # Deprecation and Migration

package/template/.claude/skills/devflow/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: devflow
-description: Flagship interactive guide, intent router, workspace state inspector, and sitemap for Nexus-DevFlow workflows. Inspects current workspace state, maps natural language requests to matching stages/commands, and provides a cheat sheet of all available DevFlow skills. Use when the user runs devflow, /devflow, $devflow, status, asks how to use devflow, asks what command to run next, or needs guidance on DevFlow lifecycle paths.
+description: "[Devflow] Flagship interactive guide, state inspector, and intent router for DevFlow workflows."
 ---
 
 # devflow - Interactive Workflow Guide & Intent Router for Nexus-DevFlow
@@ -9,14 +9,14 @@ Use this skill to guide the user on what to do next, inspect current workspace s
 
 ## Input
 
-- **No argument (`devflow`, `/devflow`, `$devflow`, or `status`)**: Inspect current workspace state (active run in `devflow/runs/` or `devflow/context/current-stage.md`, active discovery in `devflow/discoveries/`, open findings in `devflow/context/findings.md`, and project overview in `devflow/context/project-overview.md`) and recommend the exact next action.
+- **No argument (`devflow`, `devflow`, `$devflow`, or `status`)**: Inspect current workspace state (active run in `devflow/runs/` or `devflow/context/current-stage.md`, active discovery in `devflow/discoveries/`, open findings in `devflow/context/findings.md`, and project overview in `devflow/context/project-overview.md`) and recommend the exact next action.
 - **With user request (`devflow "<request>"`)**: Classify the user's intent and guide them to the matching DevFlow 2.0 stage or companion command path.
 
 ## Workspace State Inspection
 
 When invoked without an argument (or when determining the next step), inspect:
 
-1. **Project Setup Baseline**: Read `devflow/context/project-overview.md` and `devflow/context/coding-standards.md`. If they are empty or default placeholders, recommend `/onboard` (for fresh projects) or `/adopt` (for existing codebases).
+1. **Project Setup Baseline**: Read `devflow/context/project-overview.md` and `devflow/context/coding-standards.md`. If they are empty or default placeholders, recommend `onboard` (for fresh projects) or `adopt` (for existing codebases).
 2. **Active Delivery Run**: Read `devflow/context/current-stage.md` and check `devflow/runs/{RUNNING_ID}/` for active artifacts (`10-define.md`, `20-spec.md`, `30-plan.md`, `40-implement.md`, `50-verify.md`, `60-report.md`, `70-release.md`).
 3. **Active Discovery**: Check `devflow/discoveries/` for open discovery notes.
 4. **Audit Findings Ledger**: Check `devflow/context/findings.md` for open high-severity findings.
@@ -24,15 +24,15 @@ When invoked without an argument (or when determining the next step), inspect:
 ### State-Based Recommendation Rules
 
 - If context is empty/unconfigured -> Recommend `onboard` (for fresh project) or `adopt` (for brownfield codebase).
-- If a run is at `10-define.md` -> Recommend `20-spec {RUNNING_ID}` (or `/20-spec`, `$20-spec`, `spec`).
-- If a run is at `20-spec.md` -> Recommend `30-plan {RUNNING_ID}` (or `/30-plan`, `$30-plan`, `plan`).
-- If a run is at `30-plan.md` -> Recommend `40-implement {RUNNING_ID}` (or `/40-implement`, `$40-implement`, `implement`).
+- If a run is at `10-define.md` -> Recommend `20-spec {RUNNING_ID}` (or `20-spec`, `$20-spec`, `spec`).
+- If a run is at `20-spec.md` -> Recommend `30-plan {RUNNING_ID}` (or `30-plan`, `$30-plan`, `plan`).
+- If a run is at `30-plan.md` -> Recommend `40-implement {RUNNING_ID}` (or `40-implement`, `$40-implement`, `implement`).
 - If a run is at `40-implement.md` with incomplete tasks -> Recommend `40-implement {RUNNING_ID}`.
-- If a run is at `40-implement.md` with all tasks done -> Recommend `50-verify {RUNNING_ID}` (or `/50-verify`, `$50-verify`, `verify`).
+- If a run is at `40-implement.md` with all tasks done -> Recommend `50-verify {RUNNING_ID}` (or `50-verify`, `$50-verify`, `verify`).
 - If a run passed `50-verify.md` -> Recommend `60-report {RUNNING_ID}` then `70-release {RUNNING_ID}`.
 - If no run is active and user wants to explore an idea -> Recommend `00-discover` (or `discover`, `Brainstorm`).
 - If no run is active and open P0/P1 findings exist -> Recommend `security-review` or `debug`.
-- If user asks to check system health or configuration -> Recommend `doctor` (or `/doctor`, `$doctor`).
+- If user asks to check system health or configuration -> Recommend `doctor` (or `doctor`, `$doctor`).
 
 ## Intent Classification & Skill Routing
 
@@ -51,6 +51,11 @@ When the user specifies a request, map it to the matching DevFlow 2.0 stage or c
 | "Verify code quality & QA review" | `50-verify` | `verify` | `50-verify` -> `60-report` -> `70-release` |
 | "Generate summary HTML/MD report" | `60-report` | `report` | `60-report` -> `70-release` |
 | "Package for PR merge or deployment" | `70-release` | `release` | `70-release` |
+| "Human manual QA walkthrough guide" | `try` | `try` | `try` (after implement or verify) |
+| "Safely plan feature or run reversal" | `rollback` | `rollback` | `rollback` -> `40-implement` |
+| "Set up automatic GitHub Actions CI" | `ci` | `ci` | `ci` (after onboard or adopt) |
+| "Pre-check scope & risks before spec" | `brief` | `brief` | `brief` -> `20-spec` |
+| "Run autonomous bounded delivery loop"| `autopilot` | `autopilot` | `autopilot` -> `70-release` |
 | "High-level goal or long-running task" | `goal` | `goal` | `goal` -> `00-discover` |
 | "Brainstorm ideas without allocating ID" | `brainstorm` | `brainstorm` | `brainstorm` -> `00-discover` |
 | "Deep codebase or web research" | `research` | `research` | `research` |
@@ -66,20 +71,25 @@ When the user specifies a request, map it to the matching DevFlow 2.0 stage or c
 Always provide a clean summary of available Nexus-DevFlow skills grouped by lifecycle stage:
 
 ### 1. Mainline Lifecycle Stages (Linear Order)
-- `00-discover` (`discover`, `/00-discover`, `$00-discover`) - Explore request, route inquiries, go/no-go under Discovery ID
-- `10-define` (`define`, `/10-define`, `$10-define`) - Lock delivery boundaries and allocate Running ID (`devflow/runs/{ID}`)
-- `20-spec` (`spec`, `/20-spec`, `$20-spec`) - Formalize markdown-first specifications and acceptance criteria
-- `30-plan` (`plan`, `/30-plan`, `$30-plan`) - Transform spec into executable task breakdown with test decisions
-- `40-implement` (`implement`, `/40-implement`, `$40-implement`) - Execute planned tasks incrementally with evidence
-- `50-verify` (`verify`, `/50-verify`, `$50-verify`) - Senior QA review, validation checks, and pass/fail gate
-- `60-report` (`report`, `/60-report`, `$60-report`) - Generate standardized markdown and HTML summary report
-- `70-release` (`release`, `/70-release`, `$70-release`) - Package verified work for PR merge or deployment
+- `00-discover` (`discover`, `00-discover`, `$00-discover`) - Explore request, route inquiries, go/no-go under Discovery ID
+- `10-define` (`define`, `10-define`, `$10-define`) - Lock delivery boundaries and allocate Running ID (`devflow/runs/{ID}`)
+- `20-spec` (`spec`, `20-spec`, `$20-spec`) - Formalize markdown-first specifications and acceptance criteria
+- `30-plan` (`plan`, `30-plan`, `$30-plan`) - Transform spec into executable task breakdown with test decisions
+- `40-implement` (`implement`, `40-implement`, `$40-implement`) - Execute planned tasks incrementally with evidence
+- `50-verify` (`verify`, `50-verify`, `$50-verify`) - Senior QA review, validation checks, and pass/fail gate
+- `60-report` (`report`, `60-report`, `$60-report`) - Generate standardized markdown and HTML summary report
+- `70-release` (`release`, `70-release`, `$70-release`) - Package verified work for PR merge or deployment
 
 ### 2. Public Companion Commands
-- `devflow` (`status`, `/devflow`, `$devflow`) - Guide, state inspector, and intent router
-- `onboard` (`/onboard`, `$onboard`) - Baseline stack setup for freshly scaffolded projects
-- `adopt` (`/adopt`, `$adopt`) - Survey and bootstrap DevFlow into existing brownfield projects
-- `doctor` (`/doctor`, `$doctor`) - Read-only health check for setup, scripts, and workflow drift
+- `devflow` (`status`, `devflow`, `$devflow`) - Guide, state inspector, and intent router
+- `onboard` (`onboard`, `$onboard`) - Baseline stack setup for freshly scaffolded projects
+- `adopt` (`adopt`, `$adopt`) - Survey and bootstrap DevFlow into existing brownfield projects
+- `doctor` (`doctor`, `$doctor`) - Read-only health check for setup, scripts, and workflow drift
+- `try` (`try`, `$try`) - Step-by-step human manual QA review guide (where to go, what to click, what to expect)
+- `rollback` (`rollback`, `$rollback`) - Safe feature/run reversal planner with dependency risk analysis
+- `ci` (`ci`, `$ci`) - Automatic GitHub Actions workflow (`.github/workflows/verify.yml`) setup
+- `brief` (`brief`, `$brief`) - Read-only scope, dependency, and size pre-briefing before speccing
+- `autopilot` (`autopilot`, `$autopilot`) - Optional bounded autonomous loop (spec -> plan -> implement -> verify -> report)
 - `goal` - Route broad goals before Discovery
 - `brainstorm` - Ideate without allocating running IDs
 - `research` - Conduct codebase or web research

package/template/.claude/skills/diagnosing-bugs/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: diagnosing-bugs
-description: Diagnosis loop for hard bugs and performance regressions. Use inside Debug, /40-Implement, or /50-Verify when behavior is broken, throwing, failing, flaky, or slow.
+description: "[Devflow] Diagnosis loop for hard bugs and performance regressions. Use inside Debug, 40-implement, or 50-verify when behavior is broken, throwing, failing, flaky, or slow."
 ---
 
 # Diagnosing Bugs
 
 Use this support skill when the active DevFlow owner needs a disciplined root-cause loop.
 
-Do not let this skill replace `Debug`, `/40-Implement`, or `/50-Verify`. It supplies the method; the owning workflow records the artifact.
+Do not let this skill replace `Debug`, `40-implement`, or `50-verify`. It supplies the method; the owning workflow records the artifact.
 
 ## Phase 1: Build A Tight Feedback Loop
 
@@ -79,7 +79,7 @@ When a correct test seam exists:
 4. Watch it pass.
 5. Re-run the original feedback loop.
 
-If no correct seam exists, record that architecture finding and route to `codebase-design` or `/30-Plan` after the bug is fixed.
+If no correct seam exists, record that architecture finding and route to `codebase-design` or `30-plan` after the bug is fixed.
 
 ## Phase 6: Cleanup And Post-Mortem
 

package/template/.claude/skills/doctor/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: doctor
-description: Read-only DevFlow health check and diagnostics. Inspects DevFlow setup, tool adapters, context files integrity, AGENTS.md commands validity, active runs in devflow/runs/, checklist completeness, and detects workflow drift. Use when the user runs doctor, /doctor, $doctor, asks to diagnose DevFlow, or wants to check project workflow health.
+description: "[Devflow] Read-only DevFlow health check and diagnostics for context files, adapters, commands, and workflow drift."
 ---
 
 # doctor - Read-Only DevFlow Health Check & Diagnostics
@@ -12,7 +12,7 @@ Any time during development -> [doctor] -> Health Report & Actionable Fixes
 (read-only inspection)          (diagnostics)    (remediation recommendations)
 ```
 
-`/doctor` is a safe, read-only diagnostic skill that verifies whether your repository's Nexus-DevFlow configuration, context files, tool adapters, commands, and active runs are healthy and aligned.
+`doctor` is a safe, read-only diagnostic skill that verifies whether your repository's Nexus-DevFlow configuration, context files, tool adapters, commands, and active runs are healthy and aligned.
 
 ---
 
@@ -29,7 +29,7 @@ Run through these 5 health checks:
 ### Check 1: Core Framework & Context Files Integrity
 - Check if [AGENTS.md](AGENTS.md) and [CLAUDE.md](CLAUDE.md) exist and are populated.
 - Check required context files under `devflow/context/`:
-  - `project-overview.md` (Check if still empty/placeholder -> recommend `/onboard` or `/adopt`)
+  - `project-overview.md` (Check if still empty/placeholder -> recommend `onboard` or `adopt`)
   - `coding-standards.md` (Check if customized for stack)
   - `ai-interaction.md` (Check if rules are configured)
   - `current-stage.md` (Check if active run matches filesystem)
@@ -80,5 +80,5 @@ Present a clean, scannable diagnostic report:
 
 ### Recommended Remediation Actions:
 1. [Action item if any warning or failure detected]
-2. [Suggested next command, e.g. /devflow, /onboard, /adopt, etc.]
+2. [Suggested next command, e.g. devflow, onboard, adopt, etc.]
 ```

package/template/.claude/skills/documentation-and-adrs/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: documentation-and-adrs
-description: Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
+description: "[Devflow] Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase."
 ---
 
 # Documentation and ADRs

package/template/.claude/skills/domain-modeling/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: domain-modeling
-description: Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
+description: "[Devflow] Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model."
 ---
 
 # Domain Modeling

package/template/.claude/skills/followup/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: followup
-description: Followup workflow
+description: "[Devflow] Followup task tracking, post-verification iteration, and routing unresolved items to subsequent runs."
 ---
 
 ---
@@ -33,11 +33,11 @@ Preserve existing phases, subtasks, statuses, logs, QA results, and completed co
 
 Read:
 
-- `devflow/runs/{ID}-*/10-define.md`
-- `devflow/runs/{ID}-*/20-spec.md`
-- `devflow/runs/{ID}-*/30-plan.md`
-- `devflow/runs/{ID}-*/40-implement.md`
-- `devflow/runs/{ID}-*/50-verify.md` if present
+- `devflow/runs/{ID}-*10-define.md`
+- `devflow/runs/{ID}-*20-spec.md`
+- `devflow/runs/{ID}-*30-plan.md`
+- `devflow/runs/{ID}-*40-implement.md`
+- `devflow/runs/{ID}-*50-verify.md` if present
 
 ### 2. Classify The Follow-Up
 
@@ -57,7 +57,7 @@ Append the follow-up scope directly to the relevant stage markdown files for the
 
 ### 4. Ask For Confirmation
 
-After adding or proposing follow-up subtasks, ask the user to confirm before `/40-Implement`.
+After adding or proposing follow-up subtasks, ask the user to confirm before `40-implement`.
 
 ## Output
 
@@ -66,18 +66,18 @@ Return:
 - follow-up category
 - new phase/subtask plan
 - validation result
-- next command: `/40-Implement {ID}`
+- next command: `40-implement {ID}`
 
 ## Relationship To DevFlow 2.0
 
 - Classification: Companion command
 - Mainline status: Not a numbered stage
 - Typical entry points: after review, triage, or release follow-up work is identified
-- Typical handoff targets: `/10-Define`, `/20-Spec`, `/30-Plan`, `/40-Implement`
+- Typical handoff targets: `10-define`, `20-spec`, `30-plan`, `40-implement`
 
 ## Sources
 
 - `AGENTS.md`
-- Related commands: `PR-Followup`, `Issue-Triage`, `Human-Feedback`, `/10-Define`, `/20-Spec`, `/40-Implement`
+- Related commands: `PR-Followup`, `Issue-Triage`, `Human-Feedback`, `10-define`, `20-spec`, `40-implement`
 
 

package/template/.claude/skills/frontend-ui-engineering/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: frontend-ui-engineering
-description: Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
+description: "[Devflow] Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated."
 ---
 
 # Frontend UI Engineering

package/template/.claude/skills/git-workflow-and-versioning/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: git-workflow-and-versioning
-description: Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.
+description: "[Devflow] Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams."
 ---
 
 # Git Workflow and Versioning

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