AI-Assisted Project Planning and Scheduling

Generate a Work Breakdown Structure for the following project:

Project: Implement an automated accounts payable system for a
mid-size manufacturing company.

Scope: Invoice intake, automated 3-way matching (PO/invoice/receipt),
digital approval workflow (2 levels), ERP integration (SAP),
vendor self-service portal.

Deliverables: Discovery and requirements (3 weeks), System design (2 weeks),
Development and configuration (8 weeks), Integration testing (3 weeks),
UAT (2 weeks), Training and go-live (2 weeks).

Team: 1 PM, 1 BA, 2 developers, 1 QA engineer, 0.5 IT architect,
vendor support.

Format: Level 1 (phases) + Level 2 (deliverables per phase) +
Level 3 (tasks per deliverable). Include estimated effort days per Level 3 task.
Flag any tasks with high dependency risk.

Here is the project schedule for the AP automation project:
[paste schedule]

Perform a risk-adjusted schedule analysis:

1. Identify the 5 tasks with the highest schedule risk
   (dependency density, external dependencies, team capacity assumptions)
2. For each: describe the risk and estimate a pessimistic duration
3. Model three scenarios:
   - Optimistic: everything goes as planned
   - Realistic: the 2 most likely risks materialize
   - Pessimistic: the 3 highest-impact risks materialize simultaneously
4. For each scenario: what is the impact on the overall delivery date?
5. Recommend 3 schedule buffers or mitigations to protect the critical path

Here is the project WBS with task estimates: [paste]
Here is the team composition: [paste]

Identify:
1. Resource allocation by person — total estimated days per team member
2. Weeks where any team member is allocated over 100% capacity
3. Critical path tasks where there is no backup if the assigned person
   is unavailable
4. Recommended allocation changes to reduce overallocation

Assumptions: 8-hour days, 4.5 working days per week (accounting for
meetings and admin). Flag any assumption you're making that I should validate.

Here are the project tasks for the AP automation implementation: [paste]

Map the dependencies:
1. External dependencies (tasks that require something from outside
   the project team — vendor deliverables, IT infrastructure, approvals)
2. Internal dependencies (task B cannot start until task A is complete)
3. Critical path — the longest sequence of dependent tasks
4. Tasks on the critical path with the highest uncertainty

Flag any external dependencies with a delivery risk in the
first 4 weeks of the project — these are the earliest schedule threats.

Draft a project charter for executive sponsor sign-off.

Project: AP Automation implementation
Business case: Reduce invoice processing from 8 days to 2 days average,
eliminate manual entry errors, support new CFO approval rule for $50k+ invoices.
Sponsor: CFO
PM: [name]
Budget: $350,000
Timeline: 6 months to go-live
Team: [list]

Include: problem statement, business objectives (measurable),
scope (in/out), key milestones, risks and mitigations,
success criteria, governance structure, decision authority.

Tone: executive audience. Length: 2 pages maximum.
No jargon. Every objective must be measurable.

Here are the completed task records from our last 3 projects,
showing estimated vs. actual hours per task type: [paste data]

Analyze:
1. Which task types are consistently under-estimated, and by what %?
2. Which phases of projects show the most schedule variance?
3. What patterns exist in the tasks that exceeded estimates
   (developer, QA, integration, vendor-dependent)?
4. What adjustment factors should I apply to similar estimates
   in future projects?