spec-change
Change an Allium specification and carry the change through the tests and the implementation.
- License 许可
- Apache-2.0
- 所属仓库
- BiscuitBin/knarr
- 最近更新
- 2026-11-15
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- spec-change
- description
- Change an Allium specification and carry the change through the tests and the implementation.
03 SKILL.md 正文
Change a specification
The specifications under docs/specs/ decide behaviour. Code that disagrees with one is wrong until the specification is changed to say otherwise, so the specification moves first and the implementation follows.
- Read
AGENTS.mdanddocs/decisions/0001-specs-decide-behaviour.md. Identify which module underdocs/specs/owns the behaviour; each module's header states its scope.docs/OVERVIEW.mdis direction and its open questions stay open until the owning ticket settles them. - Read the whole module before editing, including its
open questionblocks. A change that belongs in another module's scope goes there instead. The vendoredtendskill is the editing procedure andalliumis the language reference. - Edit the specification: state the rule as a trigger, its guards and its outcomes. Record what you could not decide as a new
open questionrather than guessing at a product decision. - Check that dependent modules still hold. A module others import is depended on by each of them, so a change to a trigger or an entity ripples.
- Derive the tests from the changed clauses before writing implementation, and confirm they fail first. The vendored
propagateskill derives them;just plan-spec docs/specs/<module>.alliumprints the obligation count to record in the hand-back notes. - Implement until the tests pass. Never weaken a test to make it pass; fix the specification and re-derive instead. The vendored
weedskill finds where code and specification have diverged. - Run
just check-specs. It reads the JSON report rather than the exit code, so aninfodiagnostic fails it too, and an untouched checkout is clean, so anything it reports is a regression your change introduced. Then runjust analyse-specs, which fails on any finding as well; a finding cannot be waived. Both run insidejust checkand need the pinnedalliumbinary thatjust initializeinstalls into.tools/bin. - Run
just test, thenjust checkbefore handing back.
04 同仓库更多 Skills
witness
Independently witness that an Allium loop's convergence claim is true and was reached honestly. Use when the user wants to verify a loop's self-report, confirm tests really pass and no generated test was weakened, produce a convergence certificate or witness record, gate CI on a trustworthy signal, or check that an autonomous run did not cheat its way to green.
weed
Weed the Allium garden. Find where Allium specifications and implementation code have diverged, and help resolve the divergences. Use when the user wants to check spec-code alignment, compare specs against implementation, audit for spec drift or violations, sync specs with code or code with specs, or verify whether the implementation matches what the spec says.
tend
Tend the Allium garden. Use when the user wants to write, edit, update, add to, improve, clarify, refine, restructure, fix or migrate Allium specs. Covers adding entities, rules, triggers, surfaces and contracts, fixing syntax or validation errors, renaming or refactoring within specs, migrating specs to a new language version, and translating requirements into well-formed specifications. Pushes back on vague requirements.
spec-change
Change an Allium specification and carry the change through the tests and the implementation.
review-docs
Add or revise a handbook page so it satisfies the documentation contract and stays reachable.
review-change
Review a change in this repository against its invariants, specifications, tests, and documentation contract.