Use when a problem under exploration needs its surrounding system context identified before design begins — Existing systems, Integrations, Ownership, and External dependencies. This should trigger when an issue's Context Mapping point of view needs evaluation, or when a maintainer directly asks to map the systems, integrations, owners, and external dependencies relevant to a problem. Part of Plinth Toolkit
SkillScore86Maintained
Automatic
◆Product Management pack
Last verified 8/20/2026
What it changes
Passed 19 of 22 test cases with the skill, and 16 of 22 without it.
Without skill73%
With skill86%
Checks it passed that the model alone missed
Identifies Okta as an external dependency.
Includes the accounting auditing system in the system list despite it only reading data.
Flags the ownership of the cellular gateway provider as an open gap needing clarification.
and 6 more in the full report
6 fixed13 passed either way0 still failing3 broke
Pass-rate lift
+14 pp
Tokens
-16%
Agent turns
0%
Response time
-38%
Model gemini-3.6-flashMeasured 8/20/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
We are adding a new SMS notifications feature for user password resets. The brief states that our auth service triggers the notifications, but also mentions our audit logger service, customer support portal, and cellular gateway provider (Twilio). We know Security Ops owns auth service and Customer Success owns the support portal, but data flows and gateway ownership are omitted. Provide a context mapping breakdown for this change.
What was checked, without and with the skill
Checked
Without skill
With skill
Includes the audit logger service in the system breakdown even though it is not changing.
Passed
Passed
Flags the ownership of the cellular gateway provider as an open gap needing clarification.
Missed
Passed
Classifies Twilio as an external dependency outside direct team control.
Passed
Passed
case-03 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md60 lines2 files
Context Mapping
Guide identification of Existing systems, Integrations, Ownership, and External dependencies relevant to a problem under exploration. This is an interactive SKILL.
What is covered in this Skill?
Identifying existing systems that already touch the problem area
Mapping integrations and data flows between those systems
Naming ownership: who operates, maintains, or is accountable for each system or integration
Identifying external dependencies (third-party services, other teams, contracts) outside the team's direct control
Feeding context-mapping findings into 025-quality-attribute-discovery and the remaining Functional Specification lenses
Constraints
Map the surrounding context before any design decision assumes a system boundary. When this technique is orchestrated by another workflow, the orchestrator owns clarifying-question sequencing; when applied standalone, ask directly.
MUST read references/024-context-mapping.md before applying Context Mapping guidance
MUST identify existing systems that already touch the problem area, not only the system expected to change
MUST identify integrations and data flows between the identified systems
MUST name an owner (team or role) for each identified system or integration when known
MUST identify external dependencies outside the team's direct control, such as third-party services, other teams, or contracts
MUST NOT invent a system, integration, owner, or external dependency when the available content is vague or ambiguous; flag the gap for a clarifying question instead
When to use this skill
Map the systems and integrations around this problem
Identify ownership for these systems
List the external dependencies for this issue
Apply context mapping before design begins
Draft the Context Mapping section of a Functional Specification
Workflow
Read the Reference
Read references/024-context-mapping.md, then review the problem frame for systems already implicated by the problem.
Identify Existing Systems
List existing systems that already touch the problem area, including systems that are affected but not expected to change.
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Gen