npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@howaboua/pi-todomaster

v0.1.0

Published

TodoMaster extension for Pi

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

howabouahowaboua

Keywords

pipi-coding-agentpi-extensionpi-packageplanningtodo

Readme

pi-todomaster

pi-todomaster adds a checklist-first planning system to Pi.

It provides an interactive /todo UI for managing three document types:

  • PRDs
  • specs
  • todos

What you can do

  • create PRD/spec/todo plan files under .pi/plans
  • open focused list views for tasks, PRDs, specs, and closed items
  • run work/refine/review flows from the action menu
  • attach and validate bidirectional links between related plan files
  • edit todo checklists directly from the UI
  • claim/release assignment per session
  • use a standardized SDK-based TUI shell shared across extensions
  • mark items as ralph-loop or ralph-loop-linked and stage a canonical loop command from the action menu

Checklist and status model

For todo items, checklists are the primary progress signal:

  • todos MUST include a non-empty checklist on create
  • checking items updates progress deterministically
  • status is derived from checklist completion for checklist-based work

Keyboard workflow highlights

  • list views:
    • j/k or arrows to move
    • Enter to open actions
    • / to search
    • Ctrl+X to open More options (auto-timeout)
    • Tab / Shift+Tab cycle list panes
  • detail/actions:
    • j/k move through actions
    • v toggles attached detail preview
    • preview uses J/K for scrolling
    • Esc returns back
  • create/edit inputs:
    • Enter submits
    • Shift+Enter, Ctrl+Enter, or Alt+Enter inserts new lines

Storage

Plan files are stored in:

  • .pi/plans/prds
  • .pi/plans/specs
  • .pi/plans/todos

Each item is markdown with frontmatter and uses type (prd, spec, todo) for classification.

Install

pi install npm:@howaboua/pi-todomaster

Local package development:

npm install
npm run build

Publish on npm

This package is configured for public npm publishing and Pi registry discovery:

  • keywords include pi-package and pi-extension
  • publishConfig.access is set to public
  • the published tarball includes the source extension entrypoint plus the built Node CLI helper under dist/

Useful commands:

npm run publish:dry-run
npm run publish:dev
npm run release:dev

Typical release flow:

npm login
npm run publish:dry-run
npm publish