Skill: element-complete-summarization

[Case 2]

• Initial Environment: The agent receives a report about Marcin Wasniewski crashing into the back of a lorry on the A444 in Coventry. The report contains vivid but potentially distracting detail about the damaged car and the driver narrowly surviving.
• Real Question: Write a concise summary of the incident.
• Real Trajectory: The agent identifies the principal entity, the event, and the result, then compresses supporting detail while keeping the core outcome and logical relation intact.
• Real Answer: Marcin Wasniewski survived a crash on the A444 in Coventry after his car became embedded in a lorry, escaping with cuts and bruises despite severe vehicle damage.
• Why this demonstrates the capability: The source contains many striking details, but the summary must still privilege the core informational spine. The result is not merely that a crash happened; it is that the driver survived despite near-fatal damage. This case tests whether the agent can choose the right details under compression pressure.

Pipeline Execution Instructions

To synthesize data for this capability, you must strictly follow a 3-phase pipeline. Do not hallucinate steps. Read the corresponding reference file for each phase sequentially:

1. Phase 1: Environment Exploration Read the exploration guidelines to discover raw knowledge seeds: references/EXPLORATION.md

2. Phase 2: Trajectory Selection Once Phase 1 is complete, read the selection criteria to evaluate the trajectory: references/SELECTION.md

3. Phase 3: Data Synthesis Once a trajectory passes Phase 2, read the synthesis instructions to generate the final data: references/SYNTHESIS.md