# Cops Npc Pressure Map

> Use when mapping how COPS NPCs, factions, and hierarchy pressures evolved around the current chronicle state. Focus on relationship changes, obligations, leverage, loyalties, fear, and unresolved pressure rather than general biography.

- Skill: `ludofleury/cops-npc-pressure-map` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add ludofleury/cops-npc-pressure-map`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ludofleury/cops-npc-pressure-map/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ludofleury (https://skillmd.com/u/ludofleury)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/ludofleury/cops-npc-pressure-map

---


# COPS NPC Pressure Map

This skill extracts the social and political state of a chronicle cluster.

Its job is to explain:

- how key NPCs relate to each other now
- what changed in those relationships
- what each person or group is under pressure from
- what payouts, debts, fears, loyalties, or institutional constraints are in
  play

It is especially useful for a focus group such as Epsilon, Obsidian, hierarchy,
or any specific chronicle cluster.

## When to use

Use this skill when the user asks for any of:

- NPC relationship evolution
- faction pressure mapping
- who is under pressure from what
- who owes what to whom
- what the hierarchy wants now
- how a group's internal or external dynamics changed

## Required input

Prefer receiving a continuity bundle from:

- `/Users/ludovicfleury/.codex/skills/previously-in-cops/SKILL.md`

If no bundle exists yet, reconstruct one briefly from live Notion and local
continuity before mapping.

Always check:

- `/Users/ludovicfleury/Documents/RPG/lore/chronicle-memory.md`

## Focus rule

Work on the specified cluster first.

Possible focus clusters:

- a group such as `Groupe Epsilon`
- another team such as `Obsidian` if present in the chronicle
- hierarchy around a leader
- one NPC surrounded by their pressure network

If the user does not specify a cluster, default to the most active group around
the current campaign point.

## What to map

For each key person or institution, identify:

- current role
- current alignment
- relationship change
- pressure source
- what they want now
- what they fear now
- what they may demand, hide, protect, or sabotage
- what changed recently because of table play or user correction

## Output style

Prefer a compact state map over prose biography.

Suggested structure:

- `Focus cluster`
- `What changed`
- `Pressure map`

Under `Pressure map`, use short entries like:

- `Name or group`
- `Current relationship`
- `Pressure / debt / leverage`
- `Likely movement`

## Synthesis rule

Do not stop at explicit statements.
Track implications from:

- scenario choices
- promotions or demotions
- transfers
- exposure
- shame
- institutional need
- hidden loyalties
- failed cover-ups
- favors and unpaid costs

The point is to reveal what is moving under the surface now.

## Guardrails

- Do not write biographies.
- Do not flatten a relationship to `ally` or `enemy` if it is more unstable.
- Do not ignore hierarchy, bureaucracy, or political cost.
- Do not forget that tiny incidents can change trust and leverage dramatically.
- Do not miss updated pressure that exists in local chronicle memory even if
  Notion has not caught up.

Think of this skill as:

continuity bundle in,
relationship pressure map out.