62 lines
4.7 KiB
Markdown
62 lines
4.7 KiB
Markdown
---
|
|
status: resolved
|
|
parent: "[[031-slice-skill-map]]"
|
|
blocked-by: []
|
|
claimed-by: "019fbb2a-dbcd-79d2-ae72-c5bcdd1d714e"
|
|
claimed-at: "2026-07-31T22:57:30-04:00"
|
|
tags:
|
|
- ticket/research
|
|
---
|
|
|
|
# Slice skill old to-tasks research
|
|
|
|
## Question
|
|
|
|
What behavior should `slice` preserve, adapt, or reject from the old local `to-tasks` skill?
|
|
|
|
## Findings
|
|
|
|
The old skill accepts source material from the current conversation or an explicit argument such as a spec path, and only derives a feature slug when a `.claude/spec/<feature-slug>.md` source exists.
|
|
`slice` should preserve the source-material flexibility but reject the `.claude/spec`-specific slug contract because Wayfinder artifact provenance and parent links replace that field.
|
|
Source: `/home/alexion/wrk/dotfiles/modules/agents/claude-code/skills/to-tasks/SKILL.md`.
|
|
|
|
The old skill treats codebase exploration as optional when the agent has not already explored the area.
|
|
It says task titles and descriptions should use the project's domain glossary vocabulary and respect ADRs, and it explicitly looks for prefactoring that makes the implementation easier before slicing.
|
|
`slice` should preserve this behavior, but resolve glossary and ADR context through the active project and artifact destination rather than Claude-specific paths.
|
|
Source: `/home/alexion/wrk/dotfiles/modules/agents/claude-code/skills/to-tasks/SKILL.md`.
|
|
|
|
The core slicing rule is durable: each slice is a tracer bullet that delivers a narrow complete path through every layer the change requires, is demoable or verifiable on its own, and puts any prefactoring first.
|
|
`slice` should preserve this as a central contract.
|
|
Source: `/home/alexion/wrk/dotfiles/modules/agents/claude-code/skills/to-tasks/SKILL.md`.
|
|
|
|
The old skill requires a user review loop before writing task files.
|
|
It presents the proposed breakdown with file stem, blockers, and covered user stories when available, then asks whether granularity, dependency relationships, and merge or split choices are correct.
|
|
`slice` should preserve review-before-write by default, while allowing an explicitly noninteractive caller mode only if the new skill chooses to support one.
|
|
Source: `/home/alexion/wrk/dotfiles/modules/agents/claude-code/skills/to-tasks/SKILL.md`.
|
|
|
|
The old global numbering sequence is a legacy `.claude/tasks` mechanic.
|
|
It scans for the highest four-digit prefix under `.claude/tasks/` and never restarts per feature.
|
|
`slice` should reject that mechanism because Wayfinder artifacts use the AI-artifacts destination's naming and identifier allocation rules instead.
|
|
Source: `/home/alexion/wrk/dotfiles/modules/agents/claude-code/skills/to-tasks/SKILL.md`.
|
|
|
|
The old `blocked-by` field is a durable dependency concept but not a reusable representation.
|
|
It stores permanent dependencies by full task filename stem and treats a slice as pickable when every blocker has all acceptance criteria resolved.
|
|
`slice` should preserve permanent blocking edges and frontier pickability, but adapt them to Wayfinder `blocked-by` wikilinks and ticket statuses.
|
|
Sources: `/home/alexion/wrk/dotfiles/modules/agents/claude-code/skills/to-tasks/SKILL.md`, `/home/alexion/wrk/dotfiles/modules/agents/claude-code/skills/to-tasks/TASK-FORMAT.md`.
|
|
|
|
The old body format is worth carrying forward in adapted form.
|
|
It uses `## What to build` for a concise end-to-end behavior description and `## Acceptance criteria` for checklist completion.
|
|
It also says not to include brittle file paths or code snippets unless a prototype snippet encodes a settled decision more precisely than prose can.
|
|
`slice` should preserve these body sections and the anti-staleness rule inside Wayfinder task tickets.
|
|
Source: `/home/alexion/wrk/dotfiles/modules/agents/claude-code/skills/to-tasks/TASK-FORMAT.md`.
|
|
|
|
The old completion model is acceptance-criteria-centered.
|
|
A task is done when every criterion is checked as satisfied or deliberately dropped, with dropped work recorded in Implementation Notes by the implementation flow.
|
|
`slice` should preserve acceptance criteria as execution checklist content, but final lifecycle state must be the Wayfinder ticket `status` rather than a separate `.claude/tasks` convention.
|
|
Source: `/home/alexion/wrk/dotfiles/modules/agents/claude-code/skills/to-tasks/TASK-FORMAT.md`.
|
|
|
|
## Conclusion
|
|
|
|
`slice` should preserve the old skill's flexible source intake, optional codebase exploration, tracer-bullet vertical slicing, prefactoring-first bias, default user review loop, permanent blocker semantics, end-to-end task body, acceptance criteria, and anti-stale-detail guidance.
|
|
It should reject `.claude/tasks` output, `.claude/spec` feature-slug metadata, four-digit task numbering, filename-stem blockers, and `.claude/tasks` completion semantics in favor of Wayfinder artifacts.
|