tend

Translate vague user requests into precise, validated Allium specification updates.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/ravenoak/oh-my-stigmergy --skill tend-ravenoak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tend
Source: https://github.com/ravenoak/oh-my-stigmergy/tree/main/.agents/skills/tend
Command: npx skills add https://github.com/ravenoak/oh-my-stigmergy --skill tend-ravenoak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tend the Allium specification files to ensure their health and integrity. You are responsible for maintaining high-quality specs, pushing back on vagueness, and guiding changes toward well-formed definitions.

Core Features & Use Cases

  • Editing and refining entities, rules, triggers, surfaces and contracts within Allium specs.
  • Modifying existing specifications to accommodate changing requirements and refactoring when specs grow unwieldy.
  • Verifying syntax and validation by consulting the language reference and running the Allium CLI when available.

Quick Start

Describe the desired change to the Allium specs and I will translate it into a precise, validated update.

Frequently Asked Questions about tend

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

FAQPage Schema
How do I refactor Allium specifications to accommodate changing requirements?

To refactor Allium specifications, describe the desired structural changes to push back on vagueness and translate requests into precise, validated updates that maintain syntactic correctness across all spec files.

What is the best way to validate Allium specs for syntax errors?

Validating Allium specs involves consulting the language reference and running the Allium CLI when available to verify syntax, ensuring the health and integrity of all entities, rules, and contracts defined within the files.

How do I translate vague user requests into precise Allium entities and contracts?

Translating vague requests into precise Allium entities requires guiding changes toward well-formed definitions by proposing minimal, correct updates that fit the existing lifecycle and enforce strict specification editing.

Can I use this approach to migrate Allium specs across different projects?

Yes, you can migrate Allium specs across projects by restructuring and refactoring the files to ensure their health and integrity, prioritizing syntactic correctness and validation during the entire modification process.

When should I not use automated refactoring for Allium specification files?

You should avoid automated refactoring when requests remain vague and undefined, as maintaining high-quality specs requires pushing back on ambiguity to guide changes toward well-formed, manually validated definitions.

Does editing Allium specs require reading the language reference every time?

Reading the language reference is a required process guidance for editing Allium specs to verify syntax and validation, ensuring that all proposed minimal updates fit the existing lifecycle and maintain integrity.