Maintains and evolves Allium specification files when you need to add entities, fix validation errors, or translate new requirements into well-formed specs. This isn't a passive formatter. It challenges vague requirements, asks probing questions about edge cases and failure modes, and pushes back when you haven't thought through the boundaries. The skill reads existing specs carefully before changing them, validates syntax with the CLI when available, and keeps an eye on data flow between rules, transition reachability, and whether your new triggers actually have corresponding surfaces. Worth noting it only touches spec files, never implementation code, and explicitly won't extract specs from existing code or run discovery sessions.
npx skills add https://github.com/juxt/allium --skill tend