pi-initiatives
Initiative and project tracker for pi — manage initiatives, todos, and PRs with a split-panel TUI and LLM-callable tools.
Package details
Install pi-initiatives from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:pi-initiatives- Package
pi-initiatives- Version
1.1.0- Published
- Apr 21, 2026
- Downloads
- 116/mo · 7/wk
- Author
- affsantos
- License
- MIT
- Types
- extension
- Size
- 155.8 KB
- Dependencies
- 0 dependencies · 4 peers
Pi manifest JSON
{
"extensions": [
"./extensions/initiatives"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
pi-initiatives
Initiative and project tracker for Pi — organize work as folders and markdown files, browse it in a fast split-panel TUI, and manage initiatives and todos through both commands and LLM-callable tools.
Why this package?
pi-initiatives gives Pi a lightweight, file-based system for tracking ongoing work:
- browse initiatives in a dedicated
/initiativesUI - create new initiatives with a guided wizard
- manage todos with stable IDs, WIP state, assignees, tags, and notes
- resume work quickly from the most relevant files
- keep everything in plain markdown on disk
No database, no SaaS backend, no lock-in — just folders, index.md, and todos.md.
Install
From npm
pi install npm:pi-initiatives
From GitHub
pi install git:github.com/affsantos/pi-initiatives
Quick Start
- Start Pi
- Run:
/initiatives
On first run, pi-initiatives will guide you through:
- choosing an initiatives root folder
- creating one or more team/department folders
- optionally creating your first initiative immediately
If you prefer to set things up manually, you can still do:
mkdir -p ~/Initiatives/"Engineering"
mkdir -p ~/Initiatives/"Product"
pi
Then inside Pi:
/initiatives
Features
- First-run onboarding — friendly setup flow for new users
- Split-panel TUI — browse initiatives on the left, see details, todos, and PRs on the right
- File-based storage — initiatives live as normal folders and markdown files
- Guided initiative creation — team, type, priority, DRI, stakeholders, description, tags
- Todo management — open → WIP → done states, assignees, tags, session claims, markdown bodies
- Stable todo IDs — operate on todos safely even when line numbers shift
- WIP freshness tracking — stale WIP detection after 24 hours
- Resume modes — quick resume for hot files, or full resume for all markdown files
- PR tracking — parsed from the
## Pull Requestssection inindex.md - Persistent widget — active initiative count, open todos, and current WIP in Pi’s status area
Commands
| Command | Description |
|---|---|
/initiatives |
Browse initiatives, create new ones, manage status, todos, PR links, and resume work |
/todos |
Quick access to todos for the active initiative |
Tools
| Tool | Description |
|---|---|
initiative_todo |
LLM-callable tool to list, add, start, toggle, update, claim, release, append, and delete todos, plus initiative status actions |
initiative_create |
LLM-callable tool to create a new initiative on disk |
How it stores data
Each initiative is a folder inside a top-level team/department folder:
~/Initiatives/
├── Engineering/
│ ├── Auth Revamp/
│ │ ├── index.md
│ │ └── todos.md
│ └── API v2/
│ ├── index.md
│ └── todos.md
└── Product/
└── Q2 Planning/
└── index.md
index.md
Holds the initiative metadata and overview, including fields like:
- type
- status
- team
- owner / DRI
- stakeholders
- priority
- tags
- summary / description
- optional pull requests section
todos.md
Stores markdown checkboxes with metadata:
- [ ] Open task @assignee #tag ~id:a1b2c3d4
- [~] In progress task ~id:e5f6a7b8 ~ts:2025-01-15T10:30
- [x] Completed task ~id:c9d0e1f2
Notes and details go here (indented)
Because everything is stored on disk, your initiatives and todos persist across Pi restarts and machine reboots.
Configuration
The initiatives root folder is resolved in this order:
pi-initiatives.dirin~/.pi/agent/settings.jsonPI_INITIATIVES_DIRenvironment variable- default:
~/Initiatives
Example settings.json:
{
"pi-initiatives": {
"dir": "~/my/initiatives"
}
}
Teams / departments
Top-level subdirectories under the initiatives root are treated as teams or departments. They are just an organizational layer.
Example:
~/Initiatives/
├── Engineering/
├── Product/
└── Data Platform/
Typical workflow
- Run
/initiatives - Create or select an initiative
- Add or claim todos
- Resume work with quick-resume or full-resume
- Update status as the work progresses
- Track PRs in
index.md
Publishing / sharing
If you publish this package to npm, others can install it with:
pi install npm:pi-initiatives
Or directly from GitHub:
pi install git:github.com/affsantos/pi-initiatives
License
MIT