| { |
| "absolute_id": 158, |
| "persona": "Operations Manager", |
| "task": "Based on the operations team's division of responsibilities and the three user communication records about the latest product in the communication records folder, summarize a future work plan for the operations team. Prioritize tasks, provide concrete implementation plans, list the to-do items, support the team's future work, and output `operations_team_work_plan.md`.", |
| "task_diff": "hard", |
| "output_files": [ |
| "operations_team_work_plan.md" |
| ], |
| "rubrics": [ |
| "Does the output file exist and have the name `operations_team_work_plan.md`?", |
| "Does the output file include a background and demand-summary section that organizes all 11 user needs from record one, record two, and record three?", |
| "Does the output file clearly divide the four demand priority levels of P0 (critical), P1 (high), P2 (medium), and P3 (low)?", |
| "Are the two P0 critical-priority needs in the output file system-stability issue follow-up and implementation of the global dashboard requirement?", |
| "Does the output file include a table of operations-team division of labor and corresponding responsibilities, clearly showing the responsible modules for departments such as Customer Success Operations and Product Operations?", |
| "Does the system-stability issue follow-up clearly assign joint responsibility to the Customer Success Operations Department and the Data Operations Department, with completion required within one month?", |
| "Does the output file include a to-do list organized by department, covering the five departments of Customer Success Operations, Product Operations, Growth Operations, Data Operations, and Content Operations?", |
| "Does the Customer Success Operations Department to-do list include calling Wang Lei back to understand the details of the stability issue, and is it marked as P0 priority?", |
| "Does the Product Operations Department to-do list include interviewing Wang Lei to clarify the detailed requirements for the global dashboard?", |
| "Does the output file include a follow-up and review mechanism section clearly defining three mechanisms: weekly stand-up meetings, monthly reviews, and demand-closure tracking?", |
| "Does the output file include a performance metrics section listing four measurable indicators: paid-customer satisfaction, requirement implementation rate, conversion rate, and retention rate?", |
| "Do the performance metrics explicitly require that P0 and P1 requirements achieve a 100% implementation rate within the planned timeframe?", |
| "Does the plan fully record the three needs proposed by Zhang Min, namely Gantt chart view, `@all`, and cross-team shared links?", |
| "Is Zhang Min's request for a Gantt chart view placed under P1 high priority?", |
| "Is Wang Lei's request for a time-tracking function recorded and placed under P1 priority?", |
| "Is Chen Ya's request for on-demand storage expansion in the free version recorded and placed under P2 priority?", |
| "Is Chen Ya's request for third-party cloud-drive integration recorded and placed under P3 priority?", |
| "Are Chen Ya's two requests for online preview and annotation of PSD/AI files and visitor permissions recorded and placed under P2 priority?", |
| "Does every priority level of work task clearly include specific implementation steps and time requirements?", |
| "In the to-do list, does every task clearly specify the owner, priority, and deadline?", |
| "Does the plan integrate all user feedback from the three communication records without omitting any explicitly proposed requirement?", |
| "Does the work plan assign a corresponding responsible department to every requirement?" |
| ], |
| "rubric_types": [ |
| "Basic Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Process Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Process Evaluation", |
| "Outcome Evaluation", |
| "Process Evaluation", |
| "Outcome Evaluation" |
| ], |
| "file_dep_graph": [ |
| { |
| "from": "record_one.md", |
| "to": "operations_team_work_plan.md" |
| }, |
| { |
| "from": "record_two.md", |
| "to": "operations_team_work_plan.md" |
| }, |
| { |
| "from": "record_three.md", |
| "to": "operations_team_work_plan.md" |
| } |
| ], |
| "data_manifest": [ |
| { |
| "filename": "record_two.md", |
| "stored_relpath": "data/eb88b7aa5a6164c3_record_two.md" |
| }, |
| { |
| "filename": "record_three.md", |
| "stored_relpath": "data/f89a6c12a6add15f_record_three.md" |
| }, |
| { |
| "filename": "record_one.md", |
| "stored_relpath": "data/31899ead25a0cb4c_record_one.md" |
| } |
| ], |
| "tested_capabilities": [ |
| "Workspace Exploration", |
| "Task-Providing File Utilization", |
| "Lineage Tracing", |
| "Semantic Content Relations Understanding" |
| ] |
| } |
|
|