Packages

The OSS half of AtomPRD lives at github.com/atomprd/atomprd. All packages are MIT.

Shipped

Package	Version	Use for
@atomprd/spec	v0.3.0	Zod schemas + 26 atom kinds + 20 relations + 2-layer + provenance types
@atomprd/core	shipped	PrdDocument wrapper + diff + integrity validation
@atomprd/codegen	shipped	CodegenTemplate interface + runTemplate() driver
@atomprd/codegen-senlang	v0.3.0	Bridge: atoms → SenLang Document v0.3 + map + scenarios
@atomprd/sdk	shipped	Re-exports for downstream consumers
@atomprd/mcp-server	shipped	MCP transport (HTTP + stdio) for IDE / agent integration
@senlang/to-atomprd	v0.1.0	Reverse: Sen Document → AtomPRD draft manifest (lives in senlang/tools/)

Scaffold (WIP)

Package	Status
@atomprd/cli	atomprd init / validate / gen / mcp — 4-command thin CLI
@atomprd/codegen-nestjs	NestJS template — entities, controllers, migrations

Internal-first (deferred)

Per the BOUNDARIES charter, Cloud-internal modules are NOT extracted into OSS until the boundary stabilises. Candidates that may publish later:

• @atomprd/store — PrdStore + SessionStore interfaces (file / S3 / Postgres impls).
• @atomprd/llm — LlmClient interface + OpenRouter / Claude / Gemini providers.
• @atomprd/interview — PM Interview FSM (8-phase, storage-agnostic).
• @atomprd/decompose — Feature Decompose FSM.

These exist in the Cloud monorepo as private packages today. Publishing requires (a) an external consumer asking for the surface, and (b) a stable enough API that semver doesn’t churn.

Cloud-only (private)

Package	Notes
@atomprd-cloud/*	NestJS API, React dashboard, marketing, docs (this site).
packages-pro/billing	Lemon Squeezy integration + usage metering.
packages-pro/prompts-production	Per-vertical interview prompt packs.

These never publish to npm.

See also

• Spec → Overview — conformance + versioning.
• Governance → BOUNDARIES — OSS ↔ Cloud charter.
• Codegen → Architecture — how CodegenTemplate works.