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

@garndev/wip

v0.6.5

Published

wip: per-project workflow state for Claude Code

Readme

wip

wip icon

Talk to one agent. It orchestrates a fleet of subagents that run a deterministic flow.

You talk to one agent — the coordinator. It orchestrates a fleet of subagents that run a deterministic flow: named phases, gates that stop for your decisions, and the subagent each phase runs. Every run, gate and artifact is recorded in the project, so you can audit the work and keep control without asking the model what happened.

Long work with an AI assistant has a memory problem: the plan lives in a chat, a new session starts from zero, and nobody can say which subagent is running or which decision waits on a human. wip keeps that state in .wip/.

The workflow is not fixed. You create the flows you want by talking to the coordinator: the phases in them, the instructions for each phase, and an agent for each one with the rules, the model and the write scope you choose. Flows and agents are Markdown files in the repository, so they are readable, diffable and yours to edit.

Why wip

  • One agent to talk to. It orchestrates the fleet of subagents and records what each run did.
  • Deterministic workflows. Phases, gates and write scopes are declared in Markdown, not improvised.
  • Yours to change. Create flows and agents by talking to the coordinator; their rules, model and write scope are yours.
  • The work survives the chat. A new session reads the same state and continues where the last one stopped.
  • You always know what is running and what waits on you. wip state and wip web show it without asking the model.
  • Decisions stop instead of guessing. A gate opens a question and waits for your answer.
  • It stays local. No network, no daemon, no dependencies: SQLite in the project, definitions in .claude/ or ~/.claude/.

What you get

  • Durable per-project state. Items, phases, runs, gates and history in .wip/, found by walking up from any directory.
  • Flows as Markdown. Phases, gates, agents and write scopes; wip init ships four flows — development, ideas, reports and tasks — covering code, research, documents and decisions.
  • One coordinator, four subagents. fast, efficient, thinker and wise share one contract and differ in how much they investigate and decide.
  • A read-only kanban. wip web serves it from the binary; wip init also installs an optional pane for Claude Code by default (the wizard's fifth step), and wip init --kanban installs it from scripts.
  • Scheduled checks without a daemon. Flows declare polls; wip cron keeps reminders and fixed-time passes, and the coordinator arms them when a session starts.
  • Auditable by default. Every item keeps its runs, gates and history; archiving prunes safely to the system trash, never a hard delete.

Status: published as @garndev/wip on the npm registry; the current version is at the top of the CHANGELOG.

Getting started

Requirements

Claude Code's claude CLI, Node 22.13 or later and npm; a standalone binary can be built from source (see docs/install.md).

1. Install

npm install -g @garndev/wip

2. Initialise the project

cd my-project
wip init

The wizard asks five things: the scope (local or ~/.claude/), the flows to write, the wip start command, what goes into .gitignore, and whether to install the Kanban mod for Claude Code. See docs/init.md.

3. Start the coordinator

wip start

Bare wip does the same in a terminal when the project is initialised and a start command is saved. See docs/start.md.

4. Ask for work

Write as you would to a colleague: «fix the failing login test», «investigate why the build is slow», «what is waiting on me?». The coordinator records the item, moves it through the flow and stops at the decisions that are yours.

5. See what is happening

wip state          # every item, its phase and what it waits on
wip web --open     # the read-only kanban in the browser
wip check          # invariants and warnings

Documentation

| Document | What it covers | | ------------------------------------------------------------------------------------------- | ------------------------------------------------- | | Install | npm, binary, upgrade, backup, rollback, uninstall | | Init | wip init, scopes, .gitignore, the Kanban mod | | Start | wip start, saved commands, WIP_BIN | | Agents and models | the four generics, levels, model: | | Flows | flow format, wip-flow, flow lint | | Commands | the command table, --json, exit codes | | Prune | wip prune, rules, trash, safety | | Web | wip web, ports, LAN, Docker, logs | | Polling | scheduled checks, states | | Cron | reminders and fixed-time passes | | Coordinating | session start, attention, kanban | | Releasing | the maintainer's release process | | CLAUDE.md | developing this repository |

License

MIT. See LICENSE.