Skip to content
Skills Library
Management & product · Analysis

024-context-mapping

/024-context-mapping

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

Repository
plinth ↗
Licence
Apache-2.0
Last repository change
21.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

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

Original author description

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

How it works

  1. Constraints
  2. When to use this skill
  3. Workflow
  4. Reference
Original SKILL.md headings · 61 lines, 395 words
SKILL.md preview
---
name: 024-context-mapping
description: 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
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.19.0
---
# 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

1. **Read the Reference**

Read `references/024-context-mapping.md`, then review the problem frame for systems already implicated by the problem.

2. **Identify Existing Systems**

List existing systems that already touch the problem area, including systems that are affected but not expected to change.

3. **Map Integrations**

Identify integrations and data flows between the identified systems.

4. **Name Ownership**

Name an owning team or role for each identified system or integration when known.

5. **Identify External Dependencies**

Identify third-party services, other teams, or contracts outside the team's direct control that the problem or its resolution depends on.

6. **Report the Context Map**

Report Existing systems, Integrations, Ownership, and External dependencies, and flag any item left open pending a clarifying answer.

## Reference

For detailed guidance, examples, and constraints, see [references/024-context-mapping.md](references/024-context-mapping.md).
Files in this package (2)
  • SKILL.md 3 KB
  • references/024-context-mapping.md 6 KB

Versions

The database has no other skills named 024-context-mapping.

Database snapshot: 13.11.2026 · package version e8bfb06268f4 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100025-quality-attribute-discovery
    Use when a problem under exploration needs its quality attributes (non-functional requirements) identified and prioritized before architecture and design begin. This should trigger when an issue's Quality Attribute Discovery point of view needs evaluation, or when a maintainer…
  • 100021-problem-framing
    Use when a problem or issue needs explicit framing before deeper analysis begins — establishing the Problem statement, Current state, Desired state, Stakeholders, and Success criteria. This should trigger when an issue's Problem Framing point of view needs evaluation, or when a…
  • 100022-root-cause-analysis
    Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This should trigger when an issue's Root Cause Analysis point of view needs evaluation, or when…
  • 100ecosystem-map
    Map the full ecosystem of actors, systems, and relationships surrounding the user — to understand the broader context the solution must fit into. Use when the sprint topic touches multiple integrated systems or data sources, when the team suspects hidden technical constraints…
  • 100product-discovery
    Use when starting a new feature or initiative and you need problem context, prior art, and acceptance criteria before design — the DISCOVER phase entry point — pulling Jira/Confluence context and synthesizing a discovery brief to validate problem framing
  • 100discovering-context
    Use when a goal is big, vague, or dependency-heavy and you need to map every piece of context required before planning — "map the context", "what context do I need", "build a context graph/DAG", "what do I need to know before I can plan this", "discover the dependencies first

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.