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

work-kit-cli

v0.5.0

Published

Structured development workflow for Claude Code. Two modes, 7 phases, 31 steps, plus debug recovery.

Readme

work-kit

Structured development workflow for Claude Code. Two modes, 7 phases, 31 steps, plus auto-debug recovery — orchestrated by a TypeScript CLI with reusable skill files.

What's new in v0.5

  • Define phase runs before Plan to refine vague asks into a concrete spec (auto-skipped for bug fixes/refactors).
  • wk-debug triage skill auto-fires when any step reports needs_debug, then the originating step retries (max 2 iterations). Not user-invocable — fires from inside the pipeline.
  • test/browser drives the running app via Chrome DevTools MCP and verifies user-facing acceptance criteria in a real browser. Skips gracefully if the MCP isn't installed.
  • decision knowledge type auto-graduates ## Decisions bullets into .work-kit-knowledge/decisions.md so future sessions don't re-litigate settled choices.

Installation

One-step setup (recommended):

npx work-kit-cli setup

This auto-detects Claude Code projects in your workspace and installs the skill files. If multiple projects are found, it lists them for you to choose.

Global install:

npm install -g work-kit-cli

Quick start

# 1. Set up work-kit in your project
npx work-kit-cli setup

# 2. In Claude Code, start a workflow
/full-kit add user avatar upload    # strict, all phases
/auto-kit fix login redirect bug    # dynamic, only needed stages

Modes

/full-kit <description>

Runs every phase and step in strict order. No shortcuts.

Best for: large features, new systems, maximum rigor.

/auto-kit <description>

Classifies the request (bug-fix, small-change, refactor, feature, large-feature) and builds a dynamic workflow with only the steps needed.

Best for: bug fixes, small changes, refactors, well-understood tasks.

CLI commands

| Command | Description | |---------|-------------| | init <description> | Initialize a new workflow with a task description | | next | Advance to the next step | | complete | Mark the current step as complete | | status | Show current workflow state (phase, step, progress) | | context | Generate context summary for the current phase | | validate | Validate state integrity and phase prerequisites | | loopback | Route back to a previous stage (max 2 per route) | | workflow | Display the full workflow plan | | pause | Pause the active session (state preserved on disk) | | resume [--slug <slug>] | Without --slug: list resumable sessions in this repo. With --slug: resume the named session | | observe [--all] | Live TUI dashboard of active/paused/completed sessions. --all watches every work-kit project on the system | | doctor | Run environment health checks (supports --json) | | setup | Install work-kit skills into a Claude Code project |

Picking up where you left off

work-kit resume (or /resume-kit in Claude Code) scans every worktree of the current repo for .work-kit/tracker.json files in paused or in-progress state and lets you pick one. It works from the main repo root — no need to cd into a worktree first. In-progress sessions are listed too, so a terminal you closed without pausing can be recovered: just look for the row with a stale lastUpdatedAgoMs.

Watching multiple projects

work-kit observe --all discovers every work-kit-enabled repo from your ~/.claude/projects/ history and watches them all in one dashboard. Each row shows the project name, work item slug, mode, type, current state, and worktree.

Phases

| Phase | Steps | Agent | |-------|-----------|-------| | Plan | Clarify, Investigate, Sketch, Scope, UX Flow, Architecture, Blueprint, Audit | Single | | Build | Setup, Migration, Red, Core, UI, Refactor, Integration, Commit | Single | | Test | Verify, E2E, Validate | Verify + E2E parallel, then Validate | | Review | Self-Review, Security, Performance, Compliance, Handoff | 4 parallel reviewers, then Handoff | | Deploy | Merge, Monitor, Remediate | Single (optional) | | Wrap-up | Summary + Archive | Single |

Architecture

Context management

Each phase runs as a fresh agent. The Build agent doesn't carry Plan's investigation notes — no context bloat.

Phases communicate through Final sections in .work-kit/state.md. Each phase writes a ### <Phase>: Final section that the next phase reads.

State management

Dual state files in .work-kit/:

  • tracker.json — state machine (current phase, step, transitions, loop-back counts)
  • state.md — content (working notes, Final sections, accumulated context)

All writes are atomic to prevent state corruption.

Parallel agents

  • Test phase: Verify and E2E run in parallel, then Validate runs sequentially
  • Review phase: Self-Review, Security, Performance, and Compliance run as 4 parallel reviewers, then Handoff runs sequentially

Loop-back routing

Any stage can route back to a previous stage. Each route is enforced with a max count of 2 to prevent infinite loops.

Validation

  • full-kit: phase-level prerequisites (Plan before Build before Test...)
  • auto-kit: step-level validation against the ## Workflow checklist
  • Both modes refuse to skip ahead

Output

.work-kit-tracker/
  index.md                              # log of all completed work (links to summaries + archives)
  archive/
    avatar-upload-2026-04-03/
      state.md                          # full phase outputs
      tracker.json                      # full JSON tracker (phases, timing, status)
      summary.md                        # distilled wrap-up summary

Repo structure

work-kit/
  cli/
    src/
      commands/       # CLI command implementations
      config/         # Configuration and defaults
      context/        # Context generation for phases
      engine/         # Workflow engine and transitions
      state/          # State machine and file management
      index.ts        # Entry point
  skills/
    full-kit/SKILL.md   # /full-kit orchestrator
    auto-kit/SKILL.md   # /auto-kit orchestrator
    plan/SKILL.md       # Plan phase runner
    plan/steps/        # 8 step files
    build/SKILL.md      # Build phase runner
    build/steps/       # 8 step files
    test/SKILL.md       # Test phase runner
    test/steps/        # 3 step files
    review/SKILL.md     # Review phase runner
    review/steps/      # 5 step files
    deploy/SKILL.md     # Deploy phase runner
    deploy/steps/      # 3 step files
    wrap-up/SKILL.md    # Final summary + cleanup
  package.json

Requirements