# Cops Lapd Blues Synopsis Writer

> Use when writing or rewriting the LAPD Blues focus paragraph for a COPS scenario in Chronicle. Read the actual scenario page first, then explain in French what the scenario reveals about Warden, Groupe Epsilon, internal hierarchy pressure, and the specific ensemble dynamics that matter later in the chronicle.

- Skill: `ludofleury/cops-lapd-blues-synopsis-writer` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add ludofleury/cops-lapd-blues-synopsis-writer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ludofleury/cops-lapd-blues-synopsis-writer/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-lapd-blues-synopsis-writer

---


# COPS LAPD Blues Synopsis Writer

This skill writes the **second Chronicle block** that follows a scenario
synopsis: the `LAPD Blues` paragraph.

It is for **MJ-facing chronicle pages**, not for player teasers and not for cast
summaries.

The job of this paragraph is to explain:

- what the scenario reveals about **Groupe Epsilon**
- what it reveals about **Warden**
- how the **hierarchy** presses on them
- why that matters later in the chronicle

## When to use

Use this skill when the user asks for any of:

- a `LAPD Blues` block under a scenario synopsis
- a Chronicle paragraph focused on Epsilon or Warden
- a rewrite of a scenario paragraph that should explain the group impact
- a second paragraph like the one under `Des pains et des jeux`
- a synopsis focused on how a scenario affects Epsilon internally

## Required source discipline

Do not write this paragraph from memory if the scenario page exists.

Always do this first:

1. read the full scenario page
2. identify the `LAPD Blues`, `Rollcall`, dispatch, briefing, and office scenes
3. identify what the field investigation changes for Warden or Epsilon
4. only then write the paragraph

If the scenario page is thin on group material, use the visible hierarchy
pressure in the page before inferring anything broader.

## Source order

### 1. Scenario page first

Priority zones:

- `LAPD Blues`
- `COPS Channel`
- `Rollcall`
- dispatch / bureau / standby scenes
- scenes where the hierarchy interferes
- scenes where other services, unions, City Hall, or favored units create pressure
- late sections where ownership of the case changes

### 2. Epsilon/Warden lore second

If needed, then use:

- `/Users/ludovicfleury/Documents/RPG/lore/chronicle-memory.md`
- `/Users/ludovicfleury/Documents/RPG/lore/epsilon-overview.md`
- `/Users/ludovicfleury/Documents/RPG/lore/warden-arc.md`

Use lore only to sharpen interpretation, not to overwrite what the scenario page
actually shows.

## What the paragraph must do

Every `LAPD Blues` paragraph should make clear:

### 1. Group state

How Epsilon feels and functions in this scenario.

Examples:

- tired but cohesive
- scattered but still responsive
- politically exposed
- treated like cleanup crew
- split across ugly assignments

### 2. Warden's position

What Warden is doing here as leader.

Examples:

- holding the group together
- protecting the team from hierarchy pressure
- distributing work according to strengths and liabilities
- trying to convert work into leverage
- surviving under political punishment

### 3. Institutional pressure

What outside force bears down on the group in this scenario.

Examples:

- Skripnick
- Hawkins or the favored lane
- audits, commissions, unions
- other services trying to seize the file
- City Hall or prefect pressure

### 4. Chronicle value

Why this scenario matters to Epsilon later.

Examples:

- confirms the group identity
- shows Warden's limits
- hardens distrust of the institution
- opens a later gray-zone survival pattern
- changes how the players relate to the unit

## Style rules

- Write in French unless the user asks otherwise.
- Write one compact paragraph by default.
- Be narrative, not schematic.
- Write for an MJ who already knows the campaign world.
- Prefer group dynamics over cast inventory.
- Mention named NPC members only if they illuminate a real dynamic.
- Do not list half the squad just to prove the group exists.
- Do not turn the paragraph into a generic statement about bureaucracy.
- Do not flatten Warden into a martyr or mastermind.

## Bad patterns

Do not do this:

- a cast roll call disguised as analysis
- a paragraph that only says the group is under pressure
- a pure Warden biography detached from the scenario
- a pure hierarchy summary detached from the group
- a vague claim such as `this is where Epsilon becomes important`

## Good pattern

Use this internal progression:

1. what the scenario shows of the group in motion
2. what Warden is doing to keep it functional
3. what pressure bears on that function
4. what this locks in for the chronicle

This should feel like one story, not four bullet points.

## Quality check before sending

Before finalizing, test the draft:

- Does it describe Epsilon as seen in this scenario, not in general?
- Does it say something concrete about Warden's function here?
- Does it identify the relevant hierarchy pressure?
- Could an MJ remember why this scenario matters to Epsilon later?
- Does it avoid cataloguing NPCs?

If any answer is no, rewrite.

## Output mode for Chronicle

For Chronicle, place it as a second italic paragraph directly under the
scenario synopsis.

Use the opening tag:

- `*LAPD Blues. ...*`

Do not use:

- `Synopsis court`
- `Focus Epsilon`
- bullet points
- cast labels