product-capability

A capability contract exposes business rules, invariants, scope boundaries, trust boundaries, data ownership, and migration needs upfront. It also defines actors, surfaces, states, interfaces, and governance constraints to prevent ambiguity before multi-service work starts.

Generating a capability contract from roadmap items involves restating the ask into a precise capability summary, resolving constraints, and defining implementation interfaces and data models. This produces a ready-to-implement artifact for downstream engineering lanes.

Yes, you can use a capability contract to clarify open decisions across multiple repos by explicitly capturing unresolved questions and trust boundaries. It generates a durable artifact ensuring all downstream services share the same constraints and governance logic.

The best way to document data implications and interfaces is to generate an SRS-style capability plan covering data models, state transitions, and surface interfaces. This durable artifact captures governance constraints and open questions for future reuse across harnesses.

Yes, this approach works without external dependencies by taking raw PRDs, roadmap asks, or founder notes as input. It processes the ambiguous product intent directly to output a structured capability contract clarifying invariants and migration needs.