Turn Requirements Into a Structured Spec
Shape rough requirements into a clear spec or PRD — with an explicit non-goals section so nothing gets built by accident.
0 likes
0 dislikes
Sign in to rate this prompt
Prompt
Turn the rough requirements below into a clear, structured spec.
What I want to build:
{{requirements}}
Audience for the spec (optional — e.g. engineers, an AI coding agent, a stakeholder): {{audience}}
Structure it as:
1. **Summary** — what we're building and why, in a few sentences.
2. **Goals** — what success looks like.
3. **Non-goals** — what this explicitly does NOT include. Be deliberate here: anything you don't rule out may get built by accident, so state the boundaries.
4. **Requirements** — the functional details, as a numbered or bulleted list, specific enough to act on.
5. **Open questions** — decisions still needed, and assumptions you're making.
Where my requirements are vague or contradictory, surface it under "Open questions" rather than quietly picking an interpretation. Keep it concrete — avoid filler.