plan-change
Plan a change when the scope, affected specifications, risks, or validation need evidence before any code is written.
- License 许可
- Apache-2.0
- 所属仓库
- BiscuitBin/knarr
- 最近更新
- 2026-11-15
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- plan-change
- description
- Plan a change when the scope, affected specifications, risks, or validation need evidence before any code is written.
03 SKILL.md 正文
Plan a change
- Read
AGENTS.mdand the specification modules underdocs/specs/the change touches. Separate what you read from what you are guessing. - Inspect the worktree before proposing anything, and preserve work you did not author.
- Write down the observable outcome, and the explicit non-goals. A plan that does not say what it will not do cannot be reviewed for scope.
- Identify whether behaviour changes. If it does, the specification changes first: hand off to the
spec-changeskill rather than planning code against an unchanged spec. - Identify the boundaries crossed: a new effect needs an adapter outside the sans-IO core and a fake for the tests; a new Erlang call needs a named
*_ffi.erlmodule; a new process needs a supervisor; a new topic needs an owning documentation page; a new pin is a manual edit recorded perCONTRIBUTING.md. - Name the risks and the evidence that would settle them, and say which actions need authorization the agent does not already have: anything that leaves the worktree does.
- Split into steps that can each be verified on their own, each pairing behaviour with its test and its documentation.
- Present the plan with open questions marked as open. Confirm the plan runs green with
just checkbefore treating it as done.
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.