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

chief-clancy

v0.9.48

Published

Autonomous, board-driven development for Claude Code

Readme

Clancy

Autonomous development for Claude Code — driven by your Kanban board, or by local plan files.

npm License: MIT

npx chief-clancy

[!WARNING] Clancy is in early development. Expect breaking changes and rough edges.

Clancy scaffolds slash commands, hooks, and board integrations into your Claude Code project. It picks up tickets from your Kanban board (Jira, GitHub Issues, Linear, Shortcut, Notion, or Azure DevOps), implements them autonomously, and creates pull requests. Also supports local plan execution via --from — no board needed.

How it works

With a board:

  1. Install: npx chief-clancy — choose global or local install
  2. Configure: /clancy:init — connect your board, enter credentials
  3. Scan: /clancy:map-codebase — 5 parallel agents document your codebase
  4. Run: /clancy:implement — pick up one ticket, implement, create PR
  5. Go AFK: /clancy:autopilot — loop through your backlog unattended

Without a board — local plan-driven flow:

  1. Install: npx chief-clancy
  2. Configure: /clancy:init — answer "No" when asked about a board. When prompted for optional roles, enable both Strategist and Planner — the local flow uses /clancy:brief and /clancy:plan, which only install when their roles are enabled.
  3. Scan: /clancy:map-codebase
  4. Draft: /clancy:brief --from outline.md/clancy:plan --from <brief>/clancy:approve-plan <plan> (writes a .approved marker file — a write-side contract; a future PR will wire a runtime gate that re-hashes the plan and refuses to run on mismatch)
  5. Run one plan: /clancy:implement --from .clancy/plans/<plan>.md
  6. Go AFK: /clancy:implement --from .clancy/plans/ --afk — batch-executes every plan in the directory that has a sibling .approved marker, naturally sorted. Unapproved plans are skipped with a warning. (Marker SHA-256 verification is deferred — only marker existence is currently checked.)

Packages

This is the CLI entry point for the Clancy monorepo. It delegates to:

Documentation

Credits

Built on the Ralph technique by Geoffrey Huntley. See CREDITS.md.

License

MIT — see LICENSE.