# Map Capability Dependencies

> Maps cross-team dependencies when asked what blocks delivery, who owns an input, or which decisions must happen first; records ownership and failure paths without inventing commitments.

- Skill: `jovanipink/map-capability-dependencies` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx get-skill add jovanipink/map-capability-dependencies`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jovanipink/map-capability-dependencies/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: JovaniPink (https://skillmd.com/u/jovanipink)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/jovanipink/map-capability-dependencies

---


# Cross-Capability Dependency Mapping

Use generic terminology and preserve the status of every material statement: observed fact, proposal, ratified decision, rejected decision, unresolved question, measured result, estimate, or causal claim.

## Workflow

1. Define the outcome and capability boundary being mapped.
2. Inventory capabilities, owners, inputs, outputs, contracts, data authority, platforms, and decision rights.
3. Classify dependencies as data, technical, process, policy, people, funding, vendor, or decision dependencies.
4. Record direction, criticality, lead time, confidence, failure effect, fallback, and evidence.
5. Identify cycles, single points of failure, shared bottlenecks, contested ownership, and unratified contracts.
6. Build a critical path and identify which dependencies can proceed in parallel.
7. Assign validation, escalation, and change-notification obligations to named owners.

## Boundaries

- Do not infer ownership from who last edited or operates a downstream copy.
- Do not publish private topology, identity, or contractual details in a public artifact.
- Do not treat a dependency map as authority to change another owner's system.

## Output

Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.

Return Capability map, Dependency register, Critical path, Ownership gaps, Failure paths, Parallel work, and Decisions needed.

## Example

Synthetic example; not an observed client result.

Input: A report launch needs a schema from one team and access approval from another.

Output: Schema delivery and access approval are separate dependencies. Record an owner and acceptance evidence for each before committing to the launch sequence.

