@jakkrichm/create-nexus-devflow 2.0.0 → 2.0.2

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

@@ -1,63 +1,63 @@
 ---name: commit
-
-description: Smart Commit (Git Orchestration) - Stage files intelligently and write a concise, imperative commit message according to project standards.
----
-# ๐Ÿ’พ Smart Commit (Git Orchestration)
-
-## Target: $ARGUMENTS
-
-Stage files intelligently and write a concise, imperative commit message according to project standards.
-
-Primary behavior now lives in:
-
-```text
-.agents/skills/release-git-operations/SKILL.md
-```
-
-Treat this workflow file as a compatibility wrapper around that skill in `commit` mode.
-
----
-
-## ๐Ÿ› ๏ธ Internal Process
-
-You are an orchestrator. Your goal is to call the specialized Git Committer agent to perform a high-quality commit.
-
-### Phase 1: Assessment & Staging
-**Call Agent**: `prp-core-git-committer`
-- Provide the target description (e.g., "all", "backend only", "staged").
-- The agent will:
-  - Check the current Git status and branch.
-  - **MANDATORY BRANCH RULE:** Use the user's current branch as-is. Do not create, switch, or checkout a branch automatically. Only create or switch branches when the user explicitly asks for that exact branch action in the current request.
-  - If the current branch appears risky for the intended commit (for example `main`/`master` or a protected branch), warn the user and ask whether they want to continue on the current branch or explicitly create/switch to another branch.
-  - Interpret your description to stage the correct files.
-  - Review the staged changes to understand the context.
-
-### Phase 2: Message Generation & Commit
-- Ensure the agent generates an imperative commit message (e.g., `feat: Add user auth`).
-- The agent will execute the commit and capture the result.
-
-### Phase 3: Result Summary
-- Verify the agent reports:
-  - Commit Hash.
-  - Final Commit Message.
-  - Statistics (Files changed, additions, deletions).
-
----
-
-๐Ÿ“Œ **Next Step**: Run `PR` to create a Pull Request.
-
-## Relationship To DevFlow 2.0
-
-- Classification: Companion command
-- Mainline status: Release support command, not a numbered stage
-- Typical entry points: `/70-Release` after the report is aligned and release execution is ready
-- Typical handoff targets: `PR`, `Deploy`, `/70-Release`
-
-## Sources
-
-- `AGENTS.md`
-- `.agents/skills/release-git-operations/SKILL.md`
-- `.agents/skills/git-workflow-and-versioning/SKILL.md`
-- Related commands: `/70-Release`, `PR`, `Deploy`, `Merge`
-
-
+
+description: Smart Commit (Git Orchestration) - Stage files intelligently and write a concise, imperative commit message according to project standards.
+---
+# ๐Ÿ’พ Smart Commit (Git Orchestration)
+
+## Target: $ARGUMENTS
+
+Stage files intelligently and write a concise, imperative commit message according to project standards.
+
+Primary behavior now lives in:
+
+```text
+.agents/skills/release-git-operations/SKILL.md
+```
+
+Treat this workflow file as a compatibility wrapper around that skill in `commit` mode.
+
+---
+
+## ๐Ÿ› ๏ธ Internal Process
+
+You are an orchestrator. Your goal is to call the specialized Git Committer agent to perform a high-quality commit.
+
+### Phase 1: Assessment & Staging
+**Call Agent**: `prp-core-git-committer`
+- Provide the target description (e.g., "all", "backend only", "staged").
+- The agent will:
+  - Check the current Git status and branch.
+  - **MANDATORY BRANCH RULE:** Use the user's current branch as-is. Do not create, switch, or checkout a branch automatically. Only create or switch branches when the user explicitly asks for that exact branch action in the current request.
+  - If the current branch appears risky for the intended commit (for example `main`/`master` or a protected branch), warn the user and ask whether they want to continue on the current branch or explicitly create/switch to another branch.
+  - Interpret your description to stage the correct files.
+  - Review the staged changes to understand the context.
+
+### Phase 2: Message Generation & Commit
+- Ensure the agent generates an imperative commit message (e.g., `feat: Add user auth`).
+- The agent will execute the commit and capture the result.
+
+### Phase 3: Result Summary
+- Verify the agent reports:
+  - Commit Hash.
+  - Final Commit Message.
+  - Statistics (Files changed, additions, deletions).
+
+---
+
+๐Ÿ“Œ **Next Step**: Run `PR` to create a Pull Request.
+
+## Relationship To DevFlow 2.0
+
+- Classification: Companion command
+- Mainline status: Release support command, not a numbered stage
+- Typical entry points: `/70-Release` after the report is aligned and release execution is ready
+- Typical handoff targets: `PR`, `Deploy`, `/70-Release`
+
+## Sources
+
+- `AGENTS.md`
+- `.agents/skills/release-git-operations/SKILL.md`
+- `.agents/skills/git-workflow-and-versioning/SKILL.md`
+- Related commands: `/70-Release`, `PR`, `Deploy`, `Merge`
+
+

