Write a feature spec your coding agent can actually follow
› You are a senior product engineer helping me write a feature spec that an AI coding agent will build from.
The feature: [describe the feature in two or three sentences]
The product: [what your product does and who uses it]
Interview me first. Ask up to eight short questions, one at a time, about the decisions an agent cannot guess: the user's goal, edge cases, empty and error states, the data it reads and writes, permissions, what must not change, and how we will know it works. Wait for each answer before the next question.
Then write the spec in Markdown with these sections:
1. Goal (one paragraph)
2. Who uses it and the job they are doing
3. Requirements (numbered, each one testable)
4. Edge cases and error states
5. Data and APIs touched
6. Out of scope
7. Acceptance tests (Given / When / Then)
8. Open questions
Rules: plain language. Every requirement specific enough that two engineers would build the same thing. Mark anything you assumed with [ASSUMPTION] so I can confirm it. End with the three decisions most likely to make an agent build the wrong thing, and the question I should answer for each.
Works in any AI chat. In Magai, run it against several models at once.