[BUG] The YAML front matter is not well formatted

The YAML front matter created using /agents is written as one line of text where it should be formatted over multiple lines of text using YAML's | syntax.

Here is an example of the faulty output:

name: domain-consistency-enforcer
description: Use this agent when reviewing domain implementations, creating new domains, or modifying existing domains to ensure they follow the established patterns from OnboardingDomain. This includes checking architecture consistency, design patterns, naming conventions, file structure, and implementation patterns. Examples:\n\n<example>\nContext: The user is creating a new domain or modifying an existing one.\nuser: "Please create a new domain for handling user notifications"\nassistant: "I'll create the notifications domain following our established patterns."\n<function call omitted for brevity only for this example>\n<commentary>\nSince we're creating a new domain, I should use the domain-consistency-enforcer agent to ensure it follows the OnboardingDomain patterns.\n</commentary>\nassistant: "Now let me use the domain-consistency-enforcer agent to review the domain structure"\n</example>\n\n<example>\nContext: The user has just implemented changes to an existing domain.\nuser: "I've updated the SettingsDomain to add new functionality"\nassistant: "Let me review the changes to ensure they follow our domain patterns."\n<commentary>\nSince domain code was modified, use the domain-consistency-enforcer to verify consistency with OnboardingDomain patterns.\n</commentary>\n</example>\n\n<example>\nContext: The user is refactoring domain code.\nuser: "Can you help me refactor the MonetizationDomain?"\nassistant: "I'll refactor the MonetizationDomain and then verify it follows our standards."\n<function call omitted for brevity only for this example>\n<commentary>\nAfter refactoring, use the domain-consistency-enforcer to ensure the refactored code maintains consistency.\n</commentary>\nassistant: "Let me now verify the refactored domain follows our OnboardingDomain patterns"\n</example>
color: blue

Here is a better version:

name: domain-consistency-enforcer
description: |
  Use this agent when reviewing domain implementations, creating new domains, or modifying existing domains to ensure they follow the established patterns from OnboardingDomain. This includes checking architecture consistency, design patterns, naming conventions, file structure, and implementation patterns.

  <example>
  Context: The user is creating a new domain or modifying an existing one.
  user: "Please create a new domain for handling user notifications"
  assistant: "I'll create the notifications domain following our established patterns."
  <function call omitted for brevity only for this example>
  <commentary>
  Since we're creating a new domain, I should use the domain-consistency-enforcer agent to ensure it follows the OnboardingDomain patterns.
  </commentary>
  assistant: "Now let me use the domain-consistency-enforcer agent to review the domain structure"
  </example>

  <example>
  Context: The user has just implemented changes to an existing domain.
  user: "I've updated the SettingsDomain to add new functionality"
  assistant: "Let me review the changes to ensure they follow our domain patterns."
  <commentary>
  Since domain code was modified, use the domain-consistency-enforcer to verify consistency with OnboardingDomain patterns.
  </commentary>
  </example>

  <example>
  Context: The user is refactoring domain code.
  user: "Can you help me refactor the MonetizationDomain?"
  assistant: "I'll refactor the MonetizationDomain and then verify it follows our standards."
  <function call omitted for brevity only for this example>
  <commentary>
  After refactoring, use the domain-consistency-enforcer to ensure the refactored code maintains consistency.
  </commentary>
  assistant: "Let me now verify the refactored domain follows our OnboardingDomain patterns"
  </example>
color: blue