024-context-mapping — Claude Code skill: map systems before design
024-context-mapping is a Claude Code skill that maps existing systems, integrations, owners, and external dependencies before design when system boundaries are undefined.
Apache-2.0 142 installs ★ 465 updated 2026-10-21
npx skills add jabrena/plinth --skill 024-context-mapping -a claude-codeWhat 024-context-mapping does
The skill is interactive: rather than generating a map immediately, the agent asks clarifying questions when the problem description is vague. If a system, integration, or owner cannot be found in the available material, the skill flags the gap instead of inventing an answer.
The workflow reads references/024-context-mapping.md first, then enumerates affected systems — including those not expected to change — maps data flows between them, and assigns an owning team or role to each one. The final step records external dependencies: third-party services, other teams, and contracts outside the team's direct control.
Output feeds into skill 025-quality-attribute-discovery and the remaining lenses of the Functional Specification. The skill is part of Plinth Toolkit v0.19.0, licensed under Apache-2.0.
What it helps with
- map existing systems and integrations around a problem before any design decision
- identify owners for each system and integration by team or role
- record external dependencies such as third-party services, contracts, and other teams
- draft the Context Mapping section of a Functional Specification
- pass the finished context map to the next Plinth Toolkit skill
Example prompts for the agent
- Map the context for this issue: existing systems, integrations, owners, and external dependencies
- Apply
024-context-mappingbefore we design anything and list all affected systems - Fill in the Context Mapping section of the Functional Specification for this ticket
How to install 024-context-mapping
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 024-context-mapping -a claude-code2Manually: put the files in place
~/.claude/skills/024-context-mapping/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/024-context-mapping/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 024-context-mapping -a codex2Manually: put the files in place
.agents/skills/024-context-mapping/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 024-context-mapping -a cursor2Manually: put the files in place
.cursor/skills/024-context-mapping/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth skills/024-context-mapping2Manually: put the files in place
.github/skills/024-context-mapping/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 024-context-mapping -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/024-context-mappingManually: put the files in place
.devin/skills/024-context-mapping/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 024-context-mapping -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 024-context-mapping
How do I install 024-context-mapping in Claude Code?
Run npx skills add jabrena/plinth --skill 024-context-mapping -a claude-code; the skill will be available at ~/.claude/skills/024-context-mapping/SKILL.md.
What does the 024-context-mapping skill do?
It guides an agent through identifying systems already touching a problem area, mapping data flows, naming owners, and listing external dependencies — all before any design work begins. The process is interactive, so the agent asks follow-up questions when information is missing.
What must be in the repository for this skill to work?
The file references/024-context-mapping.md must exist — the skill reads it as its first mandatory step. Without that file the context-mapping workflow will not proceed.
Source text
SKILL.md · Apache-2.0
--- 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).
© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth