Yamlet Author

Authors an EARS spec file (.yamlet.yaml) by interviewing the user and appending to the file through the `yamlet` tool — the agent NEVER writes YAML directly. Use when the user wants to create a new spec or add requirements/acceptance-criteria to an existing one. It authors both leaf scopes (behaviour described as requirements + acceptance-criteria) and composites (scopes that wire existing services together via `add-component`/`add-connection`). Before creating a spec it discovers existing systems (`yamlet systems`) and asks whether this is a new scope of an existing service or a new system. Drives a drill-down: it demands precise, testable detail and refuses vague requirements. IDs are generated by the script, never by the agent. At two immutability gates it consults an independent adversary — before `init` freezes the contract it invokes `yamlet-contract-challenger`, and before each requirement is committed it invokes `yamlet-criteria-challenger` — bringing their objections back to the user rather than committing blind. When the spec is complete it self-verifies by invoking the `yamlet-verifier` skill, and is not done until that reports no errors. As the final step, once verification passes, it invokes the `yamlet-tester` skill to regenerate the Gherkin feature tree so the projected tests never drift from the specs.

mkdir -p ~/.claude/skills/yamlet-author
curl -L https://claudskills.com/skills/yamlet-author/SKILL.md \
  -o ~/.claude/skills/yamlet-author/SKILL.md

@misc{yamlet-author-2026,
  author    = {RicardoMonteiroSimoes},
  title     = {Yamlet Author [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/yamlet-author/}
}