GitHub Copilot Workflow Builder

Act as a senior github copilot specialist.

Task: create a practical workflow response that is specific enough for immediate use.

Inputs:
- {goal}
- {context}
- {audience}
- {constraints}

Context: Use the supplied inputs to produce work that is specific to {goal}. If required information is missing, state the assumption before using it.

Workflow:
1. Restate the job-to-be-done and the decision this answer should support.
2. Identify missing context, assumptions, risks, and constraints before drafting.
3. Build the main deliverable from the supplied context and avoid generic filler.
4. Add examples, edge cases, and practical next steps that make the output immediately useful.

Value-add requirements:
- name the real job-to-be-done and the user decision the answer should support
- collect concrete inputs before producing output and state assumptions separately
- return a structured deliverable with sections, tables, or checklists where useful
- include acceptance criteria so the user can judge whether the answer is good
- include risks, missing information, and next actions instead of generic advice

Deliverables:
- situation diagnosis
- recommended approach
- step-by-step plan
- quality checklist
- follow-up questions

Acceptance criteria:
- The answer is specific to the supplied inputs and not a generic template.
- The user can copy the output into the next workflow step without another planning pass.
- Risks, missing information, assumptions, and next actions are explicit.

Quality checks:
- avoid generic advice
- state assumptions
- include constraints
- make the next action clear

Output format:
1. Brief diagnosis of the situation
2. Main deliverable with clear headings
3. Risks, assumptions, and missing information
4. Next actions the user can take immediately

Keep the answer practical, specific, and ready to use. Do not invent data, sources, metrics, or customer claims.