Resolve divergences between Allium behavioral specification files and implementation code.
npx skills add https://github.com/juxt/claude-plugins --skill weed-juxt
Please help me install this Agent Skill. Skill: weed Source: https://github.com/juxt/claude-plugins/tree/main/plugins/allium/skills/weed Command: npx skills add https://github.com/juxt/claude-plugins --skill weed-juxt
This Skill solves the problem of Allium behavioral specifications diverging from their corresponding implementation code, which leads to outdated documentation, unexpected system behavior, and wasted debugging time when documented behavior does not match actual code functionality.
Use the weed skill to check all divergences between the order-processing.allium spec and the src/order_processor.clj implementation files.
High-intent search queries and answers about installing and using this skill.
To check for Allium spec drift, run a check-only divergence report against your implementation code. This identifies misaligned state transitions, missing trigger coverage, and unenforced invariants without modifying any files.
The best way to align outdated Allium specs with code is to update the specification files to match the current implementation. This synchronizes documented behavior with actual state transitions and trigger coverage in the codebase.
Yes, you can update implementation code to match an Allium behavioral specification. This mode modifies the code to enforce documented state transitions, external triggers, and invariants defined in the spec.
Yes, Allium spec alignment validates process-level state machine reachability, external trigger coverage, and invariant enforcement. It detects undeclared state changes in code rather than relying solely on line-by-line text comparison.
Use a spec alignment tool for Allium files when you need to validate complex process-level behaviors like state transition reachability and invariant enforcement, which manual line-by-line code auditing easily misses.
Unexpected system behavior during state transitions occurs when Allium specifications diverge from implementation code. Running a divergence report detects undeclared state changes and missing external trigger coverage causing the mismatch.
scottopellCompare .allium specifications with implementation code to detect divergences.
SumitvedpathakValidate Git branch names and required directories.
sburlGenerates random and adversarial inputs to detect crashes, hangs, and invariant violations across languages using fast-check, hypothesis, and Go fuzz.
igor1309Detect factual mismatches between markdown documentation and code in a repository.
