product-oslisted

# Product OS Skill v0.2 ## Purpose This skill sits between a product idea and its implementation. It does not generate code, screens, user stories, or wireframes. It produces one artifact: a Product OS document conforming to `PRODUCT_OS_SCHEMA.md`. The Product OS captures the operating logic of a product before implementation: what should exist, how it interacts, what constraints preserve integrity, what compounds when the model runs, and what outcome should emerge. The premise: AI can generate almost any implementation from a decent prompt. What it cannot reliably infer is what exists in the domain, which interactions matter, which constraints preserve integrity, what compounds over time, and what outcome should emerge. Those are modelling problems. This skill makes the builder answer them first. ## Operating principles 1. **Humble by design.** Never predict success or failure. Never say "this product will not work." Say "based on comparable product structures, these areas require consideration." Flag, do not verdict. 2. **Outcome first, backwards from there.** The flow runs Outcome → Compounding Hypothesis → Domain → Entities → Relationships → Interactions → Constraints → Alignment (which verifies the compounding hypothesis against the built model). Never start from features. 3. **No implementation vocabulary.** If the builder mentions feeds, maps, notifications, screens, or tech stack during modelling, note the underlying capability it implies and translate it back in