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

@devground/sdd

v1.5.0

Published

spec-flow: the spec-driven development intake skill — classify, enrich and route any change to the right amount of process, installable into any project

Vulnerabilities

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

Links

Git

Maintainers

elkisdmelkisdm

Keywords

spec-driven-developmentsddspec-flowclaude-codeskillintakedevground

Readme

@devground/sdd

spec-flow — the spec-driven development intake skill for Claude Code. It turns a raw, vague change request into a right-sized, professional spec, then routes it to the minimum process the change actually deserves. Infer aggressively, state assumptions, proceed — escalate ceremony only when the change is big or risky enough to earn it.

Install

Into the current project:

npx @devground/sdd
# -> .claude/skills/spec-flow/

For all your projects (user-level):

npx @devground/sdd --global
# -> ~/.claude/skills/spec-flow/

Existing files are never overwritten — re-run after an upgrade to add new reference files while keeping your local edits.

What it does

Given a change request ("add login", "make this faster", "fix this bug"), the skill:

  1. Orients via docs/codemap.md (reading it is mandatory when it exists) and verifies paths against real code.
  2. Classifies along 5 orthogonal axes: type · size · risk · uncertainty · surface.
  3. Routes to one of 4 tiers (Express → Light → Standard → Full) so a typo skips straight to the fix while a risky migration gets explore + spec + design + ADR.
  4. Enriches into a dual-audience brief (plain-language summary + technical depth) with the concrete files & routes to touch — and, from Tier 2 up, a pre-mortem: paths, failure modes, invariants (each with the test that breaks it), symmetries and reuse, answered before code exists. It is the reviewer's question list, moved to spec time (ADR-0037).
  5. Gates the design (Step 3.6): the brief is reviewed against that checklist before the first edit; on Tier 3 the gate can be delegated to a read-only planner.
  6. Closes with tests and a bounded review: new logic ships with tests watched to fail with the fix reverted (ADR-0029), then /code-review runs as a gate with a ledger — two passes by default, a third only after a redesign (ADR-0036, ADR-0037).
  7. Emits telemetry (one line per change to .spec-flow/events.jsonl) so impact is measurable — including first-pass findings with vs without a pre-mortem, the number that says whether the whole thing works.

Measuring impact

This package ships the skill only. Whether spec-flow actually helps — test-coupling, code survival, orientation cost, friction — is measured by @devground/dev-metrics (dev-metrics spec-flow-impact and dev-metrics orientation), which reads the .spec-flow/events.jsonl telemetry plus git and transcript history.

Fuente canónica y sincronización

La skill viva se desarrolla en ~/.claude/skills/spec-flow/ (validada en uso real). El directorio skill/ de este paquete es una copia versionada de esa fuente. Tras un cambio en la skill canónica, resincroniza el mirror:

node scripts/sync-spec-flow.mjs   # o: pnpm --filter @devground/sdd sync

El script copia SKILL.md + references/ desde ~/.claude/skills/spec-flow/; no copia evals/ (vive solo en la fuente canónica). No se corre en prepublishOnly a propósito: la fuente está fuera del repo, así que el mirror commiteado es lo que se publica y sincronizar es un acto deliberado del desarrollador, no un paso de release.

License

MIT