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

jpm-cli

v1.0.3

Published

Jatrick Project Manager (JPM) - Spec-Driven Development CLI for AI Agents

Readme

JPM-CLI: Just Project Manager

Node.js Version License: MIT PRs Welcome

Đọc bằng tiếng Việt 🇻🇳

JPM (Jatrick Project Manager) is a Spec-Driven Development CLI designed to streamline the workflow of AI Agents and Human Developers. It enforces a strict "Plan → Design → Split → Sync" methodology to ensure code quality and project consistency.


🌟 Why JPM?

  • 🧠 Spec-Driven: No more coding without a plan. PRD and Architecture artifacts are mandatory.
  • ⚡ AI-Powered: Uses Google Gemini to generate high-quality specs and task breakdowns.
  • 🤝 GitHub Sync: Decomposes big features into "Parent Issues" with trackable Tasklists.
  • 🛡️ Master Rule Enforcement: Enforces your project's JPM_MASTER.md rules (Tech Stack, Naming, Design) on every AI generation.

📦 Installation

Install globally via NPM:

npm install -g jpm-cli

Configuration (Important!)

JPM requires a Google Gemini API Key. You can set this up easily:

  1. Run the config command:
    jpm config
    (This opens the global installation directory)
  2. Create or duplicate .env file in that folder.
  3. Add your key:
    JPM_API_KEY=your_gemini_api_key_here

🚀 Zero to Hero Workflow

1. Initialize a Project

Go to your project folder and wake up JPM.

mkdir my-super-app
cd my-super-app
jpm init

Creates .jpm/ structure and JPM_MASTER.md. Edit JPM_MASTER.md to define your stack!

2. Plan a Feature (The "What")

Generate a Product Requirement Document (PRD).

jpm plan "User Authentication"

3. Design the System (The "How")

Create a technical architecture based on the PRD.

jpm design "User Authentication"

4. Split into Tasks (The "Steps")

Break the architecture down into atomic, developer-ready tasks.

jpm split "User Authentication"

5. Sync to GitHub (The "Management")

Push your tasks to GitHub Issues (requires gh CLI).

jpm sync

🧹 Maintenance

Clean up cache and backups to save space:

jpm clean

🛠️ Tech Stack

  • Runtime: Node.js
  • Language: TypeScript
  • AI: Google Gemini (via @google/generative-ai)
  • CLI Tools: inquirer, ora, boxen, commander

👨‍💻 Development

If you want to contribute to JPM or modify it locally:

  1. Clone & Install:

    git clone https://github.com/Jpatrick-Phan/JPM.git
    cd JPM
    npm install
  2. Linting & Formatting: We use ESLint and Prettier. Run this before committing:

    npm run lint      # Check for issues
    npm run lint -- --fix # Auto-fix issues
  3. Testing: Run the test suite (Core + CLI Integration):

    npm test
  4. Local Build:

    npm run build
    # Test your local build:
    node dist/src/index.js -h

Made with ❤️ by Jatrick