1.9 KiB
status, parent, claimed-by, claimed-at, blocked-by, tags
| status | parent | claimed-by | claimed-at | blocked-by | tags | ||
|---|---|---|---|---|---|---|---|
| resolved | 031-slice-skill-map | 019fbb2a-dbcd-79d2-ae72-c5bcdd1d714e | 2026-07-31T23:27:00-04:00 |
|
|
Slice skill source
Question
Implement the packaged slice skill source from the approved implementation-ready specification.
What to build
Use /design-skill to add the slice skill under the repository's packaged skill source tree.
The skill should guide agents through slicing source material into Wayfinder task tickets, including artifact destination handling, review-before-write behavior, blocking-edge recording, and implementation-oriented task bodies.
Acceptance criteria
/design-skillhas been applied to draft and verify the skill structure.skills/slice/SKILL.mdexists and follows the approved specification.- Any companion reference files needed by the skill live under
skills/slice/. - The skill description is concise and accurately describes when to use
slice. - The skill does not instruct agents to write
.claude/tasks/files. - The skill uses Wayfinder artifact terminology consistently with
ARTIFACTS.md.
Implementation Notes
Created skills/slice/SKILL.md with disable-model-invocation: true.
No companion reference files were needed.
The skill source embeds the minimum Wayfinder ticket contract and tells agents to follow destination artifact conventions.
Applied /design-skill structurally by checking invocation mode, information hierarchy, completion criteria, duplication, sediment, sprawl, no-op behavior, and leading-word fit against skills/design-skill/GLOSSARY.md.
A headless Pi smoke-test with --skill skills/slice did not reliably exercise the user-invoked skill and produced horizontal slices, so I tightened the skill text to reject layer-only slices and to give an exact review shape.
The smoke-test evidence is under /tmp/slice-smoke/.