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

pi-spec-builder

v0.1.1

Published

Spec-Driven Development (SDD) and architecture planning framework for Pi Coding Agent

Readme


📐 Overview

pi-spec-builder brings structured Spec-Driven Development (SDD) and architectural guardrails to Pi Coding Agent.

Left unchecked, AI coding agents frequently begin editing code immediately without clarifying requirements, designing interface contracts, or considering failure modes.

pi-spec-builder enforces a battle-tested 3-phase development lifecycle inside .specs/<feature>/:

  1. Proposal: Clarify user problem, non-goals, and tradeoffs.
  2. Specification: Detail TypeScript interface contracts, data models, and Mermaid architecture diagrams.
  3. Tasks: Break work into atomic, verifiable checklists.

Code modification is gated until you review and approve the architectural specification.

┌─────────────────┐       /sdd init feature      ┌─────────────────────────┐
│                 │ ───────────────────────────> │  01-proposal.md         │
│                 │                              │  (Problem & Non-Goals)  │
│                 │ <─────────────────────────── └───────────┬─────────────┘
│                 │     /sdd approve proposal                │
│    Developer    │                                          ▼
│    (Terminal)   │                              ┌─────────────────────────┐
│                 │                              │  02-specification.md    │
│                 │                              │  (Interfaces & Mermaid) │
│                 │ <─────────────────────────── └───────────┬─────────────┘
│                 │     /sdd approve spec                    │
│                 │                                          ▼
│                 │                              ┌─────────────────────────┐
│                 │                              │  03-tasks.md            │
│                 │                              │  (Implementation Phase) │
└─────────────────┘                              └─────────────────────────┘

✨ Features

  • 📑 Standardized SDD Artifacts: Automatically structures proposals, specs, and task lists.
  • 🚦 Phase Transition Gates: Tracks approval states per feature in .specs/status.json.
  • 📊 Architecture Diagrams: Integrated Mermaid boilerplate for sequence and component flows.
  • 🛡️ Autonomous Guard (sdd_check_guard): Pi self-audits whether sign-off was given before making edits.

🚀 Installation

Via Pi Package Registry (Recommended)

pi install npm:pi-spec-builder

Direct from GitHub

pi install git:https://github.com/lleontor705/pi-spec-builder.git

From Local Source

git clone https://github.com/lleontor705/pi-spec-builder.git
cd pi-spec-builder
npm install && npm run build
pi install ./

📖 Usage & Commands

Slash Commands

| Command | Description | | :--- | :--- | | /sdd init <feature> | Scaffolds .specs/<feature>/ with standard markdown templates. | | /sdd status | Displays active features and their current phase / approval status. | | /sdd approve <feature> proposal | Approves Phase 1 (Proposal) and moves to Specification. | | /sdd approve <feature> specification | Approves Phase 2 (Spec) and unlocks code implementation. |

Agent Autonomous Tools

  • sdd_init_feature: Pi initializes an SDD feature folder when tasked with a complex goal.
  • sdd_check_guard: Pi checks if the specification is approved before touching source code.
// Prompt:
"We need to implement a rate-limiter using sliding-window Redis counters."

Pi creates .specs/rate-limiter/01-proposal.md and pauses:

"I have drafted the proposal in .specs/rate-limiter/01-proposal.md. Run /sdd approve rate-limiter proposal when you're ready to proceed to API specifications."


🏗️ Architecture & Development

# Clone
git clone https://github.com/lleontor705/pi-spec-builder.git
cd pi-spec-builder

# Install & Build
npm install
npm run build

📄 License

MIT © Luis Leon