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

splitflowai

v0.1.2

Published

MCP server for smart session management. Breaks features into tickets and runs each in a fresh Claude Code session.

Downloads

334

Readme

Splitflow

MCP server that gives Claude Code the ability to break features into tickets and run each in a fresh background session. Your session becomes a control panel.

The Problem

When you ask Claude Code to build a big feature, everything happens in one session. Context accumulates, quality drops by subtask 6-7, and you don't know why.

The Solution

Splitflow breaks your feature into tickets and runs each in a separate Claude Code session with fresh context. You stay in control — skip tickets, give feedback, pause/resume — without leaving your terminal.

Install

npx splitflowai setup

That's it. One command. Auto-detects your agents (Claude Code, Codex) and registers Splitflow with all of them.

Usage

Just talk to Claude Code normally:

You: add a payment system with stripe — checkout, webhooks, email receipts

Claude automatically uses Splitflow to:

  1. Break it into focused tickets
  2. Run each in a fresh background session
  3. Report progress as tickets complete
  4. Auto-commit each ticket's work

Check progress

You: how's it going?

Give feedback

You: for the checkout page, use shadcn components

Skip, add, or reorder

You: skip the email receipts ticket, I'll do that myself

Next day

You: what did I work on yesterday?

MCP Tools

| Tool | What it does | |------|-------------| | plan_feature | Break a feature into ordered tickets using AI | | execute_plan | Run tickets in fresh background Claude Code sessions | | get_status | Check progress — which ticket is running, what's done | | add_ticket | Add a new ticket to an existing plan | | skip_ticket | Skip a ticket | | apply_feedback | Apply changes to a completed or pending ticket | | get_history | See all features worked on in this project | | pause_execution | Pause after the current ticket finishes | | resume_execution | Resume from the next pending ticket |

How It Works

┌─────────────────────────────────┐
│  Your Claude Code session       │
│  (lightweight control panel)    │
└──────────────┬──────────────────┘
               │ MCP
               ▼
┌─────────────────────────────────┐
│  Splitflow MCP Server           │
│  Plans → Executes → Tracks      │
└──────────────┬──────────────────┘
               │ Spawns
               ▼
┌──────────┐ ┌──────────┐ ┌──────────┐
│ Ticket 1 │ │ Ticket 2 │ │ Ticket 3 │
│ Fresh ctx│ │ Fresh ctx│ │ Fresh ctx│
└──────────┘ └──────────┘ └──────────┘

Each ticket runs in an independent claude -p session with only the context it needs.

Requirements

  • Claude Code CLI installed
  • ANTHROPIC_API_KEY set (for ticket planning)
  • Node.js >= 18

License

MIT