@riverai7z/pi-todo 0.1.0 → 0.1.1

package/DESIGN.md

@@ -29,14 +29,14 @@ TaskState
 Allowed status transitions:
 
 ```text
-pending ───────► in_progress ───────► completed ───────► deleted
-   ▲                  ▲                    │
-   │                  └────────────────────┤
-   └───────────────────────────────────────┘
-
-in_progress may return to pending when work is released. Completed work may be reopened as pending or in_progress when verification or new requirements reveal more work. Deleted is terminal.
+pending     → in_progress | completed   | deleted
+in_progress → pending     | completed   | deleted
+completed   → pending     | in_progress | deleted
+deleted     → (none)
 ```
 
+This permits direct completion, releasing active work back to pending, and reopening completed work. Deleted is terminal.
+
 ## Persistence and branch semantics
 
 No project task file is written. Every tool result stores a complete snapshot in `details`:

package/README.md

@@ -9,7 +9,7 @@ Claude Code-style structured task management for Pi.
   - `TaskGet`
   - `TaskList`
   - `TaskUpdate`
-- Status workflow: `pending` → `in_progress` → `completed`, plus terminal `deleted` tombstones.
+- Any non-deleted status (`pending`, `in_progress`, `completed`) can move to either other non-deleted status or terminal `deleted`.
 - Owners, metadata, `blocks`/`blockedBy` dependencies, cycle rejection, and unresolved-blocker filtering.
 - Session-local state reconstructed from tool-result `details`, so `/reload`, compaction, `/tree`, and forks preserve branch semantics without project files.
 - Live responsive task overlay above the editor, with blocked work deprioritized and categorized overflow.

package/index.ts

