@jakkrichm/create-nexus-devflow 2.0.0 → 2.0.2

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

@@ -1,98 +1,98 @@
----
-name: review-followup-routing
-description: Classify review comments, extend existing work safely, and route corrective or future work back into the right DevFlow 2.0 stage. Use for PR follow-up and post-review follow-up planning.
----
-
-# Review Follow-up Routing
-
-## Overview
-
-This skill groups follow-up handling that used to be split across:
-
-- `PR-Followup`
-- `Followup`
-
-It keeps follow-up work attached to the right running ID without replacing the numbered mainline.
-
-## Related Foundation Assets
-
-This skill should reuse and align with:
-
-- `.agent/resources/schemas/pr_followup.template.md`
-- active stage markdown artifacts under `devflow/runs/{ID}-*/`
-
-## Supported Modes
-
-- `pr-followup`
-- `task-followup`
-
-## When to Use
-
-- after `PR-Review` when review comments need classification and response
-- after human feedback, QA, or release review when a task needs additional scoped work
-- when existing work should be extended instead of replaced
-
-## Process
-
-### 1. Load Current Context
-
-Read only the minimum needed:
-
-- existing running ID workspace artifacts
-- latest review comments, requested changes, or QA findings
-- current implementation or verification notes when relevant
-
-### 2. Classify The Follow-up
-
-Classify each item into a useful bucket such as:
-
-- fix now
-- already resolved
-- needs clarification
-- new scope follow-up
-- pre-existing issue
-- non-actionable
-
-For task follow-up, also classify the change shape:
-
-- extension
-- enhancement
-- integration
-- refinement
-- bug fix after review
-
-### 3. Preserve Existing History
-
-Extend existing markdown artifacts instead of replacing them:
-
-- keep current phases and completed work intact
-- append new phases, subtasks, notes, or decision logs
-- keep the same running ID unless the new scope truly deserves a separate work line
-
-### 4. Save Reusable Output
-
-For PR-centered follow-up, save a report under:
-
-```text
-devflow/reports/{date}-pr-followup-{ID}.md
-```
-
-Use `.agent/resources/schemas/pr_followup.template.md` when a formal report is required.
-
-For task follow-up, append the approved follow-up work directly into the relevant stage markdown files for the same running ID.
-
-### 5. Route Back
-
-- `/40-Implement` for immediate corrective work
-- `/50-Verify` when only verification needs another pass
-- `/10-Define` or `/20-Spec` when the follow-up becomes genuinely new scope
-
-## Output
-
-Return:
-
-- mode used
-- classification summary
-- what changes now versus later
-- where the follow-up was recorded
-- exact recommended next command
+---
+name: review-followup-routing
+description: Classify review comments, extend existing work safely, and route corrective or future work back into the right DevFlow 2.0 stage. Use for PR follow-up and post-review follow-up planning.
+---
+
+# Review Follow-up Routing
+
+## Overview
+
+This skill groups follow-up handling that used to be split across:
+
+- `PR-Followup`
+- `Followup`
+
+It keeps follow-up work attached to the right running ID without replacing the numbered mainline.
+
+## Related Foundation Assets
+
+This skill should reuse and align with:
+
+- `.agent/resources/schemas/pr_followup.template.md`
+- active stage markdown artifacts under `devflow/runs/{ID}-*/`
+
+## Supported Modes
+
+- `pr-followup`
+- `task-followup`
+
+## When to Use
+
+- after `PR-Review` when review comments need classification and response
+- after human feedback, QA, or release review when a task needs additional scoped work
+- when existing work should be extended instead of replaced
+
+## Process
+
+### 1. Load Current Context
+
+Read only the minimum needed:
+
+- existing running ID workspace artifacts
+- latest review comments, requested changes, or QA findings
+- current implementation or verification notes when relevant
+
+### 2. Classify The Follow-up
+
+Classify each item into a useful bucket such as:
+
+- fix now
+- already resolved
+- needs clarification
+- new scope follow-up
+- pre-existing issue
+- non-actionable
+
+For task follow-up, also classify the change shape:
+
+- extension
+- enhancement
+- integration
+- refinement
+- bug fix after review
+
+### 3. Preserve Existing History
+
+Extend existing markdown artifacts instead of replacing them:
+
+- keep current phases and completed work intact
+- append new phases, subtasks, notes, or decision logs
+- keep the same running ID unless the new scope truly deserves a separate work line
+
+### 4. Save Reusable Output
+
+For PR-centered follow-up, save a report under:
+
+```text
+devflow/reports/{date}-pr-followup-{ID}.md
+```
+
+Use `.agent/resources/schemas/pr_followup.template.md` when a formal report is required.
+
+For task follow-up, append the approved follow-up work directly into the relevant stage markdown files for the same running ID.
+
+### 5. Route Back
+
+- `/40-Implement` for immediate corrective work
+- `/50-Verify` when only verification needs another pass
+- `/10-Define` or `/20-Spec` when the follow-up becomes genuinely new scope
+
+## Output
+
+Return:
+
+- mode used
+- classification summary
+- what changes now versus later
+- where the follow-up was recorded
+- exact recommended next command

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

