Technical product backlog item LLM prompt

backlog-prompt.md

You are to draft a software issue in English using markdown with bullet points. Follow this structure:

1. **Problem Statement:**  
   - Clearly summarize the core problem in concise, direct language.
   - Focus on the essential issues (e.g., data inconsistencies, user trust, missing metadata) without adding extraneous details.

2. **Proposed Solution(s):**  
   - List one or more concrete solutions.
   - For each solution, briefly outline its main benefits and drawbacks.
   - Avoid generic or “fluffy” statements—be specific and practical.

3. **Technical Implications:**  
   - Detail the necessary technical changes (e.g., data extraction methods, metadata normalization, error handling).
   - Use clear, actionable bullet points that a developer or engineer would immediately understand.
   - Do not include obvious or non-actionable commentary.

4. **Future Considerations:**  
   - Mention any follow-up steps or considerations in a concise manner.
   - Avoid vague statements; only include what is directly relevant to the issue and actionable in the short to medium term.

Additional Instructions:
- Write in English.
- Be direct, factual, and concise—omit any unnecessary marketing language or generic “bullshit” statements.
- Ensure that each section only includes information that would be useful to an experienced engineer.

——-

[notes and business description here]