A Snapshot Enhancement Proposal (SNEP) is the design document for a significant Snapshot improvement, new feature, or change. It explains the intended change and its motivation, then records the design, trade-offs, and validation plan. SNEPs give maintainers and the community a focused place to discuss a change before implementation begins.
Submit SNEPs as Markdown files in a GitHub pull request. Follow these rules:
- Create a tracking issue. Its issue number is also the SNEP number.
- Create a descriptively named directory under
docs/design, prefixed with that number—for example,docs/design/123-multi-gpu-support. - Name the proposal document
README.md. - Start with the SNEP template.
- Generate the table of contents with
make update-tocbefore opening or updating the pull request. Check it without modifying files by runningmake verify-toc.
When working with a compatible coding agent, invoke the repository's $snep
skill for a guided, section-by-section proposal draft. The skill is located at
.agents/skills/snep and follows this process and the template; it does not
replace proposal review.
SNEP is inspired by the Kubernetes Enhancement Proposal (KEP) process and the Grove Enhancement Proposal (GREP) convention.
The directory prefix is the tracking issue number. It supplies a stable, unique identifier for the SNEP and connects the design directly to the issue where its status and implementation work are tracked.