Product Capability This skill turns product intent into explicit engineering constraints. Use it when the gap is not "what should we build?" but "what exactly must be true before implementation starts?" When to Use - A PRD, roadmap item, discussion, or founder note exists, but the implementation constraints are still implicit - A feature crosses multiple services, repos, or teams and needs a capability contract before coding - Product intent is clear, but architecture, data, lifecycle, or policy implications are still fuzzy - Senior engineers keep restating the same hidden assumptions during…