AGENT SKILL

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.

  1. Read AGENTS.md and docs/decisions/0001-specs-decide-behaviour.md. Identify which module under docs/specs/ owns the behaviour; each module's header states its scope. docs/OVERVIEW.md is direction and its open questions stay open until the owning ticket settles them.
  2. Read the whole module before editing, including its open question blocks. A change that belongs in another module's scope goes there instead. The vendored tend skill is the editing procedure and allium is the language reference.
  3. Edit the specification: state the rule as a trigger, its guards and its outcomes. Record what you could not decide as a new open question rather than guessing at a product decision.
  4. 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.
  5. Derive the tests from the changed clauses before writing implementation, and confirm they fail first. The vendored propagate skill derives them; just plan-spec docs/specs/<module>.allium prints the obligation count to record in the hand-back notes.
  6. Implement until the tests pass. Never weaken a test to make it pass; fix the specification and re-derive instead. The vendored weed skill finds where code and specification have diverged.
  7. Run just check-specs. It reads the JSON report rather than the exit code, so an info diagnostic fails it too, and an untouched checkout is clean, so anything it reports is a regression your change introduced. Then run just analyse-specs, which fails on any finding as well; a finding cannot be waived. Both run inside just check and need the pinned allium binary that just initialize installs into .tools/bin.
  8. Run just test, then just check before handing back.

04 同仓库更多 Skills

BiscuitBin
BiscuitBin/knarr

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.

★ 1
BiscuitBin
BiscuitBin/knarr

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.

★ 1
BiscuitBin
BiscuitBin/knarr

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.

★ 1
BiscuitBin
BiscuitBin/knarr

spec-change

Change an Allium specification and carry the change through the tests and the implementation.

★ 1
BiscuitBin
BiscuitBin/knarr

review-docs

Add or revise a handbook page so it satisfies the documentation contract and stays reachable.

★ 1
BiscuitBin
BiscuitBin/knarr

review-change

Review a change in this repository against its invariants, specifications, tests, and documentation contract.

★ 1