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

@william9527/virtual-team

v0.2.2

Published

AI-driven virtual team framework — automate software development with PM and Coder agents powered by Claude CLI

Readme

@william9527/virtual-team

AI-driven virtual team framework — automate software development with PM and Coder agents powered by Claude CLI.

What is this?

Virtual Team is an orchestration framework that runs two AI agents in a loop:

  • PM (Project Manager) — reads a task list (GOALS.md), selects the next task, writes a detailed specification
  • Coder (Software Engineer) — reads the specification, implements the code, runs tests, and reports back

The loop continues automatically until all tasks are complete, with safety mechanisms for stuck detection, truncation recovery, and human intervention requests.

Prerequisites

  • Node.js >= 18
  • Git
  • Claude CLI (claude) installed and authenticated

Quick Start

# Install
npm install -g @william9527/virtual-team

# Initialise in your project
cd my-project
virtual-team init

# Define your tasks
vim .virtual-team/GOALS.md

# Start the development loop
virtual-team start

CLI Commands

virtual-team init [--force]

Creates the .virtual-team/ directory with:

  • prompts/pm.txt — PM system prompt
  • prompts/coder.txt — Coder system prompt
  • PLAYBOOK.md — Framework documentation
  • GOALS_TEMPLATE.md — Template for creating task lists
  • INTENT_SPEC_TEMPLATE.md — Template for task specifications
  • GOALS.md — Empty task list for you to fill in
  • config.json — Configuration file

virtual-team start [options]

Starts the PM ↔ Coder development loop.

| Option | Description | |--------|-------------| | --dry-run | Log actions without executing agents | | --max-cycles <n> | Limit PM→Coder cycles | | --sleep <seconds> | Override cooldown time (default: 600) | | --project <path> | Specify project root (default: cwd) |

virtual-team status

Shows current task progress (TODO / IN PROGRESS / DONE counts).

Configuration

Edit .virtual-team/config.json:

{
  "sleepTime": 600,
  "errorSleepTime": 300,
  "stuckLimit": 3,
  "pmMaxTurns": 45,
  "coderMaxTurns": 65,
  "pmModel": "sonnet"
}

| Key | Default | Description | |-----|---------|-------------| | sleepTime | 600 | Cooldown seconds between PM and Coder phases | | errorSleepTime | 300 | Retry wait after API errors | | stuckLimit | 3 | Consecutive no-change cycles before force exit | | pmMaxTurns | 45 | Max conversation turns for PM | | coderMaxTurns | 65 | Max conversation turns for Coder | | pmModel | "sonnet" | Model for PM agent |

Programmatic API

import { loadConfig, startLoop, initVirtualTeam } from '@william9527/virtual-team';

// Initialise
initVirtualTeam('/path/to/project');

// Run the loop
const config = loadConfig('/path/to/project');
const result = await startLoop(config, { maxCycles: 5 });
console.log(result.status); // 'all_done' | 'human_needed' | 'stuck' | 'max_cycles_reached'

Safety Mechanisms

| Mechanism | Description | |-----------|-------------| | Task completion detection | Loop ends when no [TODO] or [IN PROGRESS] in GOALS.md | | Truncation detection | Missing signal file → rollback and retry | | Stuck detection | N consecutive no-change cycles → force exit | | Human intervention | HUMAN_NEEDED.md pauses the loop | | API error tolerance | Retry with backoff on API/network errors |

GOALS.md Format

## Epic 1: Infrastructure

### Feature 1.1: Project Setup

- [ ] `[TODO]` Task 1.1.1: Initialise Node.js project
  - Goal: Set up package.json, TypeScript, and build tooling
  - Output: package.json, tsconfig.json, working `npm run build`

Task statuses: [TODO][IN PROGRESS][DONE]

License

MIT