allium-env

Use for practical command recipes when agents operate Allium CLI commands on a folder of .allium specs.

Use when running deeper semantic and process-level analysis on a folder of .allium specs after allium check has passed.

Use when validating a folder of .allium specs with allium check. Resolves the folder to an entrypoint file, runs validation, interprets diagnostics, and defines the repair loop.

Use when defining or applying CI-quality command gates for a folder of .allium specs. Assumes allium is already available.

Use as a concise reference for Allium CLI commands when working on a folder of .allium specs. Assumes the CLI is already available and entrypoint resolution is required.

Use when an Allium CLI command fails on a folder of .allium specs. Classifies diagnostics, performs minimal repairs, and reruns the correct command against the resolved entrypoint.

Use when extracting or inspecting the structured domain model from a folder of .allium specs using allium model.

Use when summarizing, comparing, or acting on Allium CLI output from commands run against a folder of .allium specs.

Use as the operational entry point for running Allium CLI commands on a folder of .allium files. Chooses the right command sequence and resolves the folder to an entrypoint file.

Use when debugging syntax or parsed structure for one or more .allium files inside a folder, then returning to entrypoint-level validation.

Use when deriving test obligations from a folder of .allium specs with allium plan after check and analyse pass.

Use when operating the Allium CLI on a project folder of .allium specs and applying repo-specific conventions for entrypoints, command wrappers, quality gates, and artifact locations. Assumes the allium CLI is already installed and working.

Give your AI agents something more useful than a prompt. Velocity through clarity.

Start here for all Allium work. Routes to the right skill based on your task and tells you where specs live in this project.