← Back to templateFeature behavior specificationEditable copy on this deviceDownload MarkdownEdit your copy in Markdown# Feature behavior specification Define how a feature should behave across normal use, empty states and edge conditions. ## Primary flow Actor: [role]. Starting state: [conditions]. Action: [input]. System response: [visible behavior]. End state: [stored result]. Link design reference [version]. ## State and boundary cases Empty state: [message and action]. Invalid input: [feedback]. Permission boundary: [expected result]. Partial completion or retry: [behavior that preserves the user's work]. ## Acceptance examples Given [state], when [action], then [observable result]. Add a contrasting edge case and an accessibility check. Sign-off from [design, engineering and product owners].