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

@dt-workspace/cli

v4.18.0

Published

AI-powered CLI tool to generate workflow documentation from SOW documents using Claude Code or Gemini CLI

Readme

dt-workspace CLI

Transform Your SOW into Production-Ready Documentation in Minutes

npm version License: MIT Node.js

Stop writing documentation manually. Let AI do it.


The Problem

Every software project starts with a Statement of Work—but turning that SOW into comprehensive technical documentation takes days or weeks of manual effort.

  • API contracts written inconsistently across teams
  • Database schemas documented differently by each developer
  • BDD test scenarios created as an afterthought
  • ER diagrams that are always outdated
  • Technical specs that don't match implementation

The result? Delayed project kickoffs, miscommunication between teams, and documentation that's obsolete before development begins.


The Solution

dt-workspace uses AI (Claude Code or Google Gemini) to analyze your SOW and automatically generate:

  • Structured module documentation
  • API contracts with request/response schemas
  • Database schema definitions
  • BDD/Gherkin feature files
  • ER diagrams (Mermaid, PlantUML, or ASCII)
  • Development timelines
  • Error handling specifications

One command. Complete documentation. Production-ready.


Who Benefits

| Role | Value | |------|-------| | Developers | Focus on building, not documenting. Get consistent API contracts and database schemas from day one. | | Tech Leads | Enforce documentation standards across all projects. Every module follows the same structure. | | Project Managers | Accelerate project kickoffs. Transform weeks of documentation into a single afternoon. | | Executives | Reduce time-to-market. Faster documentation means faster development cycles. |


Key Features

| Feature | Description | |---------|-------------| | AI-Powered Analysis | Claude Code or Gemini CLI analyzes your SOW and extracts modules, features, and technical requirements | | Architecture Presets | Choose from microservices (NestJS/Kafka), monolith, or serverless (AWS Lambda) templates | | BDD Test Generation | Automatic Gherkin feature files for every module and feature | | ER Diagrams | Generate entity-relationship diagrams in Mermaid, PlantUML, or ASCII formats | | Customizable Templates | Export and modify Handlebars templates to match your organization's standards | | Multi-AI Support | Switch between Claude and Gemini with a single command |


Quick Start

Installation

npm install -g @dt-workspace/cli

Prerequisites: Node.js 18+ and either Claude Code CLI or Gemini CLI

Generate Documentation in 4 Steps

# 1. Verify AI provider and CLI version
dt-workspace doctor

# 2. Initialize project configuration
dt-workspace init

# 3. Generate documentation skeleton from your SOW
dt-workspace scaffold

# 4. Fill placeholders with AI-generated content
dt-workspace populate

Commands Reference

| Command | Alias | Description | |---------|-------|-------------| | init | - | Create .dt-workspace config file | | scaffold | generate | Generate documentation skeleton from SOW | | populate | complete | Fill placeholders with AI-generated content | | doctor | check | Check AI provider and CLI version | | upgrade | - | Upgrade CLI to latest version | | provider | switch | Switch between Claude and Gemini | | presets | - | List available architecture templates | | export | templates | Export templates for customization | | timeline | - | Generate development timeline | | diagram | er-diagram | Generate ER diagrams | | diagram:convert | convert-diagram | Convert diagrams between formats | | sync | restore | Rebuild config from filesystem | | clean | - | Delete generated docs and reset config |


What Gets Generated

workflows/
├── README.md                      # Project overview with links
├── er-diagram.md                  # Global ER diagram
│
├── web-application/
│   ├── timeline.md                # Development sequence & dependencies
│   │
│   └── user-management/
│       ├── README.md              # Module overview
│       ├── user-flows.md          # User journey documentation
│       ├── technical-specs.md     # Implementation details
│       ├── api-contracts.md       # Endpoint definitions
│       ├── database-schema.md     # Table structures
│       ├── er-diagram.md          # Module relationships
│       ├── realtime-events.md     # WebSocket/Kafka events
│       ├── error-handling.md      # Error codes & handling
│       │
│       └── features/
│           ├── user-registration.feature
│           ├── user-login.feature
│           └── profile-management.feature

Architecture Presets

| Preset | Stack | Best For | |--------|-------|----------| | microservices | NestJS, Kafka, PostgreSQL, WebSocket | Distributed systems, event-driven architecture | | monolith | Single application, REST APIs | Smaller teams, rapid prototyping | | serverless | AWS Lambda, DynamoDB, API Gateway | Cloud-native, pay-per-use scaling | | supabase | PostgreSQL, RLS, Edge Functions, Realtime | Rapid MVP, real-time apps | | firebase | Firestore, Cloud Functions, Hosting | Mobile-first, Google ecosystem | | nextjs-fullstack | App Router, Server Components, Actions | Modern React fullstack | | graphql-federation | Apollo Federation, Subgraphs | Unified graph from services | | kubernetes | Helm, Istio, HPA | Enterprise container orchestration | | event-sourcing | CQRS, Event Store, Projections | Audit trails, financial systems |

dt-workspace scaffold --preset serverless
dt-workspace presets  # View all presets

Custom Templates

Modify documentation structure to match your organization's standards:

# Export built-in templates
dt-workspace export --preset microservices

# Templates saved to .dt-templates/
# Edit Handlebars files as needed
# Your customizations apply to all future generations

SOW Format

Your Statement of Work should follow this structure:

# Project Name - Statement of Work

## Platform: Web Application

### User Management
User authentication and profile management.

**Features:**
- User registration with email verification
- Login/logout with session management
- Profile editing and avatar upload

**Technical Requirements:**
- Backend: UserService, AuthService
- Databases: PostgreSQL (users), Redis (sessions)
- Events: user.created, user.updated

Impact

| Before | After | |--------|-------| | Days writing API contracts | Minutes with AI generation | | Inconsistent documentation across teams | Standardized structure for every project | | Outdated ER diagrams | Diagrams generated from actual schemas | | BDD tests as an afterthought | Feature files from day one | | Manual format conversion | One command to switch diagram formats |


Support


License

MIT © Deepak Tiwari


Stop documenting. Start building.