@@ -1,97 +1,97 @@
----
-name: roadmap-strategy
-description: Create or refresh product roadmap direction using markdown-first discovery and roadmap artifacts. Use when strategic planning should stay outside the mainline but still follow DevFlow 2.0 contracts.
----
-
-# Roadmap Strategy
-
-## Overview
-
-This skill is the shared behavior layer behind `Roadmap`.
-
-It replaces the older JSON-centered roadmap flow with a markdown-first strategy workflow that still preserves structured validation.
-
-## Related Assets
-
-This skill should reuse and align with:
-
-- `.agent/resources/schemas/roadmap_discovery.template.md`
-- `.agent/resources/schemas/roadmap.template.md`
-- `ROADMAP.md`
-
-## When to Use
-
-- when product direction, priority, or sequencing needs a dedicated roadmap pass
-- when competitor, PRD, research, or delivery insight should be consolidated into strategy
-- when roadmap work should stay outside the numbered mainline but still hand off cleanly into `PRD`, `/10-Define`, or `/20-Spec`
-
-## Canonical Artifacts
-
-Use markdown-first artifacts:
-
-- `devflow/roadmap/roadmap-discovery.md`
-- `ROADMAP.md`
-
-Optional supporting context may include:
-
-- `devflow/project_index.json` until project-index migration is fully complete
-- research notes
-- PRD outputs
-- release or insight notes
-
-## Process
-
-### 1. Load Current Strategy Context
-
-Read the minimum useful context:
-
-- existing `ROADMAP.md`
-- `devflow/roadmap/roadmap-discovery.md`
-- current research, competitor notes, PRD, or insights when relevant
-
-### 2. Refresh Discovery
-
-Capture:
-
-- project purpose
-- target users
-- current state
-- constraints
-- market context
-- known gaps
-
-Save discovery notes in `devflow/roadmap/roadmap-discovery.md` using the discovery template.
-
-### 3. Prioritize The Roadmap
-
-Group roadmap work into useful strategic buckets such as:
-
-- near-term improvements
-- medium-term bets
-- long-term bets
-- technical debt and platform readiness
-
-Keep priorities traceable to evidence from stage work, user feedback, competitor findings, or implementation insight.
-
-### 4. Save The Canonical Roadmap
-
-Update `ROADMAP.md` using `.agent/resources/schemas/roadmap.template.md`.
-
-Replace placeholder content fully and keep headings and tables intact so validation can inspect the roadmap structure.
-
-### 5. Route Back
-
-- `PRD` when product framing needs to deepen
-- `/10-Define` when roadmap decisions should become bounded work
-- `/20-Spec` when one item is ready for delivery contract work
-- `Brainstorm` when strategy is still too fuzzy to lock
-
-## Output
-
-Return:
-
-- what changed in discovery
-- what changed in the roadmap
-- priority rationale
-- validation result
-- the recommended next command
+---
+name: roadmap-strategy
+description: Create or refresh product roadmap direction using markdown-first discovery and roadmap artifacts. Use when strategic planning should stay outside the mainline but still follow DevFlow 2.0 contracts.
+---
+
+# Roadmap Strategy
+
+## Overview
+
+This skill is the shared behavior layer behind `Roadmap`.
+
+It replaces the older JSON-centered roadmap flow with a markdown-first strategy workflow that still preserves structured validation.
+
+## Related Assets
+
+This skill should reuse and align with:
+
+- `.agent/resources/schemas/roadmap_discovery.template.md`
+- `.agent/resources/schemas/roadmap.template.md`
+- `ROADMAP.md`
+
+## When to Use
+
+- when product direction, priority, or sequencing needs a dedicated roadmap pass
+- when competitor, PRD, research, or delivery insight should be consolidated into strategy
+- when roadmap work should stay outside the numbered mainline but still hand off cleanly into `PRD`, `/10-Define`, or `/20-Spec`
+
+## Canonical Artifacts
+
+Use markdown-first artifacts:
+
+- `devflow/roadmap/roadmap-discovery.md`
+- `ROADMAP.md`
+
+Optional supporting context may include:
+
+- `devflow/project_index.json` until project-index migration is fully complete
+- research notes
+- PRD outputs
+- release or insight notes
+
+## Process
+
+### 1. Load Current Strategy Context
+
+Read the minimum useful context:
+
+- existing `ROADMAP.md`
+- `devflow/roadmap/roadmap-discovery.md`
+- current research, competitor notes, PRD, or insights when relevant
+
+### 2. Refresh Discovery
+
+Capture:
+
+- project purpose
+- target users
+- current state
+- constraints
+- market context
+- known gaps
+
+Save discovery notes in `devflow/roadmap/roadmap-discovery.md` using the discovery template.
+
+### 3. Prioritize The Roadmap
+
+Group roadmap work into useful strategic buckets such as:
+
+- near-term improvements
+- medium-term bets
+- long-term bets
+- technical debt and platform readiness
+
+Keep priorities traceable to evidence from stage work, user feedback, competitor findings, or implementation insight.
+
+### 4. Save The Canonical Roadmap
+
+Update `ROADMAP.md` using `.agent/resources/schemas/roadmap.template.md`.
+
+Replace placeholder content fully and keep headings and tables intact so validation can inspect the roadmap structure.
+
+### 5. Route Back
+
+- `PRD` when product framing needs to deepen
+- `/10-Define` when roadmap decisions should become bounded work
+- `/20-Spec` when one item is ready for delivery contract work
+- `Brainstorm` when strategy is still too fuzzy to lock
+
+## Output
+
+Return:
+
+- what changed in discovery
+- what changed in the roadmap
+- priority rationale
+- validation result
+- the recommended next command