Office Productivity Task Management

Prompt

Please help me generate progress reports for 3 parallel projects (Alpha/Beta/Gamma):

1. Review calendar/events.json to find the relevant meetings for each project
2. Read action items from notes/meetings.json for the meeting notes linked to each project
3. Check to-do completion status in todo/tasks.json
4. Look up project lead contact information in contacts/contacts.json
5. Produce a progress report for each of the 3 projects, marking risk items
6. Save the final combined report as JSON to output/progress_report.json

Expected Behavior

Alpha Project (~75% progress, on track)

• Meetings: evt_601 (requirements review 3/17) + evt_602 (technical design 3/20)
• Notes: NOTE-601 (3 action items: 2 done + 1 in-progress) + NOTE-602 (2 action items: 1 done + 1 not started)
• To-dos: TODO-601 ✓, TODO-602 ✓, TODO-603 in_progress, TODO-604 ✓ → 3/4 done = 75%
• Leads: Wang Ming (project manager), Li Hua (architect), Ma Qiang (ops)
• Risk: TODO-603 (technical feasibility report, due 3/25) still in progress; microservice architecture plan depends on it

Beta Project (~45% progress, delayed, high risk)

• Meetings: evt_603 (kickoff 3/18) + evt_604 (progress check 3/22)
• Notes: NOTE-603 (3 items: 1 done + 1 in-progress + 1 blocked) + NOTE-604 (2 items: both pending, 1 overdue)
• To-dos: TODO-605 ✓, TODO-606 in_progress, TODO-607 pending/blocked, TODO-608 pending, TODO-609 in_progress → 1/5 = 20% task done rate
• Leads: Zhao Lei (product manager), Zhang Wei (backend dev), Zhou Ming (frontend dev)
• Critical risks: TODO-607 frontend prototype blocked (waiting for third-party API docs, overdue 3/22); TODO-608 API dev depends on incomplete DB design; ~1 week behind

Gamma Project (~90%+, near completion)

• Meetings: evt_605 (client meeting 3/19) + evt_606 (delivery review 3/24, no meeting notes!)
• Notes: NOTE-605 (2 items: both done); evt_606 has no corresponding notes
• To-dos: TODO-610 ✓, TODO-611 ✓, TODO-612 ✓ → 3/3 done = 100%
• Leads: Wang Ming (project manager), Zhao Lei (product manager)
• Notable: evt_606 (3/24 delivery review) is missing notes — needs follow-up

Grading Criteria

• Read all 4 data files: calendar, notes, todo, contacts (tool usage gate — see penalties below)
• Correctly classified meetings across Alpha/Beta/Gamma (evt_601–606)
• Identified that evt_606 (Gamma delivery review) has no meeting notes
• Alpha progress ~75% with TODO-603 as the risk item
• Beta project identified as delayed/high-risk with the third-party API block as core bottleneck
• Gamma project near completion (~90%+)
• Lead contact information included for each project
• Risk annotations present in the reports

Tool usage gate (automated, multiplicative penalties):

• < 3 of 5 notes read (NOTE-601–605) → ×0.5
• Todos not queried → ×0.5
• Contacts not queried → ×0.6
• Calendar not queried → ×0.6

Workspace Files

• assets/T041_claweval_T150_project_progress_report/calendar/events.json -> calendar/events.json
• assets/T041_claweval_T150_project_progress_report/notes/meetings.json -> notes/meetings.json
• assets/T041_claweval_T150_project_progress_report/todo/tasks.json -> todo/tasks.json
• assets/T041_claweval_T150_project_progress_report/contacts/contacts.json -> contacts/contacts.json

Platform Delivery

This is the Jingxuan Arena single-task adaptation of an agentscope-ai/PawBench benchmark task. Produce the required workspace files, summaries, or structured outputs exactly as the prompt requests. Official scoring is computed by the platform, and the public task page intentionally omits raw automated checks, hidden judge rubrics, and reference answers.

Task Metadata

• Source: PawBench v1.0
• Source Dataset: ClawEval
• Source Task ID: T150_project_progress_report
• Grading Type: Hybrid
• Timeout: 300 seconds
• Scenario: Office Productivity Task Management
• Capabilities: Tool Use, Planning, Logic Reasoning, Math Computation, Self Verification
• Complexity: L3
• Environment: Closed
• Modality: Text