product-capability

To translate product intent into engineering constraints, you generate a canonical capability contract that explicitly defines invariants, interfaces, and decisions before development starts. This separates user-visible promises from implementation details to clarify architecture.

A capability artifact is a structured document containing a capability summary, constraints, implementation contract, and open questions. You need one for cross-team roadmaps or PRDs where actionable specifications are missing or ambiguous, reducing rework across teams.

You turn ambiguous PRDs into actionable specifications by applying a capability contract that captures constraints, interfaces, and unresolved questions. This produces a canonical artifact with handoff guidance, making alignment explicit before multi-service work begins.

This approach works for founder notes, roadmaps, and PRDs alike. You provide the product intent and any existing capability context to generate a complete artifact, making it suitable for any stage where explicit constraints and decisions are needed.

The best way to separate user-visible promises from implementation details is to define a capability contract that explicitly captures invariants and interfaces. This clarifies policy and architecture choices while yielding a durable capability plan.

Multi-service development fails without explicit capability constraints because invariants, interfaces, and decisions remain ambiguous. Generating a canonical capability artifact makes unresolved questions explicit and provides handoff guidance, preventing misalignment and rework.