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

pi-feature-dev

v1.4.0

Published

Portable coding-agent workflows packaged as skills.

Readme

pi-feature-dev

Portable coding-agent workflows, packaged as Pi skills.

The feature-dev skill describes a tool-agnostic process for non-trivial feature work:

  • clarify requirements before coding
  • explore the existing codebase before design
  • compare implementation approaches and get approval
  • implement with one writer
  • review the diff from multiple perspectives
  • validate and summarize results

It does not require specific task-tracking, question, delegation, or review tools. If the current environment provides equivalent capabilities, use them; otherwise follow the same workflow directly in chat and with normal code tools.

The plan-exec skill executes implementation plan files task by task with isolated workers, Git task commits, internal reviews, finalize, and a portable run summary. It is portable across host agents that provide fresh-context isolated workers and Git access.

Install

npx skills add https://github.com/r13v/pi-feature-dev

From npm:

pi install npm:pi-feature-dev

From this local repo:

pi install ~/Projects/pi-feature-dev

Or for one run only:

pi -e ~/Projects/pi-feature-dev

If installing for a project, run from that project and use Pi's local install flag if desired:

pi install -l ~/Projects/pi-feature-dev

Optional companion packages

No companion package is required. Optional Pi packages can improve specific parts of the workflow, such as progress tracking, structured choices, delegation, large-output handling, web/code research, or session coordination.

Credits

The original Claude Code skills and workflows that informed these portable versions came from:

Usage

Skill command in Pi:

/skill:feature-dev Add OAuth login with Google and GitHub

Natural language also works when Pi's skill matcher triggers:

Use feature-dev to implement API rate limiting.

The skills/feature-dev/SKILL.md file is portable markdown and can be adapted for other coding assistant environments.

Run a plan with plan-exec:

/skill:plan-exec docs/plans/20260518-example.md

This package is intentionally skill-only. It does not provide prompt template shortcuts; use /skill:<name> for explicit Pi invocation.

Feature-dev workflow

The feature-dev skill guides a coding assistant through a seven-phase process:

  1. Discovery — understand the feature and establish lightweight progress tracking
  2. Codebase exploration — inspect relevant code and patterns, optionally with read-only helper passes
  3. Clarifying questions — resolve ambiguity before design
  4. Architecture design — compare minimal, clean, and pragmatic approaches
  5. Implementation — only after approval, with a single writer
  6. Quality review — inspect the diff from correctness, validation, and maintainability perspectives
  7. Validation and summary — run focused checks and summarize changes

Package contents

pi-feature-dev/
├── package.json
└── skills/
    ├── feature-dev/
    │   └── SKILL.md
    ├── plan-exec/
    │   ├── SKILL.md
    │   ├── references/
    │   └── scripts/
    ├── plan-make/
    │   └── SKILL.md
    └── plan-review/
        └── SKILL.md

Release

Releases are automated with GitHub Actions and semantic-release.

  • Push conventional commits to main.
  • With no existing v* tags, the first release will be v1.0.0.
  • After that, semantic-release calculates the next version from commit messages.
  • The workflow publishes to npm using NPM_TOKEN.
  • GitHub release notes and git tags are created automatically.

Examples:

fix: clarify approval rules
feat: add review synthesis guidance
feat!: redesign workflow phases

Development

Validate the package shape:

npm test

Then test in Pi without installing globally:

pi -e ~/Projects/pi-feature-dev