nmrtn

Garry Tan's gstack proved you can give Claude Code a full engineering team via the SKILL.md standard. I asked: what about the PM layer?

One command (/pm-run) runs the full planning cycle inside your terminal — audit → objectives → strategy → roadmap → PRD. Each skill writes a markdown artifact, the next one reads it. Context compounds across the whole pipeline.

The part I find most useful: it builds persistent memory of your product in ~/.nanopm/memory/. Re-run /pm-audit six months later and it knows what you tried before. No other PM tool does this because no other PM tool lives in your editor.

/pm-breakdown creates tickets directly in Linear or GitHub Issues from the PRD.

https://github.com/nmrtn/nanopm

Early days, would love to know: does running PM work inside your editor feel right, or does it belong in a separate tool?