@yemi33/minions 0.1.716 → 0.1.717

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.
package/CHANGELOG.md CHANGED
@@ -1,11 +1,14 @@
1
1
  # Changelog
2
2
 
3
- ## 0.1.716 (2026-04-09)
3
+ ## 0.1.717 (2026-04-09)
4
4
 
5
5
  ### Features
6
6
  - add 11 missing CC action types for comprehensive API coverage
7
7
  - agents must check minions state before starting fresh research
8
8
 
9
+ ### Fixes
10
+ - add skill block format example to shared playbook
11
+
9
12
  ## 0.1.714 (2026-04-09)
10
13
 
11
14
  ### Other
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@yemi33/minions",
3
- "version": "0.1.716",
3
+ "version": "0.1.717",
4
4
  "description": "Multi-agent AI dev team that runs from ~/.minions/ — five autonomous agents share a single engine, dashboard, and knowledge base",
5
5
  "bin": {
6
6
  "minions": "bin/minions.js"
@@ -12,5 +12,17 @@
12
12
  - Work item descriptions and `resultSummary` for prior completed work on the same topic
13
13
  - `pinned.md` — critical context flagged by the human teammate
14
14
  This avoids duplicating research another agent already completed.
15
- - If you discover a repeatable workflow, output it as a ```skill block (the engine auto-extracts it).
15
+ - If you discover a repeatable workflow, output it as a fenced skill block. The engine auto-extracts it to `~/.claude/skills/<name>/SKILL.md`. Required format:
16
+ ````
17
+ ```skill
18
+ ---
19
+ name: skill-name-here
20
+ description: One-line description of when to trigger this skill
21
+ scope: minions
22
+ ---
23
+
24
+ Instructions for the skill go here.
25
+ ```
26
+ ````
27
+ The `name` and `description` fields are required. `scope` defaults to `minions` (global). Use `scope: project` + `project: ProjectName` for project-specific skills.
16
28
  - Do TDD where it makes sense — write failing tests first, then implement, then verify tests pass. Especially for bug fixes (write a test that reproduces the bug) and new utility functions.