back
loading skill details...
Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and…
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 review You need a reusable artifact that can survive across harnesses and sessions Canonical Artifact If the repo has a durable product-context file such as PRODUCT.md, docs/product/, or a program-spec directory, update it there. If no capability manifest exists yet, create one using the template at:
don't have the plugin yet? install it then click "run inline in claude" again.