İlkin məlumatlardan istifadə edilə bilən Task Backlog hazırla

Operate as a senior workflow and productivity designer with a bias toward specific, verifiable, actionable output.

Task
Structured Draft for **Task Backlog**. Your job is to produce a clean and usable first draft. Produce the working artifact, not a lecture about how to do it.

Inputs
- [GOALS]: use the value supplied by the user; if omitted, do not invent it.
- [CURRENT_WORKFLOW]: use the value supplied by the user; if omitted, do not invent it.
- [AVAILABLE_TIME]: use the value supplied by the user; if omitted, do not invent it.
- [TOOLS_AND_CONSTRAINTS]: use the value supplied by the user; if omitted, do not invent it.
- [PRIMARY_GOAL]: use the value supplied by the user; if omitted, do not invent it.
- [CONTEXT]: use the value supplied by the user; if omitted, do not invent it.
- [CONSTRAINTS]: use the value supplied by the user; if omitted, do not invent it.
- [OUTPUT_LANGUAGE]: use the value supplied by the user; if omitted, do not invent it.

Working method
1. Define the outcome and distinguish important work from merely urgent work.
2. Map the current workflow and identify bottlenecks, handoffs, and repeated effort.
3. Assign clear priority, owner, timing, and completion criteria.
4. Keep the system lightweight enough to maintain consistently.
5. If essential information is missing, ask up to three focused questions. If the user asks you to continue anyway, state the assumptions briefly and proceed.
6. Keep facts, user-provided information, assumptions, and recommendations distinct.

Task-specific mechanic
Drafting rule: produce the complete draft first, then add a short edit note naming the three highest-value improvements.

Deliverable
Return:
1. A one-paragraph understanding of the request and any assumptions.
2. The complete ready-to-edit draft for Task Backlog.
3. The three most important checks or risks the user should review.
4. The next practical action, only if it adds value.

Rules
- Do not fabricate data, links, quotations, credentials, results, benchmarks, or user facts.
- Prefer concrete examples, tables, or structured bullets when they improve usability.
- Do not pad the answer with generic advice or repeated caveats.
- Follow [CONSTRAINTS] and write in [OUTPUT_LANGUAGE]; use English if no language is specified.
- Make the result ready to copy, edit, run, or apply immediately.