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.
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
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 published v0.4.0 line includes local and GitHub workflows, a deterministic Project Timeline over committed snapshots, twelve read-only MCP tools, reproducible release archives, checksums, and a prefix-scoped installer.
Current evidence
v0.4.0 is the latest published stable release. The 0.5.0 source line prepares a compatible CLI namespace migration but is explicitly not yet published.
Learnings
Project intelligence can be useful without probabilistic interpretation when source rules, boundaries, and output contracts are explicit.
Artifacts
Product evidence
cli
Four deterministic local workflows
The README documents brief, risks, next, and handoff commands over local Markdown, with no upload, project-file modification, external integration, or LLM requirement.
The core project-intelligence workflow is local, read-only, and inspectable from its public command contract.
documentation
Rule-based signal extraction
The extraction guide defines exact bilingual headings and markers, label precedence, ordering, deduplication, limits, overdue inference, and false-positive guards.
Risk and next-task outputs are produced by bounded deterministic rules rather than probabilistic interpretation.
architecture
Opt-in read-only GitHub provider
The provider guide limits network access to explicit commands, GET-only requests to one approved GitHub origin, bounded responses, environment-only tokens, and controlled error codes.
External context access is separated from offline workflows and constrained by a documented read-only boundary.
Test and validation
test
Cross-language validation surface
The root package scripts expose TypeScript and Rust tests, public-surface, structure, boundary, contract, version and command checks, MCP smoke tests, and release reproducibility checks.
The repository owns repeatable validation across its Node.js, Rust/WASM, MCP, installer, and release boundaries.
Installation and usage
installation
Preview-first local installation
The getting-started guide separates a no-write preview from explicit apply, scopes shims to a chosen prefix, leaves PATH and client configuration untouched, and provides a read-only verifier.
Installation mutations require an explicit apply step and remain bounded to declared targets.
Release and distribution
release
v0.4.0 Project Timeline release
The stable release adds a derived, bounded timeline over committed Project Brain snapshots without a new schema, store format, migration, write path, or network path.
The latest stable capability extends historical analysis while preserving the existing local and read-only trust boundary.
Current limitations
- v0.4.0 remains the latest published stable release; the 0.5.0 source line is prepared but is not presented here as a published release.
- Workspace packages are private and are not published to npm; supported distribution is repository- and GitHub-Release-based.
- Extraction does not infer arbitrary prose or semantic paraphrases, provider writes remain unavailable, and the outdated upstream hero artwork is not treated as current product evidence.
Overview
- Role
- Product definition, workflow architecture, delivery management, and validation
- Complexity
- High
- Detail level
- Case study
Responsibilities
- Problem definition
- Scope definition
- Product architecture
- Technical delivery
- Validation
Outcome
oh-my-pm provides stable local and GitHub read-only workflows for deterministic briefs, risks, next tasks, handoffs, and MCP access.