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

@cliangdev/conductor

v0.2.3

Published

Agentic software development platform — AI-driven PRD, implementation, and beyond

Readme

Conductor

Agentic software development — from idea to launch, with AI and humans in the loop.

npm

What is Conductor?

Conductor is an agentic software development platform that manages the entire software development lifecycle using AI agents and human collaboration. You bring the intent; agents handle the execution.

Today, Conductor covers product requirements (PRD), team review, and AI-driven implementation. The roadmap extends across the full SDLC — testing, deployment, monitoring, and incident response — every phase driven by agents, with humans in the loop at the moments that matter.

The platform is built around Claude Code. You write PRDs with AI, your team reviews and approves them, then Claude implements them — opening PRs, running tests, and tracking progress — all coordinated through Conductor.

How it works

1. Write a PRD     →   /conductor:prd in Claude Code
2. Team reviews    →   Conductor web app — comment, approve, request changes
3. Implement       →   /conductor:implement in Claude Code
4. PR opens        →   Claude commits, pushes, and creates the pull request
5. Fix & iterate   →   /conductor:fix — address review feedback on the open PR
6. Merge           →   Issue closes automatically

Agents do the execution. Humans set the intent and sign off.

Quick Start

# Install
npm install -g @cliangdev/conductor

# Authenticate (opens browser for Google sign-in)
conductor login

# Connect to a project and configure Claude Code integration
conductor init

# Start the background sync daemon
conductor start

Then open Claude Code in your project and run /conductor:prd to create your first PRD.

Claude Code Commands

| Command | What it does | |---------|-------------| | /conductor:prd | Guides you through writing a PRD with AI — discovery, research, structured output | | /conductor:implement | Takes an approved PRD and implements it — task breakdown, parallel subagents, PR creation | | /conductor:fix | Fixes bugs and review feedback on an open PR — structured intake, investigation, build validation, and push |

These commands are installed automatically when you run conductor init (project-level) or during global install (user-level, to ~/.claude/).

CLI Commands

| Command | Description | |---------|-------------| | conductor login | Authenticate via browser (Google OAuth) | | conductor logout | Clear stored credentials | | conductor init | Connect to a project and set up Claude Code MCP integration | | conductor start | Start the background sync daemon | | conductor stop | Stop the sync daemon | | conductor status | Show daemon status and sync queue | | conductor doctor | Check config, API connectivity, and Claude Code integration | | conductor config show | Print current config (API key redacted) | | conductor config set-url <url> | Hot-swap API URL without re-auth | | conductor dashboard | Live terminal view of daemon, sync queue, and active workflow runs |

MCP Tools

Once conductor init runs, Claude Code gets access to these tools via the Conductor MCP server:

| Tool | Description | |------|-------------| | create_issue | Create a new PRD or task | | list_issues | List issues with optional filters | | get_issue | Fetch a single issue with its document | | update_issue | Update title or description | | set_issue_status | Advance issue through the workflow | | scaffold_document | Create a new document attached to an issue | | delete_document | Remove a document | | list_issue_comments | Fetch reviewer comments on an issue |

Links


For Contributors & Local Development

Local dev setup

The local stack runs at http://localhost:8080 (backend) and http://localhost:3000 (frontend) with email/password auth — no Firebase required.

# First-time login against local stack
CONDUCTOR_API_URL=http://localhost:8080 conductor login --local
# Default credentials: [email protected] / conductor

# Verify
conductor config show
conductor doctor

Switching between local and prod:

conductor config set-url http://localhost:8080   # local
conductor config set-url <prod-url>              # prod

Build from source

cd conductor-tools
npm install
npm run build
npm link          # makes `conductor` available globally

Configuration

~/.conductor/config.json:

{
  "apiUrl": "https://...",
  "apiKey": "...",
  "email": "[email protected]",
  "projectId": "...",
  "localPath": "/path/to/project"
}

Override the API URL: CONDUCTOR_API_URL=http://localhost:8080 conductor login --local

Testing

See TESTING.md for the end-to-end test procedure for CLI and MCP against prod.