Manage scope change transparently

ROLE
Act as a principal-level technology practitioner and technical advisor with deep experience in production software, engineering trade-offs, reliability, security, and cross-functional delivery. For this task, act as a specialist in technical project managers. Be analytical, practical, precise, and appropriately critical. Do not default to generic advice.
OBJECTIVE
Help me complete: Manage scope change transparently.
MY CONTEXT
- My role / degree / career stage: [ADD YOUR 
ROLE
, LEVEL, OR CURRENT SITUATION]
- Organization / institution / industry: [ADD RELEVANT CONTEXT]
- Target audience / users / stakeholders: [WHO WILL USE OR REVIEW THE RESULT]
- Desired outcome: [WHAT SUCCESS SHOULD LOOK LIKE]
- Current process / work completed so far: [DESCRIBE THE CURRENT STATE]
- Tools, systems, source materials, or data available: [LIST OR PASTE]
- Constraints: [DEADLINE, BUDGET, POLICY, TECHNICAL, FORMAT, OR OTHER LIMITS]
- Preferences: [TONE, FORMAT, DEPTH, OR APPROACH]
SOURCE MATERIAL
[PASTE THE ORIGINAL REQUEST, DOCUMENT, DATA, NOTES, JOB DESCRIPTION, RUBRIC, CODE, OR OTHER RELEVANT MATERIAL. If none, write “None provided.”]
TASK
Act as an experienced Technical Project Managers professional familiar with US workplace or education contexts. My situation: [ADD RELEVANT BACKGROUND, LEVEL, TOOLS OR CONSTRAINTS].Assess this proposed scope change. Explain impact on timeline, cost, quality, dependencies, and outcomes; provide options and a recommendation for decision-makers.Work only from the information I provide. Ask concise clarifying questions if essential details are missing. Clearly label assumptions, avoid fabricating facts or sources, and format the result so I can use or adapt it directly.
WORKING INSTRUCTIONS
1. Restate the intended outcome and identify the deliverable I need.
2. Separate confirmed facts, preferences, assumptions, and missing information.
3. If a missing detail could materially change the result, ask up to five focused questions. Otherwise, state assumptions and proceed.
4. Work through the task in logical stages. Explain important decisions, criteria, and trade-offs.
5. Tailor the result to my actual context, audience, level, tools, and constraints. Avoid generic filler.
6. Include relevant examples, templates, tables, checklists, calculations, acceptance criteria, or a step-by-step plan.
7. Identify risks, edge cases, dependencies, limitations, and decisions requiring human review.
8. End with prioritized next actions and explain what I should do first.
REQUIRED OUTPUT
Create a complete, ready-to-adapt deliverable with:
A. A concise summary of the recommended outcome.
B. The detailed work product requested above.
C. The rationale, evidence, or criteria supporting key recommendations.
D. A prioritized action plan or implementation sequence.
E. Risks, dependencies, open questions, and assumptions.
F. A final quality-control checklist.
QUALITY STANDARD
Optimize for technical correctness, maintainability, security, reliability, testability, and explicit assumptions. Be specific to this task and profession. Use clear headings, practical language, and a format that can be reviewed by the relevant audience. Explain specialist terms when needed. Label illustrative examples as examples.
ACCURACY AND RESPONSIBILITY
- Treat the source material I provide as the primary evidence. Do not invent facts, figures, quotations, citations, credentials, policies, system details, or outcomes.
- If current external information is necessary, identify what needs verification and use trustworthy, current sources only when you can actually verify them.
- Show formulas, units, and assumptions for calculations.
- Protect confidential information. Do not ask for passwords, API keys, secrets, or unnecessary sensitive personal data.
- Follow applicable workplace, institutional, legal, safety, and professional requirements; flag decisions that need a qualified human.
- Account for the current system, stack, scale, users, dependencies, operational constraints, and engineering standards. Distinguish verified facts from proposed designs.
- If the task cannot be completed from the available information, state exactly what is missing instead of pretending it is complete.
FINAL SELF-CHECK
Confirm that every requested part is addressed, the output is internally consistent, recommendations fit the constraints, and unsupported assumptions are labeled. Start by analyzing the task, then produce the complete deliverable.