refactor(skills): rename to shorter verb-first names

.agents/memory/2026-05-24.md

@@ -6,8 +6,8 @@ Skill naming, metadata, document metadata, and utility skill coverage were align
 
 ## Observations
 
-- Renamed skills to a verb-first naming convention, including `write-tests` to `build-tests`.
-- Added general utility skills: `ask-questions`, `classify-content`, `coordinate-work`, `decide-direction`, `explore-context`, `plan-work`, `reason-problem`, `remember-context`, and `adapt`.
+- Renamed skills to a verb-first naming convention, including `write-tests` to `code-tests`.
+- Added general utility skills: `ask`, `classify`, `manage`, `choose`, `explore`, `plan`, `brainstorm`, `remember`, and `adapt`.
 - Added tags and YAML frontmatter metadata to skills.
 - Moved `author`, `version`, and `source` under `metadata`; added `metadata.category` to maintained skills, rules, and commands.
 - Updated `create-skill` and `create-rule` authoring guidance so new artifacts place categories under `metadata.category`.

.agents/skills/README.md

@@ -9,24 +9,24 @@ A complete skill is a directory with a required `SKILL.md` file and optional bun
 | Skill | Use it for | Notable resources |
 | --- | --- | --- |
 | [`adapt`](adapt/SKILL.md) | Detecting evidence-driven change needs and routing updates to the right skill, workflow, artifact, or owner. | [`evals/`](adapt/evals/) |
-| [`ask-questions`](ask-questions/SKILL.md) | Generating high-leverage questions, clarifying missing context, and surfacing assumptions. | [`evals/`](ask-questions/evals/) |
+| [`ask`](ask/SKILL.md) | Generating high-leverage questions, clarifying missing context, and surfacing assumptions. | [`evals/`](ask/evals/) |
 | [`audit-skill-security`](audit-skill-security/SKILL.md) | Auditing third-party or local skills before installing, updating, or trusting them. | [`references/audit-protocol.md`](audit-skill-security/references/audit-protocol.md) |
-| [`classify-content`](classify-content/SKILL.md) | Organizing material into meaningful groups by criteria, similarity, priority, dependency, or abstraction level. | [`evals/`](classify-content/evals/) |
-| [`build-backend`](build-backend/SKILL.md) | Production backend code: APIs, services, middleware, workers, persistence, validation, auth, and backend tests. | [`references/`](build-backend/references/), [`evals/`](build-backend/evals/) |
-| [`build-database`](build-database/SKILL.md) | Database code: schemas, DDL, OLTP SQL, analytics SQL, migrations, indexes, stored procedures, and dialect-specific scripts. | [`references/`](build-database/references/), [`evals/`](build-database/evals/) |
-| [`build-frontend`](build-frontend/SKILL.md) | Production frontend code: components, routes, client state, forms, styling, accessibility, performance, PWA behavior, and visualization. | [`references/`](build-frontend/references/), [`evals/`](build-frontend/evals/) |
-| [`build-tests`](build-tests/SKILL.md) | Automated tests and evals, including E2E, API, integration, performance, AI output, tool-use, RAG, and prompt regression suites. | [`references/`](build-tests/references/), [`scripts/`](build-tests/scripts/), [`evals/`](build-tests/evals/) |
-| [`coordinate-work`](coordinate-work/SKILL.md) | Managing active work across people, agents, tasks, dependencies, blockers, status, and handoffs. | [`evals/`](coordinate/evals/) |
+| [`brainstorm`](brainstorm/SKILL.md) | Working through ambiguous problems, assumptions, hypotheses, and problem framing before deciding or planning. | [`evals/`](brainstorm/evals/) |
+| [`choose`](choose/SKILL.md) | Comparing options, weighing tradeoffs, and recommending a direction using explicit criteria. | [`evals/`](choose/evals/) |
+| [`classify`](classify/SKILL.md) | Organizing material into meaningful groups by criteria, similarity, priority, dependency, or abstraction level. | [`evals/`](classify/evals/) |
+| [`code-backend`](code-backend/SKILL.md) | Production backend code: APIs, services, middleware, workers, persistence, validation, auth, and backend tests. | [`references/`](code-backend/references/), [`evals/`](code-backend/evals/) |
+| [`code-database`](code-database/SKILL.md) | Database code: schemas, DDL, OLTP SQL, analytics SQL, migrations, indexes, stored procedures, and dialect-specific scripts. | [`references/`](code-database/references/), [`evals/`](code-database/evals/) |
+| [`code-frontend`](code-frontend/SKILL.md) | Production frontend code: components, routes, client state, forms, styling, accessibility, performance, PWA behavior, and visualization. | [`references/`](code-frontend/references/), [`evals/`](code-frontend/evals/) |
+| [`code-tests`](code-tests/SKILL.md) | Automated tests and evals, including E2E, API, integration, performance, AI output, tool-use, RAG, and prompt regression suites. | [`references/`](code-tests/references/), [`scripts/`](code-tests/scripts/), [`evals/`](code-tests/evals/) |
 | [`create-rule`](create-rule/SKILL.md) | Writing or improving agent rules, instruction files, `AGENTS.md`, `CLAUDE.md`, Cursor rules, Copilot instructions, and `.agents/rules/*.md`. | [`scripts/`](create-rule/scripts/), [`evals/`](create-rule/evals/) |
 | [`create-skill`](create-skill/SKILL.md) | Creating, editing, reviewing, evaluating, packaging, optimizing, or improving skills. Start here for skill authoring. | [`references/`](create-skill/references/), [`scripts/`](create-skill/scripts/), [`eval-viewer/`](create-skill/eval-viewer/), [`agents/`](create-skill/agents/), [`assets/`](create-skill/assets/), [`evals/`](create-skill/evals/) |
