specify

A feature specification includes user stories, acceptance criteria, data models, edge cases, and test plans. It transforms vague requests into rigorous, unambiguous technical directives ready for development teams.

To ensure your technical spec aligns with project architecture and governance documents, the specification process analyzes your project's constitution, architecture constraints, and governance requirements to produce compliant, directly testable outputs.

The best way to generate acceptance criteria and test plans from a feature description is to parse the plain-English input to identify scope and edge cases, producing a rigorous specification designed to be directly testable by development teams.

Yes, you can use this to create a living spec that updates as requirements evolve. The output specification is designed to be modified as new constraints arise, ensuring your technical documentation remains continuously accurate.

Generating a feature spec does not strictly require predefined data models as inputs, but supplying project architecture and governance documents ensures the output specification is fully compliant and implementable with minimal back-and-forth.