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

@ydax/prac-kit

v1.1.5

Published

Product Requirements as Code — an open-source toolkit that turns your GitHub repository into a self-managing autonomous development system

Readme

PRaC Kit

License npm version Node.js

Product Requirements as Code — An open-source toolkit that turns your GitHub repository into a self-managing autonomous development system.

PRaC Kit gives any repository a closed-loop pipeline: you write a user Story in markdown, an AI generates the implementation contract (Blueprint), another AI writes tests-first code, and a third AI reviews and merges the PR — all triggered by a git push.

How It Works

Human writes Story → Orchestrator generates Blueprint PR → Jules writes tests →
Jules implements → Automated Reviewer merges or sends feedback → Next task triggers

The system is built on three invariants:

  1. Blueprint is the contract. No code is written without a BLUEPRINT.md entry.
  2. Tests before code. Agents write failing tests first (Test-Driven Autonomy).
  3. Docs as code. Requirements live entirely in the repository, not in external tools.

Quick Start

# Initialize PRaC in your repository
npx prac-kit init

# Configure your repo-specific values interactively
npx prac-kit config

# Create your first epic
npx prac-kit epic create my-feature

# Validate your setup
npx prac-kit doctor

What Gets Installed

your-repo/
├── prac.config.js                    ← repo-specific configuration
├── scripts/
│   ├── shared.js                     ← shared utilities (config-driven)
│   ├── orchestrate-story.js          ← Story → Blueprint translation via Gemini
│   ├── review-pr.js                  ← LLM-powered automated PR reviewer
│   ├── trigger-jules.js              ← Jules REST API trigger
│   ├── kickoff-sprint.js             ← priority cascade kickoff
│   ├── on-blueprint-merge.js         ← post-merge Linear issue creation
│   └── create-linear-cascade.js      ← batch Linear issue creation
├── .github/workflows/
│   ├── orchestrator.yml              ← detects Story changes on push
│   ├── reviewer.yml                  ← reviews Jules PRs automatically
│   ├── blueprint-merged.yml          ← triggers Jules after Blueprint merge
│   └── nightly.yml                   ← nightly test suite with self-healing
└── epics/
    └── STORY_TEMPLATE.md             ← template for new user stories

Commands

| Command | Description | |---------|-------------| | prac init | Initialize PRaC in the current repository | | prac config | Interactive walkthrough to set up prac.config.js | | prac update | Update scripts and workflows to latest version | | prac epic create <name> | Scaffold a new epic directory | | prac doctor | Validate configuration and report drift |

Configuration

All repo-specific values live in prac.config.js:

module.exports = {
  repo: 'your-org/your-repo',
  linearTeamKey: 'YOUR',
  linearTeamId: 'uuid-from-linear',
  projectName: 'Your Project',
  orchestratorModel: 'gemini-3-pro-preview',
  reviewerModel: 'gemini-3-flash-preview',
  autoMergeBlueprints: true,
  maxReviewerRevisions: 3,
  cascadeEnabled: true,
  // ... see prac.config.example.js for all options
};

Requirements

  • Node.js 20+
  • GitHub CLI (gh) authenticated
  • API keys in .env and GitHub repository secrets:

Documentation

Contributing

We welcome contributions! Please read our Contributing Guide and Code of Conduct before submitting a pull request.

Security

To report a security vulnerability, please see our Security Policy.

License

Copyright 2026 YDAX, Inc.

Licensed under the Apache License, Version 2.0. See LICENSE for the full text.