Plan small software changes into milestone specifications with verification methods.
npx skills add https://github.com/mckissinger/keel --skill spec-change
Please help me install this Agent Skill. Skill: spec-change Source: https://github.com/mckissinger/keel/tree/main/skills/spec-change Command: npx skills add https://github.com/mckissinger/keel --skill spec-change
This Skill helps teams turn small software changes into focused, build-ready specifications without the overhead of a full feature planning process while preserving verification standards.
Use the spec-change skill to create a verified milestone plan for this small change in my application.
High-intent search queries and answers about installing and using this skill.
A milestone specification for small software changes defines scope, affected surfaces, data changes, and integration boundaries. It includes done-conditions, verification methods, and ownership boundaries aligned with shared project rules, ensuring build-ready clarity without full feature overhead.
Milestone-level planning for a contained code fix or UI adjustment is needed when the change requires verified build paths, adversarial plan validation, and clear integration boundaries before implementation begins. This ensures tweaks and contained additions maintain project verification standards.
To create a verified build path for a backend tweak, author a self-contained milestone plan with done-conditions and verification methods. Apply milestone authoring rules, fidelity references for UI changes, and adversarial plan validation to ensure the implementation path is verified.
Included in a focused specification for software change management are scope, decisions, affected surfaces, data changes, and integration boundaries. It runs a compressed interview process to define implementation requirements, done-conditions, and verification methods for a single small change.
Yes, milestone planning for small changes requires adversarial plan validation before implementation begins. This validation process, alongside milestone authoring rules and verification methods, ensures the change specification remains robust and build-ready.
sumilee-pcuGenerate UX specifications and HUD design documents for game interfaces.
jchildreeVerify completion claims by executing and confirming command outputs before commits.
imkdwExplain the project's tech stack and guide architecture decisions.
Hypercart-Dev-ToolsGenerate product requirements documents and phased project plans through an eight-phase interview process.
