contract-generation

You can generate API contracts and shared TypeScript types from Gherkin scenarios by executing an automated contract generation workflow that parses feature increment specifications to output stable contract sets for parallel development.

Automated API contract generation is used to create shared types and infrastructure definitions from feature specifications, providing a stable foundation that enables parallel frontend and backend implementation without integration conflicts.

Yes, you can use automated contract generation for parallel frontend and backend development because it produces comprehensive, increment-aligned shared types and infrastructure definitions that ensure both slices work together seamlessly.

Yes, you need Gherkin scenarios and other specification documents as input because the automated contract generation operates within a feature-based workflow to derive infrastructure definitions and shared types from those exact specifications.

The best way to align API contracts with a feature increment is to automate contract generation from the increment's Gherkin scenarios, ensuring that all generated shared types and infrastructure definitions match the scoped features exactly.