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

spec-driven-docs

v1.1.0

Published

Documentation templates for spec-driven development of AI-native systems

Readme

Spec-Driven Development Template

Documentation templates for spec-driven development of AI-native systems.

What This Is

This repository contains structured documentation that serves as:

  • Templates for building AI-native control planes
  • Contracts that define how LLMs should reason about systems
  • Governance structures for agent-based architectures

Particularly useful for teams building agentic systems where governance, auditability, and clear boundaries matter.

Documentation Relationship Map

                                    ┌─────────────────────────┐
                                    │  markdown-glossary.md   │
                                    │  (Central Hub)          │
                                    │  Authoritative source   │
                                    │  for update triggers    │
                                    └───────────┬─────────────┘
                                                │
                    ┌───────────────────────────┼──────────────────────────┐
                    │                           │                          │
        ┌───────────▼───────────┐   ┌───────────▼──────────┐   ┌──────────▼─────────┐
        │     README.md         │   │   CLAUDE.md          │   │ implementation-    │
        │                       │   │                      │   │ plan.md            │
        │  - Entry point        │   │  - AI instructions   │   │                    │
        │  - Overview           │   │  - Phase protocol    │   │  - Phase tracking  │
        └───────────────────────┘   └──────────┬───────────┘   └─────────┬──────────┘
                                               │                          │
                                    ┌──────────▼──────────┐              │
                                    │   vision.md         │              │
                                    │   architecture.md   │              │
                                    │   invariants.md     │              │
                                    │   models.md         │              │
                                    └─────────────────────┘              │
                                                                         │
        ┌────────────────────────────────────────────────────────────────┘
        │
        │         ┌─────────────────────────┐           ┌──────────────────────────┐
        └────────►│  phase-audit.md         │──────────►│  phase-NN-audit.md      │
                  │  (Skill/Enforcement)    │  creates  │  (Generated reports)     │
                  │                         │           │                          │
                  └────┬────────────────────┘           └──────────────────────────┘
                       │
                       │ validates
                       │
                  ┌────▼────────────────────┐
                  │  adr-template.md        │
                  │                         │
                  └─────────────────────────┘
                       │
                       │ used by
                       │
                  ┌────▼────────────────────┐
                  │  adr-001-*.md           │
                  │  (Actual ADRs)          │
                  └─────────────────────────┘


        ┌─────────────────────────┐           ┌──────────────────────────┐
        │  codebase-health.md     │──────────►│  health-log.md          │
        │  (Skill/Monitoring)     │  appends  │  (Health reports)        │
        │                         │           │                          │
        └─────────────────────────┘           └──────────────────────────┘


        ┌─────────────────────────┐
        │  stubs.md               │
        │  artifacts.md           │◄──────── Referenced by phase-audit.md
        │  contracts.md           │          (Retrospective checks)
        │  glossary.md            │
        └─────────────────────────┘

See docs/markdown-map.md for the full relationship analysis.

Repository Structure

.
├── .claude/                    # Claude Code Editor configuration
│   └── settings.local.json     # Local Claude settings
│
├── .github/                    # GitHub-specific configurations
│   └── workflows/              # GitHub Actions workflows
│       └── audit-check.yml     # Automated audit validation
│
├── CLAUDE.md                   # AI assistant persistent context and rules
├── README.md                   # This file - repository overview
├── implementation-plan.md      # Phase tracking and implementation roadmap
│
├── docs/                       # Authoritative documentation templates
│   ├── architecture.md         # System architecture specification
│   ├── artifacts.md            # Artifact definitions and contracts
│   ├── contracts.md            # System contracts and interfaces
│   ├── health-log.md           # Codebase health monitoring log
│   ├── invariants.md           # Non-negotiable system constraints
│   ├── markdown-map.md         # Documentation relationship analysis
│   ├── models.md               # Data models and schemas
│   ├── stubs.md                # Stub definitions for development
│   ├── vision.md               # System philosophy and long-term goals
│   │
│   ├── audits/                 # Phase audit reports (generated per phase)
│   │
│   ├── decisions/              # Architecture Decision Records (ADRs)
│   │   └── adr-template.md     # Template for creating new ADRs
│   │
│   └── glossary/               # Term and file contracts
│       ├── glossary.md         # System terminology definitions
│       └── markdown-glossary.md # Central hub: authoritative source for update triggers
│
├── scripts/                    # Automation scripts
│   └── hooks/                  # Git hooks for enforcement
│       ├── README.md           # Git hooks documentation
│       ├── commit-msg          # Commit message validation hook
│       └── pre-commit          # Pre-commit validation hook
│
└── skills/                     # LLM-enforced procedures and skills
    └── llm/                    # LLM-specific skills and capabilities
        ├── codebase-health.md  # Skill for monitoring codebase health
        └── phase-audit.md      # Skill for enforcing phase completion protocol

Purpose

Each file in this repository is designed to become a reusable template for spec-driven development workflows where:

  1. Specifications are written first
  2. LLMs implement against those specs
  3. Governance ensures compliance
  4. Documentation stays synchronized with reality

Quick Start

npx spec-driven-docs init

This copies all documentation templates into your current project directory. Use --force to overwrite existing files.

Then:

  1. Customize CLAUDE.md for your project
  2. Fill in docs/vision.md with your system intent
  3. Update implementation-plan.md with your phases

Learn More

See docs/vision.md for the system philosophy.

See docs/glossary/markdown-glossary.md for file-level contracts.