Add conventional naming fields to frontmatter schemas

[Copilot]

Adds standardized *_name fields across all frontmatter types for consistent metadata identification.

Changes

Frontmatter Schema Updates

• TaskFrontMatter: Added task_name field
• CommandFrontMatter: Added command_name field
• RuleFrontMatter: Added tool_name field (rules can serve dual role as tools)
• SkillFrontMatter: Added skill_name as alias for existing name field

All fields are optional and backward compatible.

Example Usage

# Rule with tool integration
---
rule_name: go-linting-standards
tool_name: golangci-lint
languages: [go]
mcp_server:
  command: golangci-lint
  args: [run]
---

# Task with conventional naming
---
task_name: fix-bug
resume: false
---

Documentation

• Added Section 5.7 "Conventional Naming Fields" with design rationale and examples
• Updated Appendix C field reference tables
• Added example demonstrating rule-as-tool pattern

Proposed Extensions

Foundation supports future additions: *_description, *_version, *_author, *_category, *_priority

Original prompt

Add names to the conventional front matter. SkillName RuleName, CommandName and TaskName. Since a rule can be a tool, add ToolName for rules only. Propose other conventions.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.