The four pillars of your PM Operating System
The PM Operating System is what allows you to operate AI as a system, and not a chatbot. Your Personal PM OS runs on four pillars: context grounds every output in your reality, skills do the production work, subagents pressure-test it through stakeholder lenses, and workflows chain them into a single run.
When to use this
- You are new to mySecond and want a map of how the pieces fit
- You are deciding whether to run a single skill or a full workflow
- You are explaining the PM OS shape to a teammate
The four pillars
| Pillar | What it is | Where to learn more |
|---|---|---|
| Context | Five markdown files capturing your company DNA — company.md, product.md, personas.md, competitors.md, goals.md | Context overview |
| Skills | Reusable PM commands like /prd-generator and /competitive-profile-builder, each a SKILL.md file with structured instructions | Skills |
| Subagents | Stakeholder perspectives your team may lack — CTO, UX Lead, Sales Lead — that review any document for a 360° read | Subagents |
| Workflows | Multi-step runs that chain skills and subagents — drop input files, get structured outputs (e.g. Problem-to-PRD, Competitive Intel Pack) | Workflows |
How they work together
Context is the foundation every other pillar reads. When you run a skill like /prd-generator, it pulls from company.md, personas.md, and goals.md so the output is grounded in your reality, not generic advice. Subagents review those outputs through specific stakeholder lenses — a CTO subagent flags feasibility gaps, a UX Lead subagent flags friction. Workflows compose the whole thing: one run can scan inputs, fire several skills in sequence, hand the draft to two subagents in parallel, and return a finished artifact. You can also run any pillar on its own.