@yishan-io/pi-task
Pi tools and workflow skills for SQLite-backed Local Tasks.
Package details
Install @yishan-io/pi-task from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:@yishan-io/pi-task- Package
@yishan-io/pi-task- Version
0.3.5- Published
- Sep 3, 2026
- Downloads
- 988/mo · 89/wk
- Author
- zhex
- License
- MIT
- Types
- extension, skill
- Size
- 66.5 KB
- Dependencies
- 0 dependencies · 3 peers
Pi manifest JSON
{
"extensions": [
"./extensions"
],
"skills": [
"./skills"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
@yishan-io/pi-task
Pi tools and workflow skills for Local Tasks.
Authority and runtime
The SQLite-backed Local Task daemon owns task metadata and status. Pi connects to the managed daemon through YISHAN_DAEMON_WS_URL. The package requires Node.js 22.4 or later.
The daemon generates UUIDs for new tasks. Imported task IDs remain opaque. Do not create, parse, or replace task IDs.
Local Task lifecycle states are new, progressing, done, and cancelled. New tasks start as new.
The package uses YISHAN_PROJECT_ID when it is set. Operations then use only that project. Without this value, new tasks are global. Lists and searches show only global tasks.
Tools
The package registers exactly these nine tools:
task_startcreates a new task with a title, description or goal and acceptance criteria, priority, tags, and an optional workspace association.task_listlists tasks by status, priority, workspace, and tags.task_searchsearches tasks with the same filters.task_readreads the synthetic, read-only task brief or a context document.task_updatechanges a title, description, new, progressing, or cancelled status, priority, or tags. It cannot set done.task_writereplaces theplan,notes, oroutcomecontext document.task_append_noteadds text tonotes.task_finishwrites the outcome and marks a task done.task_template_readreads the Agent default task description template structure.
The synthetic brief shows daemon metadata. It is not a writable context document. The daemon provides paths for plan, notes, and outcome.
Markdown conventions
For multi-step work, create tasks with an outcome-focused title, a concise goal, relevant context/background, and independently checkable acceptance criteria. Include context only when it explains why the work matters, records a binding decision, or states a constraint; keep changing research and implementation detail in notes.md, not in task metadata.
Use this editable notes structure by default:
# Notes
## Summary
## Decisions
## Evidence and Progress
- YYYY-MM-DD — <fact, result, or change>
## Open Questions
Agents may append dated facts or replace the document to reorganize it. Users can edit the Markdown context documents directly.
Use task_finish only when the user explicitly asks to complete the task. When the user explicitly says all work is complete, run self-checks and finish without asking again.
Development
bun run --cwd packages/pi-task typecheck
bun run --cwd packages/pi-task lint
bun run --cwd packages/pi-task test
cd packages/pi-task && npm pack --dry-run