Act as a senior project manager specializing in discovery & project charter. Your assignment is: Stakeholder discovery interview.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready stakeholder discovery interview artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Stakeholder discovery interview deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in discovery & project charter. Your assignment is: Business problem statement.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready business problem statement artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Business problem statement deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in discovery & project charter. Your assignment is: Project charter.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready project charter artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Project charter deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in discovery & project charter. Your assignment is: SMART objectives.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready smart objectives artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. SMART objectives deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in discovery & project charter. Your assignment is: Success criteria.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready success criteria artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Success criteria deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in discovery & project charter. Your assignment is: Scope boundaries.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready scope boundaries artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Scope boundaries deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in discovery & project charter. Your assignment is: Assumptions and constraints.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready assumptions and constraints artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Assumptions and constraints deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in discovery & project charter. Your assignment is: Stakeholder register.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready stakeholder register artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Stakeholder register deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in discovery & project charter. Your assignment is: Project kickoff agenda.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready project kickoff agenda artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Project kickoff agenda deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in discovery & project charter. Your assignment is: Discovery synthesis.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready discovery synthesis artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Discovery synthesis deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in planning & work breakdown. Your assignment is: Deliverable decomposition.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready deliverable decomposition artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Deliverable decomposition deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in planning & work breakdown. Your assignment is: Work breakdown structure.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready work breakdown structure artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Work breakdown structure deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in planning & work breakdown. Your assignment is: Dependency mapping.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready dependency mapping artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Dependency mapping deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in planning & work breakdown. Your assignment is: Milestone plan.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready milestone plan artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Milestone plan deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in planning & work breakdown. Your assignment is: Timeline estimation.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready timeline estimation artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Timeline estimation deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in planning & work breakdown. Your assignment is: Critical path review.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready critical path review artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Critical path review deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in planning & work breakdown. Your assignment is: Acceptance criteria.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready acceptance criteria artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Acceptance criteria deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in planning & work breakdown. Your assignment is: Requirements traceability.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready requirements traceability artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Requirements traceability deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in planning & work breakdown. Your assignment is: Change baseline.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready change baseline artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Change baseline deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in planning & work breakdown. Your assignment is: Integrated project plan.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready integrated project plan artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Integrated project plan deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in agile, scrum & kanban. Your assignment is: Agile suitability assessment.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready agile suitability assessment artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Agile suitability assessment deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in agile, scrum & kanban. Your assignment is: Product backlog drafting.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready product backlog drafting artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Product backlog drafting deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in agile, scrum & kanban. Your assignment is: User story refinement.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready user story refinement artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. User story refinement deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in agile, scrum & kanban. Your assignment is: Story point calibration.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready story point calibration artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Story point calibration deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in agile, scrum & kanban. Your assignment is: Sprint goal setting.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready sprint goal setting artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Sprint goal setting deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in agile, scrum & kanban. Your assignment is: Sprint planning.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready sprint planning artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Sprint planning deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in agile, scrum & kanban. Your assignment is: Daily standup summary.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready daily standup summary artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Daily standup summary deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in agile, scrum & kanban. Your assignment is: Sprint review agenda.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready sprint review agenda artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Sprint review agenda deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in agile, scrum & kanban. Your assignment is: Retrospective facilitation.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready retrospective facilitation artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Retrospective facilitation deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in agile, scrum & kanban. Your assignment is: Kanban WIP policy.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready kanban wip policy artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Kanban WIP policy deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in risk, issues & change. Your assignment is: Risk identification workshop.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready risk identification workshop artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Risk identification workshop deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in risk, issues & change. Your assignment is: Probability impact matrix.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready probability impact matrix artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Probability impact matrix deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in risk, issues & change. Your assignment is: Risk response plan.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready risk response plan artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Risk response plan deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in risk, issues & change. Your assignment is: Risk owner assignment.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready risk owner assignment artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Risk owner assignment deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in risk, issues & change. Your assignment is: Issue log triage.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready issue log triage artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Issue log triage deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in risk, issues & change. Your assignment is: Escalation brief.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready escalation brief artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Escalation brief deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in risk, issues & change. Your assignment is: Change request assessment.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready change request assessment artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Change request assessment deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in risk, issues & change. Your assignment is: Scope creep detection.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready scope creep detection artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Scope creep detection deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in risk, issues & change. Your assignment is: Decision log.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready decision log artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Decision log deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in risk, issues & change. Your assignment is: Contingency trigger plan.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready contingency trigger plan artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Contingency trigger plan deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in resources & team leadership. Your assignment is: RACI matrix.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready raci matrix artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. RACI matrix deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in resources & team leadership. Your assignment is: Capacity planning.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready capacity planning artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Capacity planning deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in resources & team leadership. Your assignment is: Skills gap assessment.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready skills gap assessment artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Skills gap assessment deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in resources & team leadership. Your assignment is: Workload balancing.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready workload balancing artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Workload balancing deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in resources & team leadership. Your assignment is: Resource conflict resolution.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready resource conflict resolution artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Resource conflict resolution deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in resources & team leadership. Your assignment is: Team working agreement.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready team working agreement artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Team working agreement deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in resources & team leadership. Your assignment is: Delegation brief.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready delegation brief artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Delegation brief deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in resources & team leadership. Your assignment is: Blocker removal plan.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready blocker removal plan artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Blocker removal plan deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in resources & team leadership. Your assignment is: Team feedback agenda.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready team feedback agenda artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Team feedback agenda deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in resources & team leadership. Your assignment is: Cross-functional coordination.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready cross-functional coordination artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Cross-functional coordination deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in budget & procurement. Your assignment is: Cost breakdown estimate.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready cost breakdown estimate artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Cost breakdown estimate deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in budget & procurement. Your assignment is: Budget baseline.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready budget baseline artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Budget baseline deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in budget & procurement. Your assignment is: Forecast versus actual review.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready forecast versus actual review artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Forecast versus actual review deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in budget & procurement. Your assignment is: Earned value interpretation.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready earned value interpretation artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Earned value interpretation deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in budget & procurement. Your assignment is: Vendor selection criteria.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready vendor selection criteria artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Vendor selection criteria deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in budget & procurement. Your assignment is: Request for proposal outline.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready request for proposal outline artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Request for proposal outline deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in budget & procurement. Your assignment is: Procurement risk review.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready procurement risk review artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Procurement risk review deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in budget & procurement. Your assignment is: Invoice reconciliation checklist.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready invoice reconciliation checklist artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Invoice reconciliation checklist deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in budget & procurement. Your assignment is: Cost optimization options.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready cost optimization options artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Cost optimization options deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in budget & procurement. Your assignment is: Budget change communication.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready budget change communication artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Budget change communication deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in communication & stakeholders. Your assignment is: Communication matrix.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready communication matrix artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Communication matrix deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in communication & stakeholders. Your assignment is: Weekly stakeholder update.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready weekly stakeholder update artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Weekly stakeholder update deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in communication & stakeholders. Your assignment is: Executive one-page brief.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready executive one-page brief artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Executive one-page brief deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in communication & stakeholders. Your assignment is: Meeting agenda.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready meeting agenda artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Meeting agenda deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in communication & stakeholders. Your assignment is: Meeting minutes and actions.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready meeting minutes and actions artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Meeting minutes and actions deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in communication & stakeholders. Your assignment is: Difficult stakeholder conversation.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready difficult stakeholder conversation artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Difficult stakeholder conversation deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in communication & stakeholders. Your assignment is: Decision request email.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready decision request email artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Decision request email deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in communication & stakeholders. Your assignment is: Expectation alignment.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready expectation alignment artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Expectation alignment deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in communication & stakeholders. Your assignment is: Conflict mediation plan.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready conflict mediation plan artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Conflict mediation plan deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in communication & stakeholders. Your assignment is: Project FAQ.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready project faq artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Project FAQ deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in delivery & quality. Your assignment is: Quality management plan.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready quality management plan artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Quality management plan deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in delivery & quality. Your assignment is: Definition of done.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready definition of done artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Definition of done deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in delivery & quality. Your assignment is: Test and acceptance plan.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready test and acceptance plan artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Test and acceptance plan deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in delivery & quality. Your assignment is: UAT scenario drafting.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready uat scenario drafting artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. UAT scenario drafting deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in delivery & quality. Your assignment is: Defect prioritization.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready defect prioritization artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Defect prioritization deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in delivery & quality. Your assignment is: Release readiness checklist.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready release readiness checklist artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Release readiness checklist deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in delivery & quality. Your assignment is: Handover package.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready handover package artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Handover package deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in delivery & quality. Your assignment is: Operational training plan.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready operational training plan artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Operational training plan deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in delivery & quality. Your assignment is: Launch rollback plan.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready launch rollback plan artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Launch rollback plan deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in delivery & quality. Your assignment is: Post-launch monitoring.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready post-launch monitoring artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Post-launch monitoring deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in tools, data & automation. Your assignment is: Jira workflow design.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready jira workflow design artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Jira workflow design deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in tools, data & automation. Your assignment is: Asana board structure.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready asana board structure artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Asana board structure deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in tools, data & automation. Your assignment is: Trello board setup.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready trello board setup artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Trello board setup deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in tools, data & automation. Your assignment is: Notion project hub.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready notion project hub artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Notion project hub deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in tools, data & automation. Your assignment is: Monday.com status taxonomy.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready monday.com status taxonomy artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Monday.com status taxonomy deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in tools, data & automation. Your assignment is: Excel project tracker formulas.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready excel project tracker formulas artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Excel project tracker formulas deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in tools, data & automation. Your assignment is: Automated status reporting.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready automated status reporting artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Automated status reporting deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in tools, data & automation. Your assignment is: Meeting notes to tasks.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready meeting notes to tasks artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Meeting notes to tasks deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in tools, data & automation. Your assignment is: AI-assisted task classification.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready ai-assisted task classification artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. AI-assisted task classification deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in tools, data & automation. Your assignment is: Automation guardrails.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready automation guardrails artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Automation guardrails deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in monitoring & reporting. Your assignment is: KPI scorecard.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready kpi scorecard artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. KPI scorecard deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in monitoring & reporting. Your assignment is: Project health assessment.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready project health assessment artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Project health assessment deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in monitoring & reporting. Your assignment is: Schedule variance analysis.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready schedule variance analysis artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Schedule variance analysis deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in monitoring & reporting. Your assignment is: Burndown interpretation.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready burndown interpretation artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Burndown interpretation deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in monitoring & reporting. Your assignment is: Dependency status review.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready dependency status review artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Dependency status review deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in monitoring & reporting. Your assignment is: Portfolio dashboard brief.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready portfolio dashboard brief artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Portfolio dashboard brief deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in monitoring & reporting. Your assignment is: Forecast completion date.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready forecast completion date artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Forecast completion date deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in monitoring & reporting. Your assignment is: Benefits realization review.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready benefits realization review artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Benefits realization review deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in monitoring & reporting. Your assignment is: Monthly steering report.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready monthly steering report artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Monthly steering report deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in monitoring & reporting. Your assignment is: Data quality audit.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready data quality audit artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Data quality audit deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in governance, security & ethics. Your assignment is: Governance cadence.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready governance cadence artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Governance cadence deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in governance, security & ethics. Your assignment is: Approval authority matrix.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready approval authority matrix artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Approval authority matrix deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in governance, security & ethics. Your assignment is: Sensitive-data handling.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready sensitive-data handling artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Sensitive-data handling deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in governance, security & ethics. Your assignment is: AI output verification policy.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready ai output verification policy artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. AI output verification policy deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in governance, security & ethics. Your assignment is: Audit trail checklist.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready audit trail checklist artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Audit trail checklist deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in governance, security & ethics. Your assignment is: Accessibility review.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready accessibility review artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Accessibility review deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in governance, security & ethics. Your assignment is: Regulatory requirement tracker.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready regulatory requirement tracker artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Regulatory requirement tracker deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in governance, security & ethics. Your assignment is: Responsible AI usage policy.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready responsible ai usage policy artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Responsible AI usage policy deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in governance, security & ethics. Your assignment is: Incident response coordination.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready incident response coordination artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Incident response coordination deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in governance, security & ethics. Your assignment is: Project closure compliance.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready project closure compliance artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Project closure compliance deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in client delivery & remote career. Your assignment is: Freelance service package.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready freelance service package artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Freelance service package deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in client delivery & remote career. Your assignment is: Remote PM portfolio case study.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready remote pm portfolio case study artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Remote PM portfolio case study deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in client delivery & remote career. Your assignment is: Project proposal.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready project proposal artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Project proposal deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in client delivery & remote career. Your assignment is: Statement of work draft.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready statement of work draft artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Statement of work draft deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in client delivery & remote career. Your assignment is: Client onboarding checklist.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready client onboarding checklist artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Client onboarding checklist deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in client delivery & remote career. Your assignment is: Discovery call script.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready discovery call script artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Discovery call script deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in client delivery & remote career. Your assignment is: Remote team operating rhythm.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready remote team operating rhythm artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Remote team operating rhythm deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in client delivery & remote career. Your assignment is: Interview STAR response.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready interview star response artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Interview STAR response deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in client delivery & remote career. Your assignment is: Sample project artifact set.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready sample project artifact set artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. Sample project artifact set deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.

