nanopm runs the PM cycle inline in your editor (audit → strategy → roadmap → PRD), then /pm-breakdown writes a WORKFLOW.md + Linear tickets Symphony picks up.

The WORKFLOW.md embeds the source PRD, the strategic bet from per-project state, and a Falsification field the PRD requires — must have a named user segment, a number, an observable behavior, and a timeframe, or the skill blocks shipping. Codex agents read all of that as the per-issue prompt template.

Schema-validated against SPEC.md §5: 21/21 checks on bin/nanopm-symphony-validate I shipped. Haven't run against the Elixir reference yet — if you know of field-name drift between spec and impl, would love to know what to fix.

https://github.com/nmrtn/nanopm

Solo project, MIT.