01
It starts by itself
spec change requested. Runs in Claude Code routine.
- ↻ spec change requested
issue labelled spec-change
Spec changes stay valid.
Install the Tend skill and make it a habit: follow https://gethabit.dev/skills/juxt/tend.md
3K installs518 starsMIT licenceSource on GitHub ↗

Tend
by juxt · 3K installs
The skill
The tend skill writes, edits and refactors Allium specs: adding entities, rules, triggers and surfaces, fixing validation errors and migrating versions, while pushing back on vague requirements.
Only when you ask.
The habit
Spec changes stay valid.
↻ Runs by itselfspec change requested
When does it start? How does it check its work? What does it remember?
Stops after one change request per run and at most two check retries.
Your agent reads the language reference and the relevant .allium files, and runs allium check first.
It asks what happens at boundaries, under failure and with concurrency before writing.
It looks at data flow, transition graph impact and surface coverage for the new rule.
It adds only what was asked and follows the spec writing guidelines.
It runs allium check after every edit and allium analyse if the spec qualifies.
It states the behavioural intent, shows the changes and logs open questions.
It writes only in its own folder and asks you before anything goes out.
Read both lists. If the left one sounds like you, the Tend skill helps.
No. It works on .allium files only; code alignment is the weed skill.
It asks you, or records an open question when no person is reachable.
Copy the prompt at the top into your agent. It installs the skill from juxt/allium and sets up the habit. Or run npx skills add juxt/allium --skill tend.
Yes. It is published under MIT. Habit is free too.
Install the Tend skill and make it a habit: follow https://gethabit.dev/skills/juxt/tend.md
All juxt skills →More docs skills →
Works in
Made by juxt, published under MIT. Habit links to the original and never changes it. Is this your skill?