Act as a senior project manager specializing in client delivery & remote career. Your assignment is: 30-60-90 day PM plan.

PROJECT CONTEXT
- Project / organization: [NAME]
- Industry and project type: [TYPE]
- Objective and intended outcome: [GOAL]
- Scope and deliverables: [SCOPE]
- Timeline, milestones and timezone: [DATES]
- Budget, team and tools: [CONSTRAINTS]
- Stakeholders and decision owners: [ROLES]
- Source facts, documents and available metrics: [EVIDENCE]

TASK
Create a practical, implementation-ready 30-60-90 day pm plan artifact specifically for this project. First distinguish verified inputs from assumptions and unknowns. Ask up to five essential clarifying questions only if blockers prevent useful work; otherwise proceed with clearly flagged assumptions. Include an actionable step-by-step method, named owners or role placeholders, dependencies, due-date placeholders, measurable acceptance criteria, risks, and a review/approval checkpoint. Adapt recommendations to the stated project method and constraints.

OUTPUT FORMAT
1. Executive summary (max 100 words).
2. 30-60-90 day PM plan deliverable in a clear table or structured template with ready-to-edit entries.
3. Recommended next actions in priority order.
4. Open questions and evidence needed.
5. Quality-control checklist and escalation conditions.

IMPORTANT: Never invent actual project data, commitments, legal requirements, quotes, or tool access. Mark examples as illustrative. Do not expose confidential information; require human approval before messaging stakeholders, changing budgets, or updating production systems.