-| [`decide-direction`](decide-direction/SKILL.md) | Comparing options, weighing tradeoffs, and recommending a direction using explicit criteria. | [`evals/`](decide-direction/evals/) |
 | [`design-api`](design-api/SKILL.md) | Contract-first API design for OpenAPI, AsyncAPI, GraphQL, endpoints, schemas, and request/response shapes. | [`references/`](design-api/references/), [`evals/`](design-api/evals/) |
-| [`explain-topic`](explain-topic/SKILL.md) | Explaining general knowledge, concepts, code, behavior, design, architecture, APIs, data flow, and tradeoffs in simple terms. | [`evals/`](explain-topic/evals/) |
-| [`explore-context`](explore-context/SKILL.md) | Investigating local repository, project document, and attached-artifact context with evidence. | [`evals/`](explore-context/evals/) |
+| [`explain`](explain/SKILL.md) | Explaining general knowledge, concepts, code, behavior, design, architecture, APIs, data flow, and tradeoffs in simple terms. | [`evals/`](explain/evals/) |
+| [`explore`](explore/SKILL.md) | Investigating local repository, project document, and attached-artifact context with evidence. | [`evals/`](explore/evals/) |
+| [`manage`](manage/SKILL.md) | Managing active work across people, agents, tasks, dependencies, blockers, status, and handoffs. | [`evals/`](manage/evals/) |
 | [`manage-git`](manage-git/SKILL.md) | Git branch naming, branch actions, commit-message drafting, and committing staged changes. | [`references/`](manage-git/references/), [`evals/`](manage-git/evals/) |
-| [`plan-work`](plan-work/SKILL.md) | Sequencing work before execution with phases, dependencies, risks, validation, and next actions. | [`evals/`](plan-work/evals/) |
-| [`reason-problem`](reason-problem/SKILL.md) | Working through ambiguous problems, assumptions, hypotheses, and problem framing before deciding or planning. | [`evals/`](reason-problem/evals/) |
-| [`remember-context`](remember-context/SKILL.md) | Preserving durable project facts, decisions, conventions, and useful observations in `.agents/memory/`. | [`evals/`](remember-context/evals/) |
+| [`plan`](plan/SKILL.md) | Sequencing work before execution with phases, dependencies, risks, validation, and next actions. | [`evals/`](plan/evals/) |
+| [`remember`](remember/SKILL.md) | Preserving durable project facts, decisions, conventions, and useful observations in `.agents/memory/`. | [`evals/`](remember/evals/) |
 | [`review-code`](review-code/SKILL.md) | Reviewing code changes, diffs, pull requests, branches, or patches for correctness, regressions, security, performance, and test gaps. | [`references/`](review-code/references/), [`evals/`](review-code/evals/) |
 | [`write-prd`](write-prd/SKILL.md) | Product requirements, product briefs, feature requirements, product scope, and launch requirements. | [`references/`](write-prd/references/), [`evals/`](write-prd/evals/) |
 | [`write-spec`](write-spec/SKILL.md) | Technical specs, design docs, functional and non-functional requirements, data contracts, UI specs, release specs, and handoff docs. | [`references/`](write-spec/references/), [`evals/`](write-spec/evals/) |
@@ -49,13 +49,13 @@ Use [`create-skill`](create-skill/SKILL.md) to create, revise, package, or evalu
 
 ```bash
 cd .agents/skills/create-skill
-python3 -m scripts.package_skill ../build-database /tmp/skills-dist
+python3 -m scripts.package_skill ../code-database /tmp/skills-dist
 ```
 
 Use this validation command when changing an existing skill:
 
 ```bash
-python3 .agents/skills/create-skill/scripts/quick_validate.py .agents/skills/build-database
+python3 .agents/skills/create-skill/scripts/quick_validate.py .agents/skills/code-database
 ```
 
 The key rule is simple: keep `SKILL.md` and any files it references together. If a skill says to read `references/postgres.md`, that file must remain available relative to the skill folder. Tiny rule, large consequences. Filesystems enjoy pettiness.

.agents/skills/adapt/SKILL.md

@@ -15,7 +15,7 @@ metadata:
   references:
     - create-skill
     - create-rule
-    - remember-context
+    - remember
 ---
 
 # adapt

.agents/skills/adapt/evals/evals.json

@@ -66,7 +66,7 @@
     {
       "id": "adapt-010",
       "category": "true-positive",
-      "prompt": "The eval caught a false positive trigger for plan-work. What should we adjust?",
+      "prompt": "The eval caught a false positive trigger for plan. What should we adjust?",
       "expected_trigger": "Trigger adapt.",
       "expected_output": "Identifies a trigger-boundary problem, targets the affected skill description or evals, and proposes a focused trigger or non-trigger update."
     },

.agents/skills/ask-questions/SKILL.md → .agents/skills/ask/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: ask-questions
+name: ask
 description: Generate high-leverage questions and clarify missing context. Use for question-generation requests like "what should I ask", "right questions", "what are we missing", "clarify this", and ambiguous requests blocked by unknowns.
 license: MIT
 tags:
@@ -8,13 +8,13 @@ tags:
   - questions
 metadata:
   author: Oleg Shulyakov
-  version: "1.0.2"
+  version: "1.0.3"
   source: github.com/olegshulyakov/agent.md
   catalog: utility
   category: collaboration
 ---
 
-# ask-questions
+# ask
 
 Generate the smallest useful set of questions that would change the next action.
 

.agents/skills/ask-questions/evals/evals.json → .agents/skills/ask/evals/evals.json

@@ -1,59 +1,59 @@
 {
   "evals": [
     {
-      "id": "ask-questions-001",
+      "id": "ask-001",
       "category": "true-positive",
       "prompt": "What should I ask the team before we commit to this migration approach?",
-      "expected_trigger": "Trigger ask-questions.",
+      "expected_trigger": "Trigger ask.",
       "expected_output": "Produces a short prioritized set of migration questions, with blockers separated from nice-to-have context."
     },
     {
-      "id": "ask-questions-002",
+      "id": "ask-002",
       "category": "true-positive",
       "prompt": "Clarify this feature request and tell me what context is missing.",
-      "expected_trigger": "Trigger ask-questions.",
+      "expected_trigger": "Trigger ask.",
       "expected_output": "Identifies missing goals, users, scope, acceptance criteria, and assumptions without planning implementation."
     },
     {
-      "id": "ask-questions-003",
+      "id": "ask-003",
       "category": "true-positive",
       "prompt": "What are the right questions to ask before choosing a vendor?",
-      "expected_trigger": "Trigger ask-questions.",
+      "expected_trigger": "Trigger ask.",
       "expected_output": "Returns high-leverage vendor selection questions ordered by decision impact."
     },
     {
-      "id": "ask-questions-004",
+      "id": "ask-004",
       "category": "true-positive",
       "prompt": "We have an ambiguous request to improve onboarding. What are we missing?",
-      "expected_trigger": "Trigger ask-questions.",
+      "expected_trigger": "Trigger ask.",
       "expected_output": "Surfaces missing user, workflow, metric, constraint, and success-context questions."
     },
     {
-      "id": "ask-questions-005",
+      "id": "ask-005",
       "category": "false-positive",
       "prompt": "Decide whether we should build or buy the onboarding tool.",
-      "expected_trigger": "Do not trigger ask-questions as the primary skill.",
+      "expected_trigger": "Do not trigger ask as the primary skill.",
       "expected_output": "Should compare options and recommend a direction rather than only generating questions."
     },
     {
-      "id": "ask-questions-006",
+      "id": "ask-006",
       "category": "false-positive",
       "prompt": "Plan the onboarding migration in milestones.",
-      "expected_trigger": "Do not trigger ask-questions as the primary skill.",
+      "expected_trigger": "Do not trigger ask as the primary skill.",
       "expected_output": "Should sequence work and include risks or verification; questions may appear only as blockers."
     },
     {
-      "id": "ask-questions-007",
+      "id": "ask-007",
       "category": "non-trigger",
       "prompt": "Explain how OAuth refresh tokens work.",
-      "expected_trigger": "Do not trigger ask-questions.",
+      "expected_trigger": "Do not trigger ask.",
       "expected_output": "Should explain the concept, not generate a discovery questionnaire."
     },
     {
-      "id": "ask-questions-008",
+      "id": "ask-008",
       "category": "non-trigger",
       "prompt": "Update the README to document the install command.",
-      "expected_trigger": "Do not trigger ask-questions.",
+      "expected_trigger": "Do not trigger ask.",
       "expected_output": "Should perform documentation work unless clarification is truly blocking."
     }
   ]

.agents/skills/reason-problem/SKILL.md → .agents/skills/brainstorm/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: reason-problem
+name: brainstorm
 description: Work through ambiguous problems before a firm output shape is warranted. Use for reasoning requests like "reason through", "think through", "brainstorm", "help me frame this", "let's work through this", and messy problem statements.
 license: MIT
 tags:
@@ -8,13 +8,13 @@ tags:
   - thinking
 metadata:
   author: Oleg Shulyakov
-  version: "1.0.2"
+  version: "1.0.3"
   source: github.com/olegshulyakov/agent.md
   catalog: utility
   category: productivity
 ---
 
-# reason-problem
+# brainstorm
 
 Clarify messy problems without forcing a premature answer.
 

.agents/skills/reason-problem/evals/evals.json → .agents/skills/brainstorm/evals/evals.json

@@ -1,59 +1,59 @@
 {
   "evals": [
     {
-      "id": "reason-problem-001",
+      "id": "brainstorm-001",
       "category": "true-positive",
       "prompt": "Let's reason through why this workflow feels fragile before we change it.",
-      "expected_trigger": "Trigger reason-problem.",
+      "expected_trigger": "Trigger brainstorm.",
       "expected_output": "Frames the problem, separates facts from assumptions, names hypotheses, and ends with a clearer next clarity step."
     },
     {
-      "id": "reason-problem-002",
+      "id": "brainstorm-002",
       "category": "true-positive",
       "prompt": "Help me think through whether this product idea is actually one problem or three.",
-      "expected_trigger": "Trigger reason-problem.",
+      "expected_trigger": "Trigger brainstorm.",
       "expected_output": "Explores interpretations, constraints, and possible framings without forcing an immediate recommendation."
     },
     {
-      "id": "reason-problem-003",
+      "id": "brainstorm-003",
       "category": "true-positive",
       "prompt": "Brainstorm possible causes for the drop in activation, but keep uncertainty visible.",
-      "expected_trigger": "Trigger reason-problem.",
+      "expected_trigger": "Trigger brainstorm.",
       "expected_output": "Generates hypotheses, marks assumptions, and identifies evidence that would distinguish them."
     },
     {
-      "id": "reason-problem-004",
+      "id": "brainstorm-004",
       "category": "true-positive",
       "prompt": "This architecture debate is messy. Help me frame the core tension.",
-      "expected_trigger": "Trigger reason-problem.",
+      "expected_trigger": "Trigger brainstorm.",
       "expected_output": "Clarifies competing goals and tradeoffs, then states a sharper problem framing."
     },
     {
-      "id": "reason-problem-005",
+      "id": "brainstorm-005",
       "category": "false-positive",
       "prompt": "Choose the best database for this workload and recommend one.",
-      "expected_trigger": "Do not trigger reason-problem as the primary skill.",
+      "expected_trigger": "Do not trigger brainstorm as the primary skill.",
       "expected_output": "Should use decision criteria and produce a recommendation."
     },
     {
-      "id": "reason-problem-006",
+      "id": "brainstorm-006",
       "category": "false-positive",
       "prompt": "Break this migration into phases with validation steps.",
-      "expected_trigger": "Do not trigger reason-problem as the primary skill.",
+      "expected_trigger": "Do not trigger brainstorm as the primary skill.",
       "expected_output": "Should produce a plan rather than an open-ended reasoning frame."
     },
     {
-      "id": "reason-problem-007",
+      "id": "brainstorm-007",
       "category": "non-trigger",
       "prompt": "Classify these bugs by severity and affected component.",
-      "expected_trigger": "Do not trigger reason-problem.",
+      "expected_trigger": "Do not trigger brainstorm.",
       "expected_output": "Should group items by explicit criteria."
     },
     {
-      "id": "reason-problem-008",
+      "id": "brainstorm-008",
       "category": "non-trigger",
       "prompt": "Remember that we chose SQLite for local development.",
-      "expected_trigger": "Do not trigger reason-problem.",
+      "expected_trigger": "Do not trigger brainstorm.",
       "expected_output": "Should write durable memory if appropriate."
     }
   ]

.agents/skills/decide-direction/SKILL.md → .agents/skills/choose/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: decide-direction
+name: choose
 description: Compare options and recommend a direction. Use for decision requests like "choose", "which option", "tradeoffs", "recommend", "should we", and option selection with criteria, risks, and reversibility.
 license: MIT
 tags:
@@ -8,13 +8,13 @@ tags:
   - tradeoffs
 metadata:
   author: Oleg Shulyakov
-  version: "1.0.2"
+  version: "1.0.3"
   source: github.com/olegshulyakov/agent.md
   catalog: utility
   category: project-management
 ---
 
-# decide-direction
+# choose
 
 Choose a direction by comparing viable options against explicit criteria.