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

@blackbelt-technology/pi-dashboard-eng-disciplines

v0.5.6

Published

Cross-cutting engineering-discipline skills for pi sessions — interview-me, doubt-driven-review, code-simplification, security-hardening, performance-optimization, observability-instrumentation, systematic-debugging, node-inspect-debugger. Orthogonal to t

Readme

@blackbelt-technology/pi-dashboard-eng-disciplines

Cross-cutting engineering-discipline skills for pi sessions. These are orthogonal to the openspec pipeline — they slot into any stage without competing for its triggers. Adapted from Addy Osmani's agent-skills and NousResearch's hermes-agent (both MIT; see NOTICE).

Why this package exists

The repo's openspec skills (openspec-explore, openspec-new-change, openspec-apply-change, code-review, ship-change, …) already own the DEFINE→PLAN→BUILD→VERIFY→REVIEW→SHIP lifecycle — and that pipeline is a shipped product (bundled into the Electron app). Importing a second lifecycle pack verbatim would put two workflows in a trigger-fight and degrade a user-facing surface.

So this package deliberately ships only the disciplines openspec does not cover, with every description retargeted so it never fires on spec / plan / build / ship / review verbs.

Skills

| Skill | Fills the gap | Fires on (not openspec verbs) | |-------|---------------|-------------------------------| | interview-me | pre-spec intent extraction, upstream of openspec-explore | "interview me", "grill me", underspecified ask | | doubt-driven-review | in-flight adversarial check (≠ post-hoc code-review) | "stress-test this", "verify before commit", "are we sure" | | code-simplification | active simplify pass (vs the passive simplicity-first rule) | "simplify this", "reduce complexity", "clean up" | | security-hardening | security discipline (no prior equiv) | "security audit", "harden", "threat model" | | performance-optimization | measure-first perf (no prior equiv) | "it's slow", "profile", "optimize perf" | | observability-instrumentation | runtime visibility (no prior equiv) | "add metrics/tracing/logging", "instrument" | | systematic-debugging | post-failure root-cause discipline (no prior equiv) | "root cause this", "why is this failing", "debug systematically" | | node-inspect-debugger | runtime state a console.log can't reach; jiti-verified breakpoints | "set a breakpoint", "inspect runtime state", "console.log isn't enough" |

Deliberately excluded

Everything in Addy's pack that overlaps the shipped openspec pipeline or existing project skills: spec-driven-development, planning-and-task-breakdown, idea-refine, incremental-implementation, frontend-ui-engineering, code-review-and-quality, shipping-and-launch, browser-testing-with-devtools, ci-cd-and-automation, git-workflow-and-versioning, etc.

Scope

Dev-only. This package is not bundled into the Electron app's bundled-extensions (unlike the openspec skills). It loads in working-tree pi sessions via the pi.skills manifest entries. Promoting any of these to a shipped surface is a separate, explicit decision.

How loading works

pi auto-discovers each .pi/skills/<name>/SKILL.md listed under pi.skills in package.json. Skills load by natural-language trigger from their frontmatter description — no manual invocation.

Attribution

Most skill bodies are reproduced under MIT from Addy Osmani's agent-skills, with only the frontmatter name/description (trigger routing) modified. The systematic-debugging and node-inspect-debugger skills are ported under MIT from NousResearch's hermes-agent and adapted to this repo's jiti-based TypeScript stack (the emitted-JS pitfall is corrected, and cdp-inspect.ts is a dependency-free TypeScript rewrite of the upstream CDP scope-walker). Full attribution and license in NOTICE.