@rallycry/conveyor-skills 1.0.2 → 1.0.3
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
|
@@ -122,7 +122,10 @@ parked and the chat marker IS the claim.
|
|
|
122
122
|
|
|
123
123
|
Post to chat at real milestones only — claim, a blocking discovery, gates
|
|
124
124
|
green, PR — never play-by-play. Your turn output is not visible to the team;
|
|
125
|
-
chat is.
|
|
125
|
+
chat is. Post a blocking discovery with `milestone: "blocked"` only if you are
|
|
126
|
+
actually parked and cannot continue until a human acts — it is a quiet parking
|
|
127
|
+
note that pages nobody. When you need an answer, ask with AskUserQuestion; that
|
|
128
|
+
is what pages a person.
|
|
126
129
|
|
|
127
130
|
**Saving the plan and card fields:** `mcp__conveyor__update_task` handles
|
|
128
131
|
title, description, plan, status, and `githubBranch` on both surfaces. Story
|
|
@@ -134,8 +134,11 @@ touching Conveyor, unless they asked you to just ship it.
|
|
|
134
134
|
> create a NEW card, which is the local/MCP shape; `mcp__conveyor__create_task`
|
|
135
135
|
> does not exist in a pod. In a pod, the card exists and you are on it: save
|
|
136
136
|
> the plan with `mcp__conveyor__update_task` (`plan`, and `description` if it
|
|
137
|
-
> needs sharpening), post the same recommendation message to chat
|
|
138
|
-
> a pod does not promote its own card to
|
|
137
|
+
> needs sharpening), post the same recommendation message to chat with
|
|
138
|
+
> `milestone: "plan_ready"`, and stop — a pod does not promote its own card to
|
|
139
|
+
> Open. A parked plan is never `blocked`: that milestone means you cannot
|
|
140
|
+
> continue until a human acts, and it pages nobody. To page a person, ask them
|
|
141
|
+
> with AskUserQuestion. If the pod also has to leave
|
|
139
142
|
> plan mode, note that `update_task` carries no story points or risk; those go
|
|
140
143
|
> through `mcp__conveyor__update_task_properties`. Everything in Phases 1-3 is
|
|
141
144
|
> identical in both environments. To break a large pod card into a pack, use
|