Public case study

oh-my-pm

A local project intelligence system for structured product and project delivery workflows.

Active Node.js pnpm Rust WASM Vitest MCP

oh-my-pm converts local project documents and selected GitHub context into deterministic operating views. Its product boundary is deliberate: local files remain local, provider access is read-only, and extraction rules are inspectable.

Case study

Project breakdown

oh-my-pm product flow

Repository-supported product flow for oh-my-pm.

1 Project documents
2 Deterministic extraction
3 Brief risks next handoff
4 Validation
5 Release boundary

Relationships

Project documents Deterministic extraction
Deterministic extraction Brief risks next handoff
Brief risks next handoff Validation
Validation Release boundary

Project documents to Deterministic extraction to Brief risks next handoff to Validation to Release boundary

oh-my-pm architecture

Repository-supported architecture view for oh-my-pm.

CLI
Runtime
Kernel
Context providers
Validation

Relationships

CLI Runtime
Runtime Kernel
Kernel Context providers
Context providers Validation

CLI to Runtime to Kernel to Context providers to Validation

Problem

oh-my-pm turns those sources into deterministic operational views without requiring an LLM, uploading local content, or modifying project files.

Overview

Project context often sits across Markdown documents, issues, pull requests, checklists, and decision notes, making a consistent handoff expensive to assemble.

Product reasoning

The packages are repository-based rather than published to npm. Analysis is rule-based and bounded by recognized headings, labels, status rules, file limits, and read-only provider access.

Product decisions

Exact English and Persian markers replace fuzzy scoring for risk and task extraction. Installation is preview-first, and GitHub network access is opt-in and read-only.

Technical architecture

A CLI and stdio MCP server run over a runtime, a Rust/WASM kernel, deterministic extractors, local context providers, and a validation and release layer.

Execution and delivery

The public v0.3.0 line includes local brief, risks, next, and handoff commands; read-only GitHub workflows; ten MCP tools; deterministic release archives; checksum files; and a prefix-scoped installer.

Current evidence

v0.3.0 is documented as the latest stable release. Public release artifacts, checksums, validation commands, fixtures, and historical releases provide inspectable delivery evidence.