What problem does it solve? Teams often discover missing interfaces and scope gaps mid-project because the system boundary was never clearly defined. This Skill produces a context diagram (DFD Level 0) that shows the system as a single bubble with every external entity and named data flow, so scope and interface requirements are captured up front. ## Core Features & Use Cases - Boundary Definition: Place the system as one bubble and identify all external entities (users, external systems, devices, organizations) with labeled, directional data flows. - Requirements Derivation: Convert every incoming and outgoing data flow into concrete input validation, output format, timing, and interface requirements. - Validation & Pitfall Checks: Apply a checklist covering single-bubble rules, named flows, bidirectional coverage, and balancing with Level 0 DFDs. - Use Case: A business analyst scoping a chemical inventory system maps Lab Technicians, an EHS Officer, the PubChem API, SSO, and a label printer around the system, then derives requirements like CAS validation and expiration alerts from each flow. ## Quick Start Ask the agent to create a context diagram for your system, listing all external entities and the data flows between them and the system.