write-skill

Create a directory under skills/ with a SKILL.md file containing YAML frontmatter with name and description fields. The write-skill process requires you to first run a pressure scenario without the skill, document the agent's failure, then write the minimal skill that counters it.

Start the description with "Use when" followed by concrete triggering conditions like symptoms, user phrases, or file states. Never summarize the workflow in the description, because Claude will follow the summary and skip the skill body.

Do not create skills for one-off solutions, standard practices already documented elsewhere, or project-specific conventions, which belong in .specture/conventions.md. Mechanical constraints that a regex or validation can enforce should be automated instead.

Pick a scenario where the skill should fire, run it in a fresh session without the skill loaded, and observe the agent's rationalizations. Then repeat with the skill loaded and add explicit counters for every excuse the agent used to skip the discipline.

Skill bodies are written in English for multi-model compatibility and better search optimization. User-facing messages and templates produced by the skill are written in Spanish, matching the framework user's preference.