spec_driven_development.specify

To write user stories for feature planning, define the primary user types and structure requirements as 'As a..., I want..., So that...'. You then establish testable acceptance criteria and scope boundaries to clarify what to build and why without implementation details.

A technology-agnostic specification defines functional requirements and feature design without committing to specific technology choices. You need it for product planning and governance reviews to ensure clear communication of what to build across technical and non-technical teams.

Creating formal specifications from feature ideas requires naming the feature and identifying primary user types. By answering guided questions, you draft a complete spec focusing on user stories, non-functional considerations, and constitutional governance principles.

Yes, you can align product specs with governance principles by reflecting constitutional principles directly within structured requirements. This approach enforces a technology-agnostic stance and ensures compliance during governance reviews without dictating implementation.

No, you do not need technical implementation details to define functional requirements. This specification process explicitly requires no implementation details, focusing entirely on the what and why to enable clear communication and testable acceptance criteria.

The best way to structure feature specs for governance reviews is to use standard-form user stories paired with structured acceptance criteria. This technology-agnostic format keeps specs focused on functional requirements and constitutional compliance for product planning.