@@ -55,6 +55,8 @@ const TaskUpdateSchema = Type.Object({
   ),
   addBlocks: Type.Optional(Type.Array(Type.String(), { description: "Task IDs that this task blocks" })),
   addBlockedBy: Type.Optional(Type.Array(Type.String(), { description: "Task IDs that block this task" })),
+  removeBlocks: Type.Optional(Type.Array(Type.String(), { description: "Task IDs this task no longer blocks" })),
+  removeBlockedBy: Type.Optional(Type.Array(Type.String(), { description: "Task IDs that no longer block this task" })),
   owner: Type.Optional(Type.String({ description: "New owner for the task" })),
   metadata: Type.Optional(
     Type.Record(Type.String(), Type.Unknown(), {
@@ -65,163 +67,13 @@ const TaskUpdateSchema = Type.Object({
 
 type TaskUpdateParams = Static<typeof TaskUpdateSchema>;
 
-const TASK_CREATE_DESCRIPTION = `Use this tool to create a structured task list for your current coding session. This helps you track progress, organize complex tasks, and demonstrate thoroughness to the user.
-It also helps the user understand the progress of the task and overall progress of their requests.
+const TASK_CREATE_DESCRIPTION = `Create a tracked task for multi-step or non-trivial work, a user-requested task list, or multiple requested items. Skip single trivial or conversational requests. Check TaskList first to avoid duplicates. Use a concise imperative subject, detailed description, and optional present-continuous activeForm. New tasks start pending; mark them in_progress before work and completed only when fully done.`;
 
-## When to Use This Tool
+const TASK_GET_DESCRIPTION = `Get one task's full details and dependencies by ID. Read it before starting or updating work to confirm current requirements and that blockedBy has no unresolved tasks. Use TaskList for an overview.`;
 
-Use this tool proactively in these scenarios:
+const TASK_LIST_DESCRIPTION = `List all non-deleted tasks with ID, status, subject, owner, and unresolved blockers. Use it to avoid duplicates, check progress, find available pending work, and pick newly unblocked work after completion. Prefer the lowest-ID unowned, unblocked task; use TaskGet for full details.`;
 
-- Complex multi-step tasks - When a task requires 3 or more distinct steps or actions
-- Non-trivial and complex tasks - Tasks that require careful planning or multiple operations
-- Plan mode - When using plan mode, create a task list to track the work
-- User explicitly requests todo list - When the user directly asks you to use the todo list
-- User provides multiple tasks - When users provide a list of things to be done (numbered or comma-separated)
-- After receiving new instructions - Immediately capture user requirements as tasks
-- When you start working on a task - Mark it as in_progress BEFORE beginning work
-- After completing a task - Mark it as completed and add any new follow-up tasks discovered during implementation
-
-## When NOT to Use This Tool
-
-Skip using this tool when:
-- There is only a single, straightforward task
-- The task is trivial and tracking it provides no organizational benefit
-- The task can be completed in less than 3 trivial steps
-- The task is purely conversational or informational
-
-NOTE that you should not use this tool if there is only one trivial task to do. In this case you are better off just doing the task directly.
-
-## Task Fields
-
-- **subject**: A brief, actionable title in imperative form (e.g., "Fix authentication bug in login flow")
-- **description**: What needs to be done
-- **activeForm** (optional): Present continuous form shown in the spinner when the task is in_progress (e.g., "Fixing authentication bug"). If omitted, the spinner shows the subject instead.
-
-All tasks are created with status \`pending\`.
-
-## Tips
-
-- Create tasks with clear, specific subjects that describe the outcome
-- After creating tasks, use TaskUpdate to set up dependencies (blocks/blockedBy) if needed
-- Check TaskList first to avoid creating duplicate tasks`;
-
-const TASK_GET_DESCRIPTION = `Use this tool to retrieve a task by its ID from the task list.
-
-## When to Use This Tool
-
-- When you need the full description and context before starting work on a task
-- To understand task dependencies (what it blocks, what blocks it)
-- After being assigned a task, to get complete requirements
-
-## Output
-
-Returns full task details:
-- **subject**: Task title
-- **description**: Detailed requirements and context
-- **status**: 'pending', 'in_progress', or 'completed'
-- **blocks**: Tasks waiting on this one to complete
-- **blockedBy**: Tasks that must complete before this one can start
-
-## Tips
-
-- After fetching a task, verify its blockedBy list is empty before beginning work.
-- Use TaskList to see all tasks in summary form.`;
-
-const TASK_LIST_DESCRIPTION = `Use this tool to list all tasks in the task list.
-
-## When to Use This Tool
-
-- To see what tasks are available to work on (status: 'pending', no owner, not blocked)
-- To check overall progress on the project
-- To find tasks that are blocked and need dependencies resolved
-- After completing a task, to check for newly unblocked work or claim the next available task
-- **Prefer working on tasks in ID order** (lowest ID first) when multiple tasks are available, as earlier tasks often set up context for later ones
-
-## Output
-
-Returns a summary of each task:
-- **id**: Task identifier (use with TaskGet, TaskUpdate)
-- **subject**: Brief description of the task
-- **status**: 'pending', 'in_progress', or 'completed'
-- **owner**: Agent ID if assigned, empty if available
-- **blockedBy**: List of open task IDs that must be resolved first (tasks with blockedBy cannot be claimed until dependencies resolve)
-
-Use TaskGet with a specific task ID to view full details including description and comments.`;
-
-const TASK_UPDATE_DESCRIPTION = `Use this tool to update a task in the task list.
-
-## When to Use This Tool
-
-**Mark tasks as resolved:**
-- When you have completed the work described in a task
-- When a task is no longer needed or has been superseded
-- IMPORTANT: Always mark your assigned tasks as resolved when you finish them
-- After resolving, call TaskList to find your next task
-
-- ONLY mark a task as completed when you have FULLY accomplished it
-- If you encounter errors, blockers, or cannot finish, keep the task as in_progress
-- When blocked, create a new task describing what needs to be resolved
-- Never mark a task as completed if:
-  - Tests are failing
-  - Implementation is partial
-  - You encountered unresolved errors
-  - You couldn't find necessary files or dependencies
-
-**Delete tasks:**
-- When a task is no longer relevant or was created in error
-- Setting status to \`deleted\` hides the task as a terminal tombstone in this Pi extension
-
-**Update task details:**
-- When requirements change or become clearer
-- When establishing dependencies between tasks
-
-## Fields You Can Update
-
-- **status**: The task status (see Status Workflow below)
-- **subject**: Change the task title (imperative form, e.g., "Run tests")
-- **description**: Change the task description
-- **activeForm**: Present continuous form shown in spinner when in_progress (e.g., "Running tests")
-- **owner**: Change the task owner (agent name)
-- **metadata**: Merge metadata keys into the task (set a key to null to delete it)
-- **addBlocks**: Mark tasks that cannot start until this one completes
-- **addBlockedBy**: Mark tasks that must complete before this one can start
-
-## Status Workflow
-
-Status progresses: \`pending\` → \`in_progress\` → \`completed\`
-
-Use \`deleted\` to hide a task as a terminal tombstone.
-
-## Staleness
-
-Make sure to read a task's latest state using \`TaskGet\` before updating it.
-
-## Examples
-
-Mark task as in progress when starting work:
-\`\`\`json
-{"taskId": "1", "status": "in_progress"}
-\`\`\`
-
-Mark task as completed after finishing work:
-\`\`\`json
-{"taskId": "1", "status": "completed"}
-\`\`\`
-
-Delete a task:
-\`\`\`json
-{"taskId": "1", "status": "deleted"}
-\`\`\`
-
-Claim a task by setting owner:
-\`\`\`json
-{"taskId": "1", "owner": "my-name"}
-\`\`\`
-
-Set up task dependencies:
-\`\`\`json
-{"taskId": "2", "addBlockedBy": ["1"]}
-\`\`\``;
+const TASK_UPDATE_DESCRIPTION = `Update one existing task after reading its latest state with TaskGet. Mark in_progress before work; mark completed only when fully accomplished and verified—keep in_progress if work is partial, blocked, or failing. Status transitions: pending → in_progress/completed/deleted; in_progress → pending/completed/deleted; completed → pending/in_progress/deleted; deleted is terminal. Use deleted for irrelevant or mistaken tasks. Add or remove dependency edges with addBlocks, addBlockedBy, removeBlocks, and removeBlockedBy; self-dependencies, missing additions, and cycles are rejected. Metadata is merged; null deletes a key. Provide at least one change.`;
 
 function textResult(text: string, details: TaskSnapshot) {
   return { content: [{ type: "text" as const, text }], details };
@@ -261,7 +113,9 @@ function hasUpdate(params: TaskUpdateParams): boolean {
     params.owner !== undefined ||
     params.metadata !== undefined ||
     (params.addBlocks?.length ?? 0) > 0 ||
-    (params.addBlockedBy?.length ?? 0) > 0
+    (params.addBlockedBy?.length ?? 0) > 0 ||
+    (params.removeBlocks?.length ?? 0) > 0 ||
+    (params.removeBlockedBy?.length ?? 0) > 0
   );
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@riverai7z/pi-todo",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Claude Code-style task list tools for Pi",
   "type": "module",
   "license": "MIT",