@rallycry/conveyor-skills 1.0.7 → 1.0.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rallycry/conveyor-skills",
-  "version": "1.0.7",
+  "version": "1.0.9",
   "description": "Shared Claude Code skills for Conveyor consumer repos, linked into .claude/skills via the conveyor-skills CLI",
   "keywords": [
     "claude",

package/skills/conveyor-build/SKILL.md

@@ -111,7 +111,11 @@ task binding and no user account.
 1. Resolve the card from the argument — slug, id, or URL. **None given → ask
    which card.** Never infer one from the branch you happen to be on.
 2. `mcp__conveyor__get_task` for the full plan and
-   `mcp__conveyor__read_task_chat` for addenda and user answers. Consult
+   `mcp__conveyor__read_task_chat` for addenda and user answers. On a pack
+   child the source documents usually sit on the parent card:
+   `mcp__conveyor__list_task_files` with `task_id` set to the parent (in a pod;
+   the local surface spells it `taskId`) lists them, and
+   `mcp__conveyor__get_attachment` with the same `task_id` reads one. Consult
    `mcp__conveyor__get_tag` on the card's tags before diving in — a tag's
    overview and linked files are the fast path into the subsystem.
 3. Route on the card's shape:
@@ -249,7 +253,10 @@ Instead: post the answer, config, or findings with
 `mcp__conveyor__upload_attachment` (any file type, up to 25MB), and complete
 the card directly with `force_update_task_status("Complete")` — there is no PR
 or review step for a no-code task. Never publish a deliverable as an off-card
-link; the card is where it belongs.
+link; the card is where it belongs. When a revision supersedes an earlier
+upload, remove the old copy with `mcp__conveyor__delete_attachment` (permanent,
+`fileId` from `list_task_files`) so the Files list shows one current version
+of each deliverable.
 
 When unsure, check the diff: a real diff means open a PR, no diff means finish
 in chat and mark it Complete.

package/skills/conveyor-plan/SKILL.md

@@ -100,6 +100,10 @@ Scale to the idea's size; a one-file tweak needs minutes, not a survey.
   already in your context. **Stop when you can cite a specific `file.ts:line`
   and a symbol name for every step your plan will contain** — that is the
   threshold, and more reading past it buys nothing.
+- **Attachments**: `mcp__conveyor__list_task_files` on the card, and on its
+  parent when the card is a pack child (in a pod pass `task_id`; the local
+  surface takes `taskId`). Source documents, screenshots and worksheets usually
+  live there, and a plan written without reading them plans the wrong work.
 - **Prior art**: `mcp__conveyor__search_tasks` on 2-3 keyword variants
   (`typeFilters` to include incidents/suggestions when relevant), then
   `mcp__conveyor__get_task` on the closest hits. You're looking for duplicates
@@ -157,6 +161,18 @@ and the order to verify in. Write it last, when you know which parts were hard.
 It is not optional and it is not a summary. It is the only channel your context
 has across the handoff, because handoffs carry the card and never the session.
 
+**Deliverables beyond the plan go on the card.** A diagram, an HTML report, a
+screenshot, or a data export the team should keep is attached with
+`mcp__conveyor__upload_attachment` — never published as a Claude artifact, which
+is an off-platform link the card cannot render. Write the file under `/tmp/`
+first (a Planner session may write there; the repo checkout stays read-only) and
+pass the caption so the file shows in the card thread rather than only in the
+Files grid. The caption field is spelled differently per surface, and both
+surfaces accept either name: in a pod pass `path` + `title`; on the local MCP
+pass `taskId` + `path` + `comment` (or `title`). An HTML deliverable must be
+self-contained — inline CSS, no `<script>`, no external assets — because the
+card serves it under `sandbox; default-src 'none'`.
+
 Size it: 1 SP default, 2 multi-file, 3 complex patterns/design, 5 hard. Larger
 → propose a pack (parent + `mcp__conveyor__create_subtask` children) instead of
 one mega-card. **Child→child ordering rides `create_subtask`/`update_subtask`'s

package/skills/conveyor-triage/SKILL.md

@@ -80,7 +80,9 @@ Find the code path the report implicates and, where you can, reproduce it. A
 diagnosis grounded only in reading is a hypothesis; a reproduction makes it a
 finding. Attach evidence to the card with `mcp__conveyor__upload_attachment` —
 a screenshot, a log excerpt, a short recording — so the Builder inherits proof
-rather than your assertion.
+rather than your assertion. A re-captured version replaces the old one:
+`mcp__conveyor__delete_attachment` (permanent, `fileId` from
+`list_task_files`) keeps the card's Files list to what is current.
 
 ## 5. Decide