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

@ceatoleii/specflow

v2.3.0

Published

Spec-driven multi-agent workflow for Cursor and AI coding tools

Downloads

1,562

Readme

SpecFlow

Turn AI coding sessions into a repeatable spec-driven workflow.

CI npm version License: MIT Node

npx @ceatoleii/specflow init

Full guide: English · Español


What it does

SpecFlow installs a four-phase pipeline into your repo so your AI assistant:

  1. Clarifies the requirement before coding (task.md with acceptance criteria)
  2. Designs a plan you approve (plan.md, tasks.md)
  3. Implements only what was approved (one agent writes code)
  4. Reviews against your criteria and verification commands (review.md)

Until you start a task, nothing changes — your assistant works as usual (Direct mode). When you say nueva tarea or flow on, Flow mode routes each message to the right phase agent.

v2.2+ installs the Cursor adapter by default. Optional Linear sync moves issue states (Todo → In Progress → Done) via the Linear MCP plugin in Cursor — not via CLI API keys.

Full Linear setup: Linear Integration · ES


Install (2 minutes)

From your project root (Node.js ≥ 18, interactive terminal):

npx @ceatoleii/specflow init

The wizard asks for language, Cursor adapter, optional Linear sync, and .agents-docs/ templates. Then:

specflow doctor          # verify install

Add to .gitignore:

.agents-state/

Your first task (cheat sheet)

| Step | You say | You get | |------|---------|---------| | Start | nueva tarea or flow on (or nueva tarea desde LIN-123) | Refiner asks clarifying questions | | Refine | Answer questions | .agents-state/current/task.md | | Design | Wait, then review plan | plan.md, tasks.md | | Approve | /approve | Implementer writes code | | Done | Wait for review | Archive + flow off on PASS |

Stop anytime: flow off or modo directo.

Details, diagrams, and what to read in each phase: How it works · Primer flujo (ES)


Everyday commands

| Command | Why use it | |---------|------------| | specflow init | First-time install in a project | | specflow doctor | Check files, adapters, flow state | | specflow doctor --run | Same + run your verification.md commands | | specflow status | Version, adapters, Linear on/off, update available | | specflow sync | Update engine & adapters (keeps .agents-docs/) | | specflow linear setup | Enable Linear state sync (Cursor MCP) |


What you edit vs what SpecFlow manages

| You own | SpecFlow manages (init / sync) | |---------|-------------------------------------| | .agents-docs/ — stack, conventions, how to test | .agents/ — orchestrator & phase rules | | Your source code (via Implementer in flow) | AGENTS.md, adapters, .specflow-version | | .gitignore entry for .agents-state/ | |

Fill .agents-docs/ before serious tasks so agents know your stack and test commands.


Documentation

| | | |---|---| | Guide (EN) | ceatoleii.github.io/specflow | | Guía (ES) | ceatoleii.github.io/specflow/es | | npm | @ceatoleii/specflow | | Changelog | CHANGELOG.md |


License

MIT © ceatoleii