- Add .pi/extensions/pi-worktree.ts with correct imports and default export - Define WorktreeEntry, WorktreeListResult, WorktreeError types - Register 4 tools: create, list, switch, remove (stubs) - Register /worktree command (stub) - Add helper function stubs: parseWorktreeList, pathExists, resolveWorktreeTarget - Uses defineTool() and Type from pi SDK for type-safe registration
18 lines
1,001 B
Markdown
18 lines
1,001 B
Markdown
# Task Plan — Issue #1: Create Extension File Structure
|
|
|
|
| Task | Description | TDD Status | Done |
|
|
|------|-------------|------------|------|
|
|
| 001 | Scaffold `.pi/extensions/pi-worktree.ts` with correct imports, tools, command, and helper stubs | ☑ RED ✅ GREEN ✅ REFACTOR | ☑ |
|
|
|
|
## Milestone Context (from implementation plan)
|
|
|
|
- **Milestone 1: Foundation** — Set up extension structure and register basic tools
|
|
- **Task 1.1**: Create Extension File — empty file with correct imports, loads without errors
|
|
- **Task 1.2**: Register Tool Scaffolding — four tool registrations with placeholder execute functions
|
|
- **Task 1.3**: Implement `git_worktree_list`
|
|
|
|
## Notes
|
|
|
|
- No traditional test framework — validation is: file exists at `.pi/extensions/pi-worktree.ts`, correct imports, pi loads without errors via `/reload` or restart.
|
|
- Single-file extension pattern: default export function receiving `ExtensionAPI`.
|
|
- Uses fj CLI for issue operations (auto-detected from git remote).
|