package/template/.agents/skills/competitor-analysis/SKILL.md

@@ -1,66 +1,66 @@
----
-name: competitor-analysis
-description: Research competitors, market alternatives, user pain points, and differentiation opportunities. Use when product framing, roadmap decisions, or strategic positioning need source-backed external context.
----
-
-# Competitor Analysis
-
-## Overview
-
-This skill gathers market context and converts it into usable product insight for PRD, Define, Spec, or Roadmap work.
-
-## When to Use
-
-- The team needs to understand competitors or substitutes
-- Product framing needs real external context
-- Roadmap decisions need evidence about gaps or opportunities
-- A feature idea needs differentiation, not just implementation detail
-
-## Process
-
-### 1. Load Product Context
-
-- read the user request, PRD, Define, Spec, or Roadmap context
-- identify target users, use case, and known alternatives
-
-### 2. Gather Evidence
-
-- find direct and indirect competitors
-- inspect public docs, reviews, forums, comparisons, issue trackers, and discussion surfaces when available
-- cite sources and separate evidence from inference
-
-### 3. Analyze Opportunities
-
-For each competitor or market segment, summarize:
-
-- positioning
-- strengths
-- recurring pain points
-- opportunity for the current project
-
-### 4. Produce Reusable Output
-
-If the result is reusable, write it under:
-
-```text
-devflow/research/{date}-{slug}-competitor-analysis.md
-```
-
-Use `.agent/resources/schemas/competitor_analysis.template.md` when saving a reusable report.
-
-### 5. Route Back
-
-- `PRD` for product framing
-- `/10-Define` for scope and decision shaping
-- `Roadmap` for prioritization
-- `/20-Spec` when a selected opportunity becomes actionable
-
-## Output
-
-Return:
-
-- competitors researched
-- market gaps
-- evidence-backed opportunities
-- source links
-- recommended return stage or command
+---
+name: competitor-analysis
+description: Research competitors, market alternatives, user pain points, and differentiation opportunities. Use when product framing, roadmap decisions, or strategic positioning need source-backed external context.
+---
+
+# Competitor Analysis
+
+## Overview
+
+This skill gathers market context and converts it into usable product insight for PRD, Define, Spec, or Roadmap work.
+
+## When to Use
+
+- The team needs to understand competitors or substitutes
+- Product framing needs real external context
+- Roadmap decisions need evidence about gaps or opportunities
+- A feature idea needs differentiation, not just implementation detail
+
+## Process
+
+### 1. Load Product Context
+
+- read the user request, PRD, Define, Spec, or Roadmap context
+- identify target users, use case, and known alternatives
+
+### 2. Gather Evidence
+
+- find direct and indirect competitors
+- inspect public docs, reviews, forums, comparisons, issue trackers, and discussion surfaces when available
+- cite sources and separate evidence from inference
+
+### 3. Analyze Opportunities
+
+For each competitor or market segment, summarize:
+
+- positioning
+- strengths
+- recurring pain points
+- opportunity for the current project
+
+### 4. Produce Reusable Output
+
+If the result is reusable, write it under:
+
+```text
+devflow/research/{date}-{slug}-competitor-analysis.md
+```
+
+Use `.agent/resources/schemas/competitor_analysis.template.md` when saving a reusable report.
+
+### 5. Route Back
+
+- `PRD` for product framing
+- `/10-Define` for scope and decision shaping
+- `Roadmap` for prioritization
+- `/20-Spec` when a selected opportunity becomes actionable
+
+## Output
+
+Return:
+
+- competitors researched
+- market gaps
+- evidence-backed opportunities
+- source links
+- recommended return stage or command