What problem does it solve?
Writing AGENTS.md files for coding agents often produces descriptive documentation instead of actionable instructions, leading to inconsistent agent behavior across packages and modules. This Skill enforces a single prescriptive convention so every AGENTS.md tells agents exactly what to do, what to ask about, what never to do, and how to validate their work.
Core Features & Use Cases
- Boundary Convention Enforcement: Guarantees every AGENTS.md contains the four mandatory sections — Always, Ask First, Never, and Validation Commands — in the correct order with size-scaled minimum rule counts.
- Prescriptive Tone Transformation: Converts descriptive prose ("The module provides...") into imperative MUST/MUST NOT rules, decision tables, and numbered checklists.
- Legacy Migration: Migrates pre-existing AGENTS.md files with legacy headings (MUST Rules, Critical Rules) into the boundary convention without losing high-risk operational details.
- Use Case: When adding a new Open Mercato package or module, invoke this Skill to generate a compliant AGENTS.md with correct structure, tone, validation commands, and a root Task Router update.
Quick Start
Ask the agent to create an AGENTS.md for your new Open Mercato package following the boundary convention with Always, Ask First, Never, and Validation Commands sections.
