codymaster 4.3.0 → 4.4.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -109,7 +109,7 @@ Traditional approach: Load every SKILL.md to decide which skill to use.
109
109
  | Skill | Triggers | Summary |
110
110
  |-------|----------|---------|
111
111
  | `cm-start` | /cm-start, start workflow, begin objective, new task | Orchestrate full cm-* workflow from objective to production code |
112
- | `cm-dashboard` | /cm-dashboard, kanban, task board, show tasks, status board | Render Kanban board from cm-tasks.json — visual task overview |
112
+ | `cm-dashboard` | /cm-dashboard, kanban, task board, show tasks, status board | Render Kanban board from OpenSpec `tasks.md` and `cm-tasks.json` — visual task overview |
113
113
  | `cm-status` | /cm-status, quick status, progress, what's next, blocked | Ultra-concise progress summary: done / next / blocked |
114
114
 
115
115
  ### Planned (not yet implemented) 🧪
@@ -26,7 +26,7 @@ When this workflow is called, the AI Assistant should execute the following acti
26
26
  - Count source files → determine intelligence level (MINIMAL/LITE/STANDARD/FULL)
27
27
  - IF level >= LITE: generate architecture diagram → `.cm/architecture.mmd`
28
28
  - IF level >= STANDARD: check CodeGraph → `codegraph status` → index if needed
29
- - IF level >= FULL: also check qmd (cm-deep-search)
29
+ - IF level >= STANDARD: also check qmd (cm-deep-search) for existing semantic vector databases and initialize/update if needed.
30
30
  - Log intelligence level to `CONTINUITY.md`
31
31
 
32
32
  1. **Understand Requirements (Planning & JTBD):**
@@ -50,20 +50,23 @@ When this workflow is called, the AI Assistant should execute the following acti
50
50
  - Apply `cm-tdd` + `cm-execution` → `cm-quality-gate`
51
51
 
52
52
  **L2 (Medium):** Full analysis flow
53
+ - Init OpenSpec (create `openspec/changes/[initiative-name]/` folder and artifacts manually)
53
54
  - Apply `cm-brainstorm-idea` if problem is ambiguous
54
- - Apply `cm-planning` (full implementation plan with task breakdown)
55
- - Create `cm-tasks.json` → launch RARV autonomous execution
55
+ - Apply `cm-planning` (full implementation plan with OpenSpec `tasks.md`)
56
+ - Create `cm-tasks.json` from `tasks.md` → launch RARV autonomous execution
56
57
  - Apply `cm-quality-gate` → `cm-safe-deploy`
57
58
 
58
59
  **L3 (Large):** Full + PRD + Architecture + Sprint
60
+ - Init OpenSpec (create `openspec/changes/[initiative-name]/` folder and artifacts manually)
59
61
  - Apply `cm-brainstorm-idea` (mandatory)
60
62
  - Apply `cm-planning` with FR/NFR requirement tracing
61
- - Sprint planning → `cm-tasks.json` with sprints
63
+ - Sprint planning → `openspec/changes/[objective]/tasks.md` sync with `cm-tasks.json`
62
64
  - Apply `cm-execution` (Mode E: TRIZ-Parallel for speed)
63
65
  - Apply `cm-quality-gate` → `cm-safe-deploy`
64
66
 
65
67
  3. **Track Progress:**
66
- - Create or update `cm-tasks.json` by breaking the objective into specific tasks
68
+ - Create `openspec/changes/[objective]/tasks.md` (for standardized spec tracking)
69
+ - Create or update `cm-tasks.json` (for autonomous agent execution)
67
70
  - Suggest `/cm-dashboard` for visual tracking
68
71
  - Suggest `/cm-status` for quick terminal summary
69
72