compose-product-portfoliolisted

# Compose Product Portfolio Turn a growing platform into a coherent portfolio without turning every feature into a product. Optimize for independently useful units, narrow semantic ownership, simple public surfaces, and composition through explicit contracts. Read [references/composable-product-portfolio-method.md](references/composable-product-portfolio-method.md) before classifying or separating product units. ## Atomic boundary This Skill owns one **Composable Product Portfolio Contract**: - portfolio-level customer jobs and product-unit boundaries; - classification of proposed surfaces as product, embedded capability, shared substrate, connector, composed experience or bundle; - the product and connector graph; - standalone-use, operational, commercial and dogfooding obligations; - decisions to keep together, extract, merge, replace or retire units; and - proof that composition does not create a hidden monolith or a fragmented distributed system. It does not own product-local domain semantics, source modules, prices, entitlements, deployment topology, runtime cells, or delivery evidence. Those remain with their owning product and matching Standards or Procedures. ## Core invariants 1. A product unit is defined by a coherent customer job and durable product promise, not by code size, a menu item, a Capability name, or a desire for another website. 2. Product, Capability, module, repository, public site, service, database, deployment and runtime cell ar