Shorten skill and agent meta descriptions

Trim the longer descriptions (up to ~300 chars) down to 110-170 chars
by cutting filler ("Use when...", "Produces X that...") while keeping
the trigger keywords intact.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: OdinMB

agents/opps-finder.md

@@ -1,6 +1,6 @@
 ---
 name: opps-finder
-description: Identifies new directions of work for ops projects — adjacent opportunities, strategic gaps, emerging context. Follows /find-opps skill autonomously, returns backlog-ready items.
+description: Find new directions for ops projects — opportunities, gaps, emerging context. Runs /find-opps autonomously, returns backlog items.
 tools: Read, Glob, Grep, WebSearch, WebFetch
 skills:
   - ops-workflow:find-opps

agents/task-finder.md

@@ -1,6 +1,6 @@
 ---
 name: task-finder
-description: Scans an ops project for new work items across 7 lenses (goal gaps, stale state, research, content, follow-through, hygiene, new directions). Updates backlog, returns summary.
+description: Scan an ops project across 7 lenses (goal gaps, stale state, research, content, follow-through, hygiene, directions). Updates backlog.
 tools: Read, Glob, Grep, Write, Edit
 model: sonnet
 skills:

skills/execute/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: execute
-description: Execute an approved ops plan — research, write, review, update state, harvest insights, and archive the plan. Use after a plan has been approved via the /plan skill. Never for code changes.
+description: Execute an approved ops plan — research, write, review, update state, archive. Use after /plan approval. Not for code.
 argument-hint: <path to plan file>
 ---
 

skills/find-opps/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: find-opps
-description: Identify new directions of work for an ops project — adjacent opportunities, strategic gaps, emerging context, preparatory research. Produces backlog-ready items that expand the project's horizon beyond existing plans. Use when the project's known work is well-mined and you need to look outward.
+description: Find new directions for an ops project — adjacent opportunities, strategic gaps, preparatory research. Use when known work is well-mined and you need to look outward.
 ---
 
 # Find Opportunities

skills/find-tasks/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: find-tasks
-description: Scan an ops repo's goals, state, and backlog to identify new valuable work items. Produces new backlog entries integrated into the project's knowledge system. Used by the get-to-work command — load when autonomously identifying what an ops project should be working on next.
+description: Scan an ops repo's goals, state, and backlog to surface new work items and add them to the backlog. Load when deciding what the project should work on next.
 ---
 
 # Ops Find Tasks

skills/prioritize/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: prioritize
-description: Select 2-3 independent tasks from an ops repo's active plans and backlog for autonomous execution. Considers impact, feasibility, independence, and project goals. Used by the get-to-work command — load when deciding which ops tasks to work on next.
+description: Pick 2–3 independent ops tasks from active plans and backlog for autonomous execution, weighing impact, feasibility, and project goals.
 ---
 
 # Ops Prioritize

skills/scaffold/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: scaffold
-description: Set up or adjust a non-code project management repo with the ops folder structure, CLAUDE.md, and INDEX.md hierarchy. Use when starting a new ops/PM repo from scratch or when an existing one needs to match the ops conventions.
+description: Set up or align a non-code ops/PM repo with the ops folder structure, CLAUDE.md, and INDEX.md hierarchy.
 disable-model-invocation: true
 ---
 

skills/update/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: update
-description: Process external information into the ops repo's knowledge base. Drop files in .update/ or pass content inline. Use when you have new information (research, status changes, reference material, deliverables) to integrate into the project's structured knowledge system.
+description: Integrate external info (research, status changes, reference material, deliverables) into the ops repo's knowledge base. Drop files in .update/ or pass content inline.
 argument-hint: <content to integrate, or empty to process .update/ folder>
 ---