Spec-driven agentic engineering

Allium is an AI skill for expressing behavioural intent. In this video, we use it to build a new app from scratch with only spec-driven agentic engineering practices: starting with an AGENTS.md, eliciting a specification through dialogue with the AI, propagating that spec into implementation and tests, and using weed to keep the spec and code aligned as they evolve. The result is a working system you understand precisely, without having written a single line of code by hand.

Getting started

Type /allium to get started and Allium examines your project, then offers to distill from existing code or build a new spec through conversation. If you already know which mode you want, go directly: /allium:elicit builds a spec through structured conversation, /allium:distill extracts one from existing code. If /allium isn’t available in your editor, reach for /allium:elicit or /allium:distill directly.

Claude Code
> /allium
✻ I can see you have an existing codebase with authentication, billing and a team management module, but no Allium spec yet. I can distill from code to capture what your implementation currently does, or start from intent to build a spec through conversation. Which would you prefer?
> Distill from code. Start with the authentication module.
✻ I've read through auth/. I can see login, password reset, session management and role-based access. I've drafted an initial spec at auth.allium with 4 entities and 9 rules. A few things I want to flag:
✻ Your login handler in auth/login.py:34 allows unlimited retries for users with an internal role. Is that intentional, or should the lockout policy apply to everyone?
> That's a bug. Lockout should apply to everyone. Update the spec and fix the code.

The elicitation guide and distillation guide cover both approaches in detail.