Feature Specification for Design and Engineering Handoff
Provide what designers and developers need.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Write a feature spec for handoff. Feature: [FEATURE]. User problem: [USER_PROBLEM]. Design mockups or descriptions: [DESIGNS]. Technical constraints: [TECH_CONSTRAINTS]. Produce: summary and purpose; user stories; screens and states (default, loading, empty, error, success); interactions and rules (validation, limits, copy text); data fields table: Field | Type | Required | Validation | Default | Notes; permissions; analytics events (name, trigger, properties); copy and error messages; accessibility notes; out of scope; open questions; and QA scenarios. Check the spec with a "ready to build" checklist: all states covered, copy final, data defined, events defined, dependencies identified. Rewrite vague lines into specific ones. Before "Show an error when invalid." After "If the email lacks an @, show 'Enter an email like name@example.com' below the field; keep the entered text." Use only my information; mark unknowns [VERIFY]. Add a short 'definition of ready' for this spec and a table of open questions with owner and due date. State which parts are final and which are still proposals so engineers do not build on a guess.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.