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

@sulhadin/orchestrator

v2.0.0

Published

AI Team Orchestration System — multi-role coordination for Claude Code

Readme

Orchestra

AI team orchestration for Claude Code. Two terminals — PM plans, worker builds.

Install

npx @sulhadin/orchestrator@latest

Skip permission prompts:

npx @sulhadin/orchestrator@latest --dangerously-skip-permissions

Two Terminals

Terminal 1: #pm — Planning

PM is your strategic partner. Discuss ideas, challenge scope, create milestones. PM never writes code — only plans.

You: #pm
PM:  "No active milestones. Ready for instructions."

You: "I want user authentication with JWT"
PM:  *discusses, challenges, refines scope*

You: "Create the milestone"
PM:  *creates prd.md, grooming.md, milestone.md, phases/*
     "🎯 M1-user-auth ready. Run #start in another terminal."

You: "Let's also plan a dashboard"
PM:  *plans M2 while worker executes M1*

PM is always available. Plan ahead while work runs in the other terminal.

Terminal 2: #start — Execution

Worker picks up milestones and executes them autonomously. Loops to the next when done.

You: #start

📋 Starting M1-user-auth

🏗️ #architect ▶ RFC + grooming validation...
🏗️ #architect ✅ RFC ready
🚦 Approve RFC? → yes

⚙️ #backend ▶ phase-1: DB schema + migrations...
⚙️ #backend ✅ phase-1 done (feat(db): add auth tables)

⚙️ #backend ▶ phase-2: API endpoints + tests...
⚙️ #backend ✅ phase-2 done (feat(auth): add login endpoint)

🎨 #frontend ▶ phase-3: Login UI...
🎨 #frontend ✅ phase-3 done (feat(auth): add login page)

🔍 #reviewer ▶ reviewing unpushed commits...
🔍 #reviewer ✅ approved

🚦 Push to origin? → yes
✅ M1-user-auth done.

📋 Starting M2-dashboard...

Close the terminal, reopen, type #start — it resumes from where it left off.

Commands

| Command | Where | What it does | |---------|-------|-------------| | #pm | Terminal 1 | Plan features, create milestones | | #start | Terminal 2 | Execute milestones, asks at approval gates | | #start --auto | Terminal 2 | Confirms once, then fully autonomous | | #hotfix {desc} | Any | Ultra-fast fix: implement → verify → commit → push | | #status | Terminal 1 | Milestone status report | | #help | Any | Show all commands | | #help skills | Any | List available skills | | #help blueprints | Any | List available blueprints | | #blueprint {name} | Terminal 1 | Generate milestones from template | | #blueprint add | Terminal 1 | Save current work as reusable template |

Manual roles (any terminal):

| Command | Role | |---------|------| | #backend | Backend Engineer | | #frontend | Frontend Engineer | | #reviewer | Code Reviewer | | #architect | Architect | | #owner | System maintenance | | #adaptive | Adaptive expert (iOS, DevOps, ML, etc.) |

Documentation

See docs/ for full documentation:

  • Getting Started — installation, first milestone, two-terminal model
  • Commands — all commands with examples
  • Roles — 7 roles, responsibilities, boundaries
  • Features — verification gate, fast track, parallel, hotfix, and more
  • Blueprints — project templates, #blueprint add
  • Skills — domain checklists, creating new skills

License

MIT