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

@engramm/dev-workflow

v3.0.1

Published

Development workflow engine with agents and vault for Claude Code

Readme

dev-workflow

npm CI License: MIT

Multi-agent development pipeline for Claude Code. 11 steps from task to commit, with quality gates, isolated agent permissions, and persistent project vault.

PREFLIGHT → READ → PLAN → PLAN_REVIEW → PLAN_FIX → CODER → REVIEW×3 → TEST → VERIFY → COMMIT
   bash     Explore Explore  Explore      Full       Full    Explore×3   bash  Explore   Full

Why

Claude Code is powerful, but without structure it improvises. It skips reviews, forgets tests, loses context between sessions, and drifts from the original task.

dev-workflow gives it a strict protocol: every task goes through an 11-step pipeline with quality gates. Each agent is isolated by permissions. Context persists across sessions.

Features

  • 11-step quality pipeline — preflight, plan with pseudo-code, plan review (9 criteria), surgical plan-fix on detail-level revisions, test-first coding, 3 parallel reviewers, mandatory test gate, task verification, commit
  • Agent isolation — reader can't write, coder can't commit, reviewer can't modify code
  • 3 specialized reviewers — security, quality, and coverage run in parallel on real git diff
  • Vault — persistent project knowledge: stack, conventions, architecture, gameplan
  • Intelligence — pattern graph with scoring (recency, frequency, context match)
  • Phase mode — break large specs into phases, code each subtask separately
  • Interactive & autonomous — ask before commit (default) or auto-commit for swarm use
  • 26 MCP tools — programmatic access to vault, tasks, intelligence, memory, workflows, agents, communication profiles (via .mcp.json)
  • Engram memory — persistent long-term store with semantic search via Voyage AI embeddings; auto-decorated with pipeline tags (step/branch/run/task)
  • 3 hooks — SessionStart, SessionEnd, TaskCompleted
  • From spec to code/vault:from-spec fills vault from SPEC.md in 4 phased steps
  • Auto-setupinit generates CLAUDE.md, permissions, .mcp.json, stack-based .gitignore, and scaffolds .claude/{agents,skills}/
  • Plan persistence — approved plans saved to vault for audit and session resume
  • Modular prompts — thin shim orchestrator (~14 lines) + 11 step files read on demand

Quick Start

npm install -g @engramm/dev-workflow
cd your-project
dev-workflow init

Then in Claude Code (VS Code or CLI):

/vault:analyze                  # fill vault from existing codebase
/workflow:dev "add email validation"   # run the full pipeline

New project from specification

/vault:from-spec                # fill vault from SPEC.md
/workflow:dev .dev-vault/phases/phase-1-foundation.md   # implement phase 1

Pipeline

| Step | Agent | What it does | |------|-------|-------------| | 0. PREFLIGHT | bash | Baseline: git status, build, tests | | 1. READ | Explore | Gather context from codebase | | 2. PLAN | Explore | Architecture analysis + pseudo-code | | 3. PLAN_REVIEW | Explore | 9 criteria + verdict-aware gate (NEEDS_REVISION short-circuits user-approve) | | 4. PLAN_FIX | Full | Apply surgical Edits to saved plan when reviewer emits Next: plan-fix (no-op pass-through if approved) | | 5. CODER | Full | Test-first implementation | | 6. REVIEW | Explore ×3 | Security + Quality + Coverage (parallel, real git diff) | | 7. FIX LOOP | Full + Explore | Coder fixes, reviewer re-checks (max 3 iterations) | | 8. TEST | bash | Build + lint + tests (compared against baseline) | | 9. VERIFY | Explore | Does the code match the original task? | | 10. COMMIT | Full | Stage + commit (interactive or autonomous) |

Permission Matrix

Agent          Read   Write   Bash           Subagent
─────────────  ─────  ──────  ─────────────  ────────
READ           yes    no      no             Explore
PLAN           yes    no      no             Explore
PLAN_REVIEW    yes    no      no             Explore
PLAN_FIX       yes    yes     no             Full (coder)
CODER          yes    yes     build/test     Full
REVIEW ×3      yes    no      no             Explore
TEST           no     no      build/test     bash
VERIFY         yes    no      no             Explore
COMMIT         no     no      git only       Full

Violation = immediate pipeline abort.

Slash Commands

Vault

| Command | Description | |---------|------------| | /vault:from-spec | Fill vault from project specification (4 phases with approval gates) | | /vault:analyze | Deep codebase analysis, fill conventions + knowledge | | /vault:bug | Record a resolved bug | | /vault:adr | Record an architecture decision | | /vault:pattern | Append a pattern bullet to conventions.md | | /vault:debt | Record tech debt | | /vault:arch | Architecture analysis: 2-3 options with trade-offs | | /vault:project-review | Full project audit: 7 perspectives, A-F scoring | | /vault:deps | Map module dependencies | | /vault:security-scan | Security audit | | /vault:test-gaps | Find untested code |

