plan-change
Plan a change when the scope, affected specifications, risks, or validation need evidence before any code is written.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- 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 upstream's documentation for the behaviour in question at the pinned version. 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 explicit non-goals, so the scope can be reviewed.
- Identify whether behaviour changes. Behaviour is upstream's to change: a difference
from
allium-cliat the pin is a defect here unless a decision record says otherwise (invariant 1). Identify the upstream result to reproduce before planning an adaptation. - Identify the boundaries crossed: the crate direction of invariant 2, the Python API's
shape (
crates/alliumpy/python/alliumpy/_alliumpy.pyiis canonical), and a new topic's owning page indocs/manifest.yml. An exposed API change moves the stub, the Rust binding and a pytest case together. - Name the risks and evidence that would settle them, and say which actions need authorization the agent does not already have.
- Split into independently verifiable steps, each pairing behaviour, test and documentation.
- Present the plan with open questions marked as open. Confirm the work runs green
with
just checkbefore treating it as done.
04 同仓库更多 Skills
rust-change
Implement or review a change to the core or the bindings crate with the layering, tests and documentation evidence the invariants require.
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.
python-change
Implement or review a change to the Python package, its stub, its tests or the console script with the stubtest, pytest and wheel-smoke evidence the invariants require.
project-check
Bring a workspace to a state where the full gate runs, and interpret what it reports.
plan-change
Plan a change when the scope, affected specifications, risks, or validation need evidence before any code is written.