@rallycry/conveyor-skills 1.0.8 → 1.0.9
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/package.json
CHANGED
|
@@ -111,7 +111,11 @@ task binding and no user account.
|
|
|
111
111
|
1. Resolve the card from the argument — slug, id, or URL. **None given → ask
|
|
112
112
|
which card.** Never infer one from the branch you happen to be on.
|
|
113
113
|
2. `mcp__conveyor__get_task` for the full plan and
|
|
114
|
-
`mcp__conveyor__read_task_chat` for addenda and user answers.
|
|
114
|
+
`mcp__conveyor__read_task_chat` for addenda and user answers. On a pack
|
|
115
|
+
child the source documents usually sit on the parent card:
|
|
116
|
+
`mcp__conveyor__list_task_files` with `task_id` set to the parent (in a pod;
|
|
117
|
+
the local surface spells it `taskId`) lists them, and
|
|
118
|
+
`mcp__conveyor__get_attachment` with the same `task_id` reads one. Consult
|
|
115
119
|
`mcp__conveyor__get_tag` on the card's tags before diving in — a tag's
|
|
116
120
|
overview and linked files are the fast path into the subsystem.
|
|
117
121
|
3. Route on the card's shape:
|
|
@@ -249,7 +253,10 @@ Instead: post the answer, config, or findings with
|
|
|
249
253
|
`mcp__conveyor__upload_attachment` (any file type, up to 25MB), and complete
|
|
250
254
|
the card directly with `force_update_task_status("Complete")` — there is no PR
|
|
251
255
|
or review step for a no-code task. Never publish a deliverable as an off-card
|
|
252
|
-
link; the card is where it belongs.
|
|
256
|
+
link; the card is where it belongs. When a revision supersedes an earlier
|
|
257
|
+
upload, remove the old copy with `mcp__conveyor__delete_attachment` (permanent,
|
|
258
|
+
`fileId` from `list_task_files`) so the Files list shows one current version
|
|
259
|
+
of each deliverable.
|
|
253
260
|
|
|
254
261
|
When unsure, check the diff: a real diff means open a PR, no diff means finish
|
|
255
262
|
in chat and mark it Complete.
|
|
@@ -100,6 +100,10 @@ Scale to the idea's size; a one-file tweak needs minutes, not a survey.
|
|
|
100
100
|
already in your context. **Stop when you can cite a specific `file.ts:line`
|
|
101
101
|
and a symbol name for every step your plan will contain** — that is the
|
|
102
102
|
threshold, and more reading past it buys nothing.
|
|
103
|
+
- **Attachments**: `mcp__conveyor__list_task_files` on the card, and on its
|
|
104
|
+
parent when the card is a pack child (in a pod pass `task_id`; the local
|
|
105
|
+
surface takes `taskId`). Source documents, screenshots and worksheets usually
|
|
106
|
+
live there, and a plan written without reading them plans the wrong work.
|
|
103
107
|
- **Prior art**: `mcp__conveyor__search_tasks` on 2-3 keyword variants
|
|
104
108
|
(`typeFilters` to include incidents/suggestions when relevant), then
|
|
105
109
|
`mcp__conveyor__get_task` on the closest hits. You're looking for duplicates
|
|
@@ -80,7 +80,9 @@ Find the code path the report implicates and, where you can, reproduce it. A
|
|
|
80
80
|
diagnosis grounded only in reading is a hypothesis; a reproduction makes it a
|
|
81
81
|
finding. Attach evidence to the card with `mcp__conveyor__upload_attachment` —
|
|
82
82
|
a screenshot, a log excerpt, a short recording — so the Builder inherits proof
|
|
83
|
-
rather than your assertion.
|
|
83
|
+
rather than your assertion. A re-captured version replaces the old one:
|
|
84
|
+
`mcp__conveyor__delete_attachment` (permanent, `fileId` from
|
|
85
|
+
`list_task_files`) keeps the card's Files list to what is current.
|
|
84
86
|
|
|
85
87
|
## 5. Decide
|
|
86
88
|
|