Workflow

| Command | Description | |---------|------------| | /workflow:dev "task" | Full 11-step pipeline | | /workflow:dev path/phase.md | Phase mode (subtask loop) | | /workflow:dev "task" --auto-commit | Autonomous mode for swarm | | /workflow:graph "name" | Render workflow as Mermaid DAG (chat-friendly) |

Session

| Command | Description | |---------|------------| | /session:resume | Restore session context | | /session:handover | Save detailed session notes | | /session:review | Multi-perspective code review (5 perspectives) | | /profile [<name>\|clear] | Switch communication profile (language/tone/verbosity) — see Communication Profiles |

Git

| Command | Description | |---------|------------| | /git:new-branch | Create branch context | | /git:pr-review | PR review with vault context | | /git:changelog | Generate changelog | | /git:merge | Transfer knowledge after merge |

CLI

dev-workflow init [--force] [--detect]   # Initialize vault, hooks, CLAUDE.md, .mcp.json
dev-workflow update                      # Update agents/skills from package (additive for skills)
dev-workflow templates-root              # Print absolute path to bundled templates/
dev-workflow settings-template           # Print bundled .claude/settings.json (absolute paths)
dev-workflow spec-template               # Print bundled SPEC.md template (Mirror Skeleton)
dev-workflow communication-template      # Print bundled communication.yaml template (4 profiles)
dev-workflow engram-trace <runId>        # Show engram socket trace summary [--raw]
dev-workflow workflow show <name> [--bodies]   # Inspect workflow structure
dev-workflow workflow graph <name> [--ascii]   # Render DAG (Mermaid default)
dev-workflow workflow effective <name>          # Show resolved step-files + subagents
dev-workflow vault diff [SPEC.md]        # Compare SPEC against vault (exit 0=match, 1=drift)
dev-workflow status                      # Vault and workflow status
dev-workflow doctor [--fix]              # Health check (vault, hooks, .mcp.json, permissions)
dev-workflow task create|list|start|done # Task management
dev-workflow agent list|show|run         # Agent management
dev-workflow run dev|hotfix|review|test  # CLI workflows
dev-workflow search "query"              # Search vault
dev-workflow config show|get|set         # Configuration
dev-workflow export|import               # Vault backup
dev-workflow serve                       # Start MCP server
dev-workflow web [--port N] [--open]     # Start the web dashboard (http://127.0.0.1:3737)

MCP Tools

26 tools available via MCP server:

| Tool | Description | |------|------------| | vault_status | Full vault state in one call | | vault_read | Read vault section | | vault_search | Search vault files | | vault_record | Create ADR / bug / debt record (auto-mirrored to engram) | | vault_knowledge | Append to knowledge.md | | vault_pattern | Append a pattern bullet to conventions.md | | intelligence_query | Query pattern graph with scoring | | task_create | Create task | | task_list | List tasks | | task_update | Update task | | task_start | Start task (link to branch) | | task_create_from_phase | Parse phase file and create missing tasks | | workflow_status | Current workflow status | | workflow_create | Save a custom workflow YAML | | workflow_start | Initiate a workflow run (slash-orchestrator path): create state file, set engram trace env vars, return runId | | step_start | Update run.currentStep at the start of a workflow step (symmetric pair with step_complete). Tags engram traces with the current step: | | agent_list | List agents with permissions | | agent_run | Generate agent prompt with vault context | | parse_engram_feedback | Parse ## Engram Feedback block from agent output | | memory_search | Search Engram memories with auto-decoration (step/branch/run/task tags) | | memory_store | Store Engram memory with auto-decoration; throws daemon errors to caller | | memory_judge | Rate Engram memory's usefulness (0.0–1.0) | | step_complete | Finalize a pipeline step: parse ## Engram Feedback, apply judgments (no blanket fallback), emit antipattern observability | | profile_get | Read communication profile state (active + default + available + config) | | profile_set | Activate communication profile (validates name; persists to .dev-vault/.profile-state) | | profile_clear | Reset communication profile state (delete .profile-state; fallback to yaml default) |

Migration: 0.1.x → 0.2.0

mcp__dev-workflow__memory_store now throws daemon errors (Voyage 403, offline, etc.) via JSON-RPC isError: true — previously returned silent {id: null}. Wrap calls in try/catch if you depend on silent behavior, or call mcp__engram__memory_store directly (no auto-decoration). Auto-mirror via vault_record / vault_knowledge / vault_pattern is unchanged (silent fail-safe; vault file is source of truth).

Engram socket resolution moved to per-project: ENGRAM_SOCKET_PATH<project>/.engram/engram.sock$HOME/.engram/engram.sock (legacy). Run engram migrate from the project root to copy legacy memories.

Pipeline gained 11th step PLAN_FIX. dev-workflow validate warns about stale references in custom workflows.

Full notes: CHANGELOG.md.

Documentation

Full documentation: supostat.github.io/dev-workflow

License

MIT