---
status: complete
tags:
  - wayfinder/map
---

# Slice skill

## Destination

Implement a packaged `slice` skill in the skills repository.
The skill turns a settled plan, spec, conversation, or artifact into Wayfinder task tickets for tracer-bullet implementation slices.

## Notes

The skill name is `slice`.
The repository source lives under `skills/slice/`.
Runtime enablement in dotfiles or another consumer repository is out of scope.
The skill should produce Wayfinder-compatible `ticket/task/afk` and `ticket/task/human` artifacts in the resolved AI-artifacts project destination, using that destination's naming and wikilink conventions.
The user's invocation is sufficient permission to slice the provided source material.
Implementation slices are destination work, not Wayfinder decision tickets.
The skill should not create `.claude/tasks/` files.
Task-ticket bodies should include implementation-oriented sections such as `## What to build`, `## Acceptance criteria`, and `## Implementation Notes` when useful.
`## Implementation Notes` may contain concise handoff guidance from slicing and later execution notes from the implementing agent.

## Frontier

None.

## Decisions so far

Preserve the old `to-tasks` source-intake, optional codebase exploration, tracer-bullet slicing, prefactoring-first bias, review loop, blockers, acceptance criteria, and anti-stale-detail guidance, but replace `.claude/tasks` output, feature-slug metadata, four-digit numbering, filename-stem blockers, and legacy completion semantics with Wayfinder artifacts.
Preserve Matt Pocock's explicit invocation, broad source intake, tracer-bullet discipline, blocker and frontier model, review loop, useful issue-body semantics, and wide-refactor expand-contract exception, adapt sizing toward coherent single-commit slices rather than fresh-context limits, and replace tracker, `.scratch`, label, native-link, and parent-issue mechanics with Wayfinder task-ticket artifacts.
Create open, unclaimed Wayfinder task tickets in the resolved artifact destination, use destination naming, identifier, wikilink, parent, blocker, status, claim, and Frontier rules, keep implementation detail in task artifacts rather than maps, and treat research, prototype, and grill tickets as planning work rather than implementation slices.
The implementation-ready `slice` specification defines explicit invocation, broad source handling, destination and parent resolution, coherent single-commit tracer-bullet slicing, the wide-refactor exception to strict vertical slicing, Wayfinder blocker and Frontier semantics, AFK versus human task classification, task body structure, review-before-write behavior, and verification expectations.
The packaged skill source lives at `skills/slice/SKILL.md`, is explicitly invoked, writes Wayfinder task artifacts rather than legacy `.claude/tasks`, and was tightened through `/design-skill` structural review.
`nix flake check "path:$PWD"` passes and verifies that the repository discovers and packages the new `slice` skill.

## Result

The packaged `slice` skill is implemented at `skills/slice/SKILL.md` and repository verification passes.

## Not yet specified

None.

## Out of scope

Enabling the skill in dotfiles or another consumer repository is outside this map.
Writing legacy `.claude/tasks/` files is outside this map.
