skills/engineering/orchestrate-herdr/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: orchestrate-herdr
-description: "Drive a plan from the current conversation or an @file through a published spec, linked dependency-aware tickets, and one-at-a-time isolated implementation to a merged PR, using Herdr and Pi agents with no Bun CLI or orchestration runtime. Use only when explicitly invoked, e.g. /orchestrate-herdr <goal> or /orchestrate-herdr @file. Composes to-spec, to-tickets, dual-review, code-review, worktrees, and forge-cli."
+description: "Drive a plan from context or @file through a published spec, linked tickets, and one-at-a-time isolated implementation to a merged PR using Herdr and Pi agents."
 disable-model-invocation: true
 ---
 

skills/engineering/to-spec/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: to-spec
-description: "Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed. Use when the user wants a spec from the current conversation, or when an orchestration workflow needs to publish a spec from context.
+description: "Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed. Use when the user wants a spec from the current conversation or an orchestration workflow needs to publish one from context."
 ---
 
 This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user; just synthesize what you already know.

skills/engineering/to-tickets/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: to-tickets
-description: Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker). Use when the user wants tickets from a plan or spec, or when an orchestration workflow needs to break a spec into agent-grabbable tickets."
+description: "Break a plan, spec, or the current conversation into tracer-bullet tickets with blocking edges, published to the configured tracker. Use when the user wants tickets from a plan or spec, or an orchestration workflow needs agent-grabbable tickets."
 ---
 
 # To Tickets