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

readyset-flow

v0.11.1

Published

Readyset — a standalone omp extension, invoked as /readyset, that fuses /plan's grounding discipline, a structured grill/propose/review/apply workflow, and mattpocock/skills prompting hygiene into its own independent command, with no runtime dependency on

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

frespfresp

Keywords

ompoh-my-pibrainstormspec-driven-development

Readme

Readyset is a standalone omp extension, invoked as /readyset. It turns a rough idea into a grounded, reviewable, executable change — with a code-enforced review gate between "written" and "executing", not just a prompt asking nicely.

Rough idea → GRILL → EXPLORE → PROPOSE → REVIEW → EXECUTE → ARCHIVE

Install

npm install --save-dev readyset-flow
npx readyset-flow install

Installs globally, tied to ~/.omp/ — available in every repo you work in. Run npx readyset-flow configure afterward to set a default language or model (optional), or npx readyset-flow uninstall to remove it later.

Use

/readyset --idea "let users export their data as CSV"
  • Grill interrogates the idea until it's unambiguous — a real Q&A, not a rubber stamp.
  • Explore greps the actual repo before anything gets proposed, instead of assuming.
  • Propose writes a proposal, design, specs, and tasks — grounded in what Explore found.
  • Review stops for your Approve / Refine / Discard. Nothing executes without a look.
  • Execute implements the tasks; each one needs a _Verified: note, and a fresh-context code review runs before the change is archived.

Already have a brainstorm sitting in .ai/brainstorms/? Run /readyset with no --idea and pick it — Grill is skipped, since the ambiguity's already resolved.

Why

Plans drift from the repo, reviews get skipped under pressure, and "done" ends up meaning "the model said so." Readyset turns each of those into a structural gate instead of a habit: ambiguity gets interrogated before anything is written, every claim about the repo is grounded in a dedicated explore phase, nothing executes without an explicit human approve, and "done" needs verification, not just a claim.

Learn more

  • Full guide — design philosophy, configuration, model/language settings, the review gate in detail, CLI validation, uninstalling, what Readyset deliberately doesn't do, and the full file/package layout.
  • Brainstorming outside omp — write a brainstorm in Claude Cowork before you ever open omp.

License

MIT — see the LICENSE file. src/skill/mattpocock-grilling.md is vendored separately under its own MIT license (Matt Pocock, full text kept in the file itself).

Resolve ambiguity before planning. Ground the plan in the real repo. Make the proposal reviewable. Require human approval before execution. Keep runtime evidence separate from claims of correctness. Then:

/readyset