product-capability

To translate product intent into engineering constraints, define capability contracts that specify invariants, interfaces, and policy boundaries. This ensures multi-service architectures align with system-level implementation requirements before coding begins.

An implementation contract is an SRS-style plan detailing actors, surfaces, and state transitions. You need one when a new feature spans multiple services and teams require durable technical artifacts to align product vision with implementation.

Extract architectural invariants and data ownership rules by analyzing product notes to identify business rules, trust boundaries, and unresolved decisions. This constraint extraction process reveals hidden technical requirements before implementation starts.

Yes, capability planning aligns multiple teams by generating explicit engineering constraints and implementation-ready plans. Defining policy boundaries and interfaces ensures all teams share a durable technical artifact for complex feature development.

The best way to define interfaces and state transitions is generating an SRS-style implementation contract. This document explicitly maps actors, surfaces, and state transitions to satisfy system-level implementation requirements across services.

Avoid capability planning for simple, single-service features that do not require multi-service architectural alignment. It is designed for complex feature development needing explicit invariants, trust boundaries, and policy definitions.