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

cforge

v0.4.3

Published

Claude Code workflow orchestration engine

Readme

Stack Forge

Claude Code workflow orchestration engine. Composes existing plugins into a unified development workflow.

What it does

Stack Forge discovers your installed Claude Code plugins (Superpowers, feature-dev, code-review, etc.) and generates an orchestration workflow that chains them together automatically. It includes health checks to ensure providers are working correctly before starting a workflow.

Quick Start

# Install
npm install -g cforge

# Initialize (zero-config)
cforge init

# Start a workflow
cforge                    # default: feature
cforge feature "add auth" # explicit
cforge bugfix "fix login" # explicit

How it works

  1. cforge init scans your system for installed plugins
  2. Auto-installs missing required providers
  3. Runs health checks to verify providers are working
  4. Generates an orchestration skill + stage skills
  5. cforge triggers the orchestration skill
  6. The skill forks subagents for each stage automatically
  7. Stages: Brainstorm → Spec → Plan → Build → Review → Release
  8. Implementation stage uses parallel execution for independent tasks

Parallel Implementation

The Implementation stage automatically detects independent tasks and executes them in parallel:

# tasks.md example
- [ ] Task 1: Modify src/discovery/scanner.ts
- [ ] Task 2: Modify src/generator/templates.ts
- [ ] Task 3: Modify src/cli/generate.ts
- [ ] Task 4: Modify src/discovery/scanner.ts (depends on Task 1)

Automatic batching:

  • Tasks 1, 2, 3 → Batch 1 (parallel, no file conflicts)
  • Task 4 → Batch 2 (serial, depends on Task 1)

Benefits:

  • 3x faster for independent tasks
  • Automatic conflict detection
  • Each task follows TDD workflow
  • Full test suite validation at end

Commands

| Command | Description | |---------|-------------| | cforge init | Initialize Stack Forge (zero-config) | | cforge [workflow] [desc] | Start or continue a workflow | | cforge status | Show current workflow status | | cforge healthcheck | Check health of installed providers | | cforge update | Re-scan providers and update configuration | | cforge generate | Regenerate all config files | | cforge validate | Validate implementation against spec requirements | | cforge reset | Reset Stack Forge to pre-initialization state |

Debug Mode

Set environment variable for verbose logging:

CFORGE_LOG_LEVEL=debug cforge <command>

Supported Providers

| Capability | Default Provider | |------------|-----------------| | Brainstorm | Superpowers | | Specification | feature-dev | | Planning | Superpowers | | Implementation | Built-in | | Review | code-review | | Release | gstack | | Memory | claude-mem |

Architecture

cforge CLI
  ├── Provider Discovery (scan plugins)
  ├── Health Check (verify providers)
  ├── Config Generator (skills, commands, CLAUDE.md)
  ├── Schema Validation (Zod)
  └── State Management (state.json with backup)

Claude Code Runtime
  ├── Orchestration Skill (state machine + fork)
  │   └── Stage Skills (context: fork isolation)
  └── Provider Delegation
      ├── Superpowers (brainstorm, planning)
      ├── feature-dev (specification)
      ├── code-review (review)
      └── gstack (release)

License

MIT