@jakkrichm/create-nexus-devflow 2.0.0 → 2.0.2

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

@@ -1,131 +1,131 @@
 ---name: insight
-
-description: Insight Extraction - Extract reusable lessons, file insights, patterns, gotchas, recommendations, and 9arm-skills/post-mortem learning from completed work.
----
-
-# Phase 54: Insight Extraction
-
-## Target: $ARGUMENTS
-
-Use this workflow after implementation, QA, human approval, PR review, or a debugging session to preserve useful knowledge for future work.
-
-Primary behavior now lives in the `insight-capture` skill. Keep this workflow as the compatibility wrapper and knowledge-capture entry point.
-
-## Prompt Source
-
-Adapted from:
-
-- `insight_extractor.md`
-
-Additional credited discipline when the source work is a bug, regression, or incident:
-
-- `.agents/skills/9arm-skills/post-mortem/SKILL.md`
-- Source pack: `9arm-skills`
-- Credit: `thananon/9arm-skills`
-- Upstream: https://github.com/thananon/9arm-skills
-- Adapted for: Antigravity IDE / Nexus-DevFlow
-
-## Process
-
-### 1. Load Evidence
-
-Inspect the available evidence:
-
-- git diff or recent commits
-- `40-implement.md`
-- `50-verify.md`
-- `70-release.md`
-- `60-report.md`
-- modified files
-- human feedback or PR comments
-
-### 2. Extract Reusable Knowledge
-
-Capture only actionable knowledge:
-
-- file purpose and important changes
-- reusable patterns
-- gotchas and triggers
-- approach outcome
-- alternatives tried
-- context or token usage notes that explain avoidable overhead
-- recommendations for future sessions
-
-Avoid generic notes that do not help future work.
-
-For bug, regression, or incident work, apply the `post-mortem` lens only after fix and validation evidence exist:
-
-- what broke
-- impact
-- reliable repro or timeline
-- root cause
-- fix
-- validation evidence
-- why it slipped through
-- prevention or follow-up
-
-### 3. Save Or Route Insights
-
-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
-
-For token/context learning, prefer the smallest concrete note:
-
-- what context was loaded unnecessarily
-- which file, artifact, or agent handoff caused repeated reading
-- what should be passed as minimal context next time
-- exact token counts only when they are available from the runtime or provider
-
-When updating `devflow/lessons.md`, inspect `.agent/resources/schemas/lessons.template.md` first and replace any placeholder text with concrete incident facts, insight, prevention, and follow-up action.
-
-If task logs are appropriate:
-
-If this insight must be tied back to the running work item, record it in `50-verify.md`, `60-report.md`, `70-release.md`, or `devflow/lessons.md` rather than a legacy task log command.
-
-## Output
-
-Return:
-
-- file insights
-- patterns discovered
-- gotchas discovered
-- approach outcome
-- context usage notes
-- recommendations
-- where the insight was recorded or should be recorded
-
-If `post-mortem` was applied, include a short `Source Discipline` note crediting `9arm-skills/post-mortem`.
-
-## Relationship To DevFlow 2.0
-
-- 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`
-
-## Sources
-
-- `AGENTS.md`
-- `.agent/resources/schemas/lessons.template.md`
-- 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.
-  - `Help {ID}` - choose this when the next route is unclear.
-
-## Wiki Update Recommendation
-
-- **Needed**: `yes` for reusable lessons, gotchas, decisions, validated root causes, or token/context optimizations.
-- **Scope**: `project` for target-project lessons, `framework` for DevFlow workflow lessons.
-- **Reason**: Insight extraction is the safest handoff point for wiki compilation.
-- **Suggested Command**: `Wiki project ingest {source}`
-
+
+description: Insight Extraction - Extract reusable lessons, file insights, patterns, gotchas, recommendations, and 9arm-skills/post-mortem learning from completed work.
+---
+
+# Phase 54: Insight Extraction
+
+## Target: $ARGUMENTS
+
+Use this workflow after implementation, QA, human approval, PR review, or a debugging session to preserve useful knowledge for future work.
+
+Primary behavior now lives in the `insight-capture` skill. Keep this workflow as the compatibility wrapper and knowledge-capture entry point.
+
+## Prompt Source
+
+Adapted from:
+
+- `insight_extractor.md`
+
+Additional credited discipline when the source work is a bug, regression, or incident:
+
+- `.agents/skills/9arm-skills/post-mortem/SKILL.md`
+- Source pack: `9arm-skills`
+- Credit: `thananon/9arm-skills`
+- Upstream: https://github.com/thananon/9arm-skills
+- Adapted for: Antigravity IDE / Nexus-DevFlow
+
+## Process
+
+### 1. Load Evidence
+
+Inspect the available evidence:
+
+- git diff or recent commits
+- `40-implement.md`
+- `50-verify.md`
+- `70-release.md`
+- `60-report.md`
+- modified files
+- human feedback or PR comments
+
+### 2. Extract Reusable Knowledge
+
+Capture only actionable knowledge:
+
+- file purpose and important changes
+- reusable patterns
+- gotchas and triggers
+- approach outcome
+- alternatives tried
+- context or token usage notes that explain avoidable overhead
+- recommendations for future sessions
+
+Avoid generic notes that do not help future work.
+
+For bug, regression, or incident work, apply the `post-mortem` lens only after fix and validation evidence exist:
+
+- what broke
+- impact
+- reliable repro or timeline
+- root cause
+- fix
+- validation evidence
+- why it slipped through
+- prevention or follow-up
+
+### 3. Save Or Route Insights
+
+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
+
+For token/context learning, prefer the smallest concrete note:
+
+- what context was loaded unnecessarily
+- which file, artifact, or agent handoff caused repeated reading
+- what should be passed as minimal context next time
+- exact token counts only when they are available from the runtime or provider
+
+When updating `devflow/lessons.md`, inspect `.agent/resources/schemas/lessons.template.md` first and replace any placeholder text with concrete incident facts, insight, prevention, and follow-up action.
+
+If task logs are appropriate:
+
+If this insight must be tied back to the running work item, record it in `50-verify.md`, `60-report.md`, `70-release.md`, or `devflow/lessons.md` rather than a legacy task log command.
+
+## Output
+
+Return:
+
+- file insights
+- patterns discovered
+- gotchas discovered
+- approach outcome
+- context usage notes
+- recommendations
+- where the insight was recorded or should be recorded
+
+If `post-mortem` was applied, include a short `Source Discipline` note crediting `9arm-skills/post-mortem`.
+
+## Relationship To DevFlow 2.0
+
+- 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`
+
+## Sources
+
+- `AGENTS.md`
+- `.agent/resources/schemas/lessons.template.md`
+- 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.
+  - `Help {ID}` - choose this when the next route is unclear.
+
+## Wiki Update Recommendation
+
+- **Needed**: `yes` for reusable lessons, gotchas, decisions, validated root causes, or token/context optimizations.
+- **Scope**: `project` for target-project lessons, `framework` for DevFlow workflow lessons.
+- **Reason**: Insight extraction is the safest handoff point for wiki compilation.
+- **Suggested Command**: `Wiki project ingest {source}`
+

