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

feature-lifecycle

v1.1.1

Published

File-based Feature Lifecycle Tracker — unified status with QA integration, traceable PR creation, and post-merge lifecycle resolution

Readme

feature-lifecycle

File-based Feature Lifecycle Tracker — unified status by aggregating BMAD, SpecKit, Agreement, ADR, and Mermaid artifacts.

Installation

Via tcsetup (recommended)

npx tcsetup install

Standalone

npx feature-lifecycle init

Options

| Flag | Description | |------|-------------| | --yes | Skip confirmation prompts | | --skip-bmad | Skip BMAD agent integration |

CLI Usage

npx feature-lifecycle init      # Install in current project
npx feature-lifecycle update    # Update commands/templates only
npx feature-lifecycle help      # Show usage

Claude Code Commands

After init, these commands are available in Claude Code:

| Command | Purpose | |---------|---------| | /feature.status <id> | Detailed status of one feature | | /feature.list | Dashboard of all features | | /feature.graph | Dependency visualization (Mermaid) | | /feature.discover | Auto-register existing features |

How It Works

  1. init scaffolds a .features/ directory with config, templates, and index
  2. /feature.status scans 5 artifact sources (BMAD, SpecKit, Agreement, ADR, Mermaid) and computes lifecycle stage + health
  3. /feature.list aggregates all features into a dashboard table
  4. /feature.graph generates a Mermaid dependency graph with status colors
  5. /feature.discover scans specs/, .agreements/, and mermaid directories to auto-register existing features

Lifecycle Stages

ideationspecplantasksimplementtestrelease

Stages are automatically computed from artifact presence. Edit .features/config.yaml to customize rules.

Directory Structure

.features/
├── config.yaml              # Project configuration
├── index.yaml               # Global registry of all features
├── lifecycle.md             # Documentation
├── _templates/
│   └── feature.tpl.yaml    # Template for new features
├── _output/                 # Generated JSON output
│   ├── dashboard.json
│   └── {feature_id}.json
└── {feature_id}/
    └── feature.yaml         # Per-feature manifest

Requirements

  • Node.js >= 18.0.0
  • Zero runtime dependencies