implement-slice
Build exactly one vertical slice, prove it in the running product, and commit it with the proof attached. One call is one slice; the next slice gets a fresh conversation. Progress lives only in git: a slice is done when its commit is on the branch.
Steps
-
Find the slices file: the path given,
spec/features/<slug>/slices.jsonfor a feature the user names, the only slices file underspec/features/, or ask.<slug>is its folder name; the branch isslices/<slug>. Read it and the spec it names. -
Find the verify skill: a project skill that runs the product and records whether checks passed, and its feature map. With none, tell the user to run
/make-verifyand end the turn. -
Get on the branch. A dirty tree stops the skill: list the files and leave them to the user. Switch to
slices/<slug>and pull, or create it from the up-to-date default branch. Stop if the slices file or its spec is not committed on this branch, itscommitis not an ancestor ofHEAD, or the verify skill is not on this branch yet. -
Pick the slice from the trailers on
<default-branch>..HEAD: