writing-agents

Define YAML frontmatter and sections for ADHD Framework .agent.md files.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/AI-Driven-Highspeed-Development/adhd_framework_v3 --skill writing-agents-ai-driven-highspeed-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-agents
Source: https://github.com/AI-Driven-Highspeed-Development/adhd_framework_v3/tree/main/modules/dev/instruction_core/data/skills/writing-agents
Command: npx skills add https://github.com/AI-Driven-Highspeed-Development/adhd_framework_v3 --skill writing-agents-ai-driven-highspeed-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Authoring ADHD Framework agent definitions can be error-prone without standardized structure. This skill enforces required YAML frontmatter, ensures mandatory section order, and guides the content to be wrapped in the <modeInstructions> block.

Core Features & Use Cases

  • Enforces YAML frontmatter fields (name, description, tools, handoffs) for .agent.md files.
  • Ensures mandatory sections order (Role Definition, <stopping_rules>, <core_philosophy>, <workflow>, <critical_rules>).
  • Provides templates and references/assets guidance to streamline authoring and validation.

Quick Start

Create or update an .agent.md by following the YAML frontmatter requirements and the mandatory section order, then wrap content in <modeInstructions>.

Frequently Asked Questions about writing-agents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure YAML frontmatter for agent definition files?

To structure YAML frontmatter for agent definition files, you must include the required fields name, description, tools, and handoffs within your .agent.md file to ensure proper role configuration.

What is the mandatory section order for ADHD Framework agent definitions?

The mandatory section order for ADHD Framework agent definitions is Role Definition, followed by <stopping_rules>, <core_philosophy>, <workflow>, and <critical_rules>, all wrapped within a <modeInstructions> block.

How do I validate agent definitions to prevent authoring errors?

You validate agent definitions by checking that the .agent.md file conforms to required YAML frontmatter fields, follows the mandatory section order, and correctly wraps all content within the <modeInstructions> block.

Can I update existing .agent.md files without breaking the workflow structure?

Yes, you can update existing .agent.md files by following the YAML frontmatter requirements and mandatory section order, ensuring all modified content remains properly wrapped in the <modeInstructions> block.

Do I need to manually wrap agent definition content in modeInstructions?

You need to wrap agent definition content in <modeInstructions> to enforce the multi-section content layout, ensuring the structured workflow and critical rules are properly contained within the .agent.md file.