@rallycry/conveyor-skills 0.1.3 → 0.1.4

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.
Files changed (3) hide show
  1. package/package.json +1 -1
  2. package/skills/conveyor-plan/references/plan-format.md +3 -2
  3. package/skills/conveyor-workflows/SKILL.md +3 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rallycry/conveyor-skills",
3
- "version": "0.1.3",
3
+ "version": "0.1.4",
4
4
  "description": "Shared Claude Code skills for Conveyor consumer repos, linked into .claude/skills via the conveyor-skills CLI",
5
5
  "keywords": [
6
6
  "claude",
package/skills/conveyor-plan/references/plan-format.md CHANGED
@@ -29,8 +29,9 @@ patterns/design choices, **5 SP** only for hard work. Split anything larger.
29
29
  ## Packs (parent + child tasks)
30
30
 
31
31
  A **pack** is Conveyor's bundle shape: a parent card with child cards.
32
- `create_subtask(parentTaskId, ...)` is the **only** way to parent a card —
33
- `create_task`/`update_task` have no parent field. Each child is a full card
32
+ `create_subtask(parentTaskId, ...)` creates a NEW child; to move an EXISTING
33
+ card under a parent (or out of one) use `set_task_parent`. `create_task` /
34
+ `update_task` have no parent field. Each child is a full card
34
35
  (own chat, plan, story points). Split into a pack only when the work is
35
36
  genuinely multiple independently buildable pieces (8-SP-tier); otherwise keep
36
37
  one card.
package/skills/conveyor-workflows/SKILL.md CHANGED
@@ -56,7 +56,9 @@ and let Conveyor's own automation do the linking.
56
56
  `conveyor-plan` skill.
57
57
  - **One card per deliverable/PR** (mirror packs below are the documented
58
58
  exception). Multi-PR work becomes a pack: children via
59
- `mcp__conveyor__create_subtask` (the ONLY way to parent a card) with
59
+ `mcp__conveyor__create_subtask` (new children) or
60
+ `mcp__conveyor__set_task_parent` (adopt an existing card into the pack, or
61
+ detach one with `parentTaskId: null`), with
60
62
  `mcp__conveyor__add_dependency` edges. Orchestration packs run children as
61
63
  their own builds/PRs; mirror packs (children created with
62
64
  `followParentStatus: true` on `create_subtask`) document already-done work