product-capability

To translate a PRD into a capability plan, you provide the product intent document to generate a concrete contract exposing constraints, invariants, interfaces, and unresolved decisions for multi-service engineering handoff.

A capability plan formalizes product intent into a durable contract exposing constraints and interfaces. You need one when a feature spans multiple teams and services requiring a durable contract to prevent ambiguity.

You extract explicit constraints and invariants from a roadmap item by processing the product intent to output a formal capability summary, actors, states, transitions, and data-model implications.

Yes, you can use founder notes to generate a formal implementation contract. The skill processes these informal inputs to produce structured artifacts including security constraints, observability requirements, and open questions.

Yes, the capability plan handles security policy constraints and observability requirements. It extracts these alongside lifecycle transitions and data ownership details to reduce rework across engineering teams.

The best way to document open questions before handoff is to generate a structured capability plan that explicitly lists unresolved decisions alongside actors, surfaces, and required state transitions for engineering lanes.