29 lines
1.1 KiB
Markdown
29 lines
1.1 KiB
Markdown
---
|
|
status: resolved
|
|
parent: "[[038-implement-skill-map]]"
|
|
claimed-by: "019fbb66-80d0-7a01-8ac9-01255adfc7b2"
|
|
claimed-at: "2026-08-01T11:32:36-04:00"
|
|
blocked-by:
|
|
- "[[041-implement-skill-wayfinder-contract-research]]"
|
|
- "[[045-implement-skill-pi-worktree-extensions-research]]"
|
|
tags:
|
|
- ticket/grill
|
|
---
|
|
|
|
# Implement skill package scope grill
|
|
|
|
## Question
|
|
|
|
Beyond the now-in-scope packaged `implement`, `test-driven-development`, and `review` skills, should this migration also deliver legacy compatibility shims or documentation for how an out-of-scope Pi worktree extension should integrate?
|
|
|
|
## Resolution
|
|
|
|
No extras are in scope.
|
|
This migration should deliver only the three packaged skills: `implement`, `test-driven-development`, and `review`.
|
|
|
|
Do not add legacy `.claude/tasks` compatibility shims.
|
|
Old task files may be ordinary context only if an agent chooses to read them, but this workflow should not preserve their lifecycle semantics.
|
|
|
|
Do not add dedicated documentation for a future Pi worktree extension, Herdr, or Treehouse integration.
|
|
Worktree orchestration remains out of scope and can define its own contract later.
|