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

@dk/speckit-opencode-plugin

v0.1.1

Published

OpenCode plugin for spec-kit/specify workflow - specification-driven development

Readme

@dmytri/speckit-opencode-plugin

OpenCode plugin for spec-kit workflow - specification-driven development.

Installation

See OpenCode Plugins for full documentation.

Add to your opencode.json:

{
  "plugin": ["@dmytri/speckit-opencode-plugin"]
}

OpenCode will automatically install the plugin on next start.

Requirements

specify CLI must be installed. See speckit.org for installation instructions:

# Install with uv (recommended)
uv tool install specify-cli --from git+https://github.com/github/spec-kit.git

# Verify installation
specify --version

The plugin will notify you if specify is not installed.

Usage

speckit({ action: "init" })        // Initialize spec-kit in current project (auto-runs on first use)
speckit({ action: "check" })       // Verify specify CLI and tools installed
speckit({ action: "phase" })       // Check current workflow phase and guidance

Workflow

After initialization, the agent uses slash commands for each phase:

  1. /speckit.constitution - Create project principles
  2. /speckit.specify - Define requirements
  3. /speckit.plan - Create technical plan
  4. /speckit.tasks - Break into tasks
  5. /speckit.implement - Execute tasks

Use speckit({ action: "phase" }) to check current progress and get guidance on what's next.

How It Works

  • Agent uses plugin tool for spec-kit operations (never uses CLI directly)
  • Plugin auto-initializes .specify/ via specify init
  • Plugin provides phase tracking and workflow guidance
  • Slash commands (loaded from .specify/templates/commands/) drive the actual workflow