package/template/.claude/skills/insight-capture/SKILL.md

@@ -1,84 +1,84 @@
----
-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.
----
-
-# Insight Capture
-
-## Overview
-
-This skill is the shared behavior layer behind `Insight`.
-
-It preserves the valuable learning workflow from the legacy system while treating insight capture as a support capability rather than a numbered stage.
-
-## Related Foundation Skills
-
-This skill should reuse and align with:
-
-- `.agents/skills/9arm-skills/post-mortem/SKILL.md`
-- `.agent/resources/schemas/lessons.template.md`
-
-## When to Use
-
-- 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
-
-## Process
-
-### 1. Load Evidence
-
-Inspect only the evidence needed:
-
-- `implement.md`
-- `verify.md`
-- `release.md`
-- `report.md`
-- recent diff, commits, or review comments when relevant
-
-### 2. Extract Actionable Knowledge
-
-Capture only useful knowledge such as:
-
-- important file or behavior changes
-- reusable patterns
-- gotchas and triggers
-- approach outcome
-- alternatives tried
-- context loading waste or handoff overhead
-- recommendations for future runs
-
-### 3. Apply Post-Mortem When Needed
-
-For bug, regression, or incident work, use the `post-mortem` lens only after fix and validation evidence exist:
-
-- what broke
-- impact
-- repro or timeline
-- root cause
-- fix
-- validation evidence
-- why it slipped through
-- prevention or follow-up
-
-### 4. Save To The Smallest Durable Destination
-
-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
-
-When updating `devflow/lessons.md`, use `.agent/resources/schemas/lessons.template.md` and replace placeholder text completely.
-
-## Output
-
-Return:
-
-- lessons captured
-- patterns and gotchas
-- approach outcome
-- recommendations
-- where the insight was recorded
-- whether `Wiki` or `/60-Report` should be the next handoff
+---
+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.
+---
+
+# Insight Capture
+
+## Overview
+
+This skill is the shared behavior layer behind `Insight`.
+
+It preserves the valuable learning workflow from the legacy system while treating insight capture as a support capability rather than a numbered stage.
+
+## Related Foundation Skills
+
+This skill should reuse and align with:
+
+- `.agents/skills/9arm-skills/post-mortem/SKILL.md`
+- `.agent/resources/schemas/lessons.template.md`
+
+## When to Use
+
+- 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
+
+## Process
+
+### 1. Load Evidence
+
+Inspect only the evidence needed:
+
+- `implement.md`
+- `verify.md`
+- `release.md`
+- `report.md`
+- recent diff, commits, or review comments when relevant
+
+### 2. Extract Actionable Knowledge
+
+Capture only useful knowledge such as:
+
+- important file or behavior changes
+- reusable patterns
+- gotchas and triggers
+- approach outcome
+- alternatives tried
+- context loading waste or handoff overhead
+- recommendations for future runs
+
+### 3. Apply Post-Mortem When Needed
+
+For bug, regression, or incident work, use the `post-mortem` lens only after fix and validation evidence exist:
+
+- what broke
+- impact
+- repro or timeline
+- root cause
+- fix
+- validation evidence
+- why it slipped through
+- prevention or follow-up
+
+### 4. Save To The Smallest Durable Destination
+
+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
+
+When updating `devflow/lessons.md`, use `.agent/resources/schemas/lessons.template.md` and replace placeholder text completely.
+
+## Output
+
+Return:
+
+- lessons captured
+- patterns and gotchas
+- approach outcome
+- recommendations
+- where the insight was recorded
+- whether `Wiki` or `/60-Report` should be the next handoff