phase 6: add allium check verification to elicit and distill
- Add 'Verification' section instructing model to run 'allium check <file>' after writing .allium files - Applies to elicit and distill (tend/weed already had it from phase 5)
This commit is contained in:
@@ -870,6 +870,10 @@ If any remain, ask: "Would a stakeholder include this in a requirements doc?"
|
||||
|
||||
The extracted spec is a starting point. For targeted changes as requirements evolve, use /skill:tend. For checking ongoing alignment between the spec and implementation, use /skill:weed.
|
||||
|
||||
## Verification
|
||||
|
||||
After writing any `.allium` file, run `allium check <file>` if the CLI is available. Fix any reported issues before presenting the result.
|
||||
|
||||
## Syntax rules
|
||||
|
||||
Before writing any `.allium` file, read `../../allium/references/allium-rules.md` for syntax gotchas, naming conventions and anti-patterns. This covers common model mistakes (e.g. `with` vs `where`, `transitions_to` vs `becomes`, capitalised vs lowercase pipe values) that the language reference does not emphasise.
|
||||
|
||||
Reference in New Issue
Block a user