Reframe A Rejection Email Into Useful Feedback For Yourself

You have had another rejection, and it reads exactly like the last one, all warmth and no specifics. This separates the boilerplate from anything genuinely about your piece, tells you plainly when there is nothing to read into, and gives you two practical next steps rather than false comfort. Good for writers submitting regularly who want a clear head, not a pep talk.

<context>
You submitted creative work (a story, a poem, a script) and received this rejection: {REJECTION_TEXT}. Most literary rejections are vague and unhelpful, but you want to extract whatever signal exists.
</context>
<task>
**Reframe the rejection into something useful:**
1. Separate boilerplate language (used on every rejection) from anything that sounds specific to your submission
2. If nothing specific exists, say so plainly rather than inventing meaning
3. Suggest two concrete next actions: where else this piece might suit, and one honest question to ask about the piece itself
4. Keep the tone steady and practical, not falsely encouraging
</task>
<output_format>
- A short breakdown of boilerplate versus signal
- Two concrete next steps
</output_format>