tend

Translate vague Allium requirements into precise .allium specifications.

1|Updated May 22, 2013
One-click install
npx skills add https://github.com/scottopell/dotfiles --skill tend-scottopell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tend
Source: https://github.com/scottopell/dotfiles/tree/main/home-dir-configs/claude/skills/allium/skills/tend
Command: npx skills add https://github.com/scottopell/dotfiles --skill tend-scottopell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps maintain and refine Allium specification files to ensure health and integrity, preventing vague requirements from seeping into specs and causing ambiguous outcomes.

Core Features & Use Cases

  • Add new entities, variants, rules, triggers, surfaces and contracts to existing specs, including migrating specs to newer language versions.
  • Fix syntax errors and validation issues in .allium files and restructure specs for clarity and maintainability.
  • Push back on vague requirements with probing questions to preserve intent and avoid ambiguous implementations.

Quick Start

Provide a vague spec request and let Tend transform it into a precise Allium specification ready for validation.

Frequently Asked Questions about tend

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

FAQPage Schema
How do I refine vague Allium spec requirements into precise .allium specifications?

To refine vague Allium spec requirements, you translate them into precise, well-formed .allium specifications by consulting the language reference, reviewing existing .allium files, and running allium check to verify syntax before applying changes.

What is the best way to fix syntax errors and validation issues in .allium files?

The best way to fix syntax errors in .allium files is to review the relevant files, consult the language reference for correct structure, and run allium check to verify syntax before applying the necessary corrections.

Can I migrate existing Allium specs to a newer language version?

Yes, you can migrate existing Allium specs to a newer language version by updating entities, variants, rules, triggers, surfaces, and contracts, then verifying the migrated .allium files with allium check.

How do you handle ambiguous requirements when writing Allium specifications?

To handle ambiguous requirements in Allium specifications, you push back on vague inputs with probing questions to preserve intent, ensuring the final .allium files avoid ambiguous implementations and outcomes.

Do I need the allium check command to validate .allium specification files?

You need the allium check command when available to verify syntax and validation errors before applying changes to .allium files, ensuring the specifications remain well-formed and precise.