feat(openprd): implement the OpenPRD standard — engine, CLI, conformance bundle

[ralyodio]

OpenPRD has existed as a document — docs/openprd.md, a front-matter schema, a template, and this repo's prd/ collection. Nothing enforced it. This adds the reference implementation.

45 files, ~3.6k lines.

@logicsrc/openprd

• Parser — front-matter, the eight ## sections, numbered requirements. ### stays content so a long Requirements section can be organized, and headings or R#-shaped lines inside code fences are ignored. Handles - R1 [P0] … and the bolded - **R1 [P0]** … style real PRDs use.
• Validation splits the standard's four conformance rules — filename, front-matter schema, id-matches-prefix, eight sections in order — from lint (empty section, missing priority tag, numbering gaps, duplicate R#, date order, one-sided supersession, stale index). Conformance failures are errors; --strict promotes the rest. Every finding carries a stable code, file, line, and hint.
• Collection rules a per-file view can't see: unique ids, monotonic numbering with no gaps, 0000 reserved for the template, cross-references that resolve.
• Lifecycle enforced, not advisory: Draft cannot jump to Final, terminal statuses do not resume, Superseded must name its replacement.
• Deterministic index generation — prd index is idempotent and CI can diff it.
• Front-matter rewriting that leaves the body byte-identical.
• Task bridge — the optional mapping the standard describes, living in tooling where it says it should: each R# becomes one logicsrc.task, validated against logicsrc-task.schema.json before emission.

CLI

logicsrc prd init
logicsrc prd new "Expand the parked-domain service"
logicsrc prd validate --strict
logicsrc prd status 0001 Review
logicsrc prd tasks 0001 --priority P0

init|new|list|show|validate|lint|index|status|next|tasks|export. Exit codes stable for CI: 0 ok, 1 invalid, 2 usage, 3 not found.

Conformance bundle

packages/schemas/fixtures/openprd/ — 6 documents that must validate, 12 that must fail, each naming the error code it must produce. Several rules depend on the filename, so every fixture records the name it is validated as.

Verification

• 76 new tests; full monorepo build and all 451 workspace tests pass
• The suite dogfoods this repo: prd/ validates with zero errors and zero warnings, the embedded template is byte-identical to docs/openprd/0000-template.md, and all 210 requirements in PRD 0001 map to schema-valid tasks
• prd/README.md is now regenerated by the tool it ships — the hand-written index it replaced was correctly flagged as stale

Note

The standard document itself is unchanged except for a new Implementation section. A PRD is still just a file: none of this is required for a document to conform.

🤖 Generated with Claude Code

[github-actions]

vu1nz Security Review

0 finding(s) in PR #?

No security issues found.