context-diagram

Create system context diagrams defining boundaries, external entities, and data flows.

23|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/jdm4pku/RE-Skills --skill context-diagram-jdm4pku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-diagram
Source: https://github.com/jdm4pku/RE-Skills/tree/main/skills/context-diagram
Command: npx skills add https://github.com/jdm4pku/RE-Skills --skill context-diagram-jdm4pku

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about context-diagram

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a context diagram for a software system?▼

Draw the system as a single bubble, place every external entity (users, external systems, devices, organizations) around it as rectangles, then add labeled directional arrows for each data flow. Validate that every entity has at least one flow and every flow has a descriptive noun-phrase name.

What is the difference between a context diagram and a Level 0 DFD?▼

A context diagram shows the system as one bubble with only external entities and flows. A Level 0 DFD decomposes that bubble into major internal processes and data stores. Every external flow on the context diagram must also appear on the Level 0 DFD, a property called balancing.

How do context diagrams help derive software requirements?▼

Each incoming data flow generates input validation, format, and trigger requirements, while each outgoing flow generates content, format, timing, and destination requirements. Each external entity implies a user class or interface specification that must be documented.

What are common mistakes when drawing a context diagram?▼

Common pitfalls include drawing multiple system bubbles, decomposing internal processes too early, leaving data flows unlabeled, forgetting bidirectional flows for entities, and never updating the diagram after elicitation reveals new interfaces.

When should I use an ecosystem map instead of a context diagram?▼

Use an ecosystem map when you need to show interactions among many systems across an enterprise before narrowing to your own system boundary. A context diagram is the right choice once you focus on a single system and its direct external interfaces.