Tighten skill trigger descriptions

Author: KSemenenko

skills/mcaf-adr-writing/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mcaf-adr-writing
-description: "Create or update an ADR under `docs/ADR/` for architectural decisions, dependency changes, data-model changes, or cross-cutting policy shifts. Use `references/adr-template.md` for scaffolding and keep the ADR self-contained, diagrammed, and testable."
+description: "Create or update an ADR under `docs/ADR/` for architectural decisions, dependency changes, data-model changes, or cross-cutting policy shifts. Use when the user asks to write, update, or document an ADR, record a design decision, capture architecture trade-offs, or justify a repo-wide technical policy."
 compatibility: "Requires repository write access; produces Markdown ADRs with Mermaid diagrams."
 ---
 

skills/mcaf-dotnet/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mcaf-dotnet
-description: "Primary entry skill for C# and .NET tasks. Detect the repo's language version, test runner, quality stack, and architecture rules; route to the right .NET subskills; and run the repo-defined post-change quality pass after any code change."
+description: "Primary entry skill for C# and .NET tasks. Detect the repo's language version, test runner, quality stack, and architecture rules; route to the right .NET subskills; and run the repo-defined post-change quality pass after any code change. Use when the user asks to implement, debug, review, or refactor .NET code, or asks which .NET skill or toolchain should apply."
 compatibility: "Requires a .NET solution or project; respects root and local `AGENTS.md` first."
 ---
 

skills/mcaf-feature-spec/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mcaf-feature-spec
-description: "Create or update a feature spec under `docs/Features/` with business rules, user flows, system behaviour, verification, and Definition of Done. Use before implementing non-trivial behaviour changes; use `references/feature-template.md` for scaffolding."
+description: "Create or update a feature spec under `docs/Features/` with business rules, user flows, system behaviour, verification, and Definition of Done. Use when the user asks for a feature spec, executable requirements, acceptance criteria, behaviour documentation, or a pre-implementation plan for non-trivial behaviour changes."
 compatibility: "Requires repository write access; produces Markdown docs with Mermaid diagrams and executable verification steps."
 ---