# Cops Previously Lines

> Use when turning COPS continuity material into clear 'what happened previously' lines. Summarize the latest relevant scenario state, major consequences, and small details with outsized impact without overloading the recap.

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

---


# COPS Previously Lines

This skill turns a continuity bundle into a clean `what happened previously`
block.

Its purpose is not to retell the whole campaign.
Its purpose is to remind the user what actually matters now.

## When to use

Use this skill when the user asks for any of:

- `what happened previously`
- recap lines
- a short chronicle reminder
- what matters now in the main line
- what political or institutional state the chronicle is in

## 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 writing.

Always check:

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

## What to keep

Always keep:

- the latest relevant scenario point
- the main line that defines the current state of play
- institutional or political shifts that matter now
- small details that created a large consequence later
- what the players changed
- what still has to be paid off
- any table-confirmed correction that changes active continuity

## What to avoid

- full lore retelling
- scene-by-scene recap
- only giant headlines with no subtle but decisive detail
- loaded dramatic prose when a precise line would do

## Output style

Keep the output readable and light.

Preferred structure:

- `Where we are now`
- `Previously`
- 5 to 10 bullets max

Good recap bullets:

- are one or two lines
- show cause and effect
- separate major arc movement from small but dangerous details
- make it easy to remember who owes what, fears what, or is cornered by what

## Synthesis rule

Balance three layers:

1. main line
2. political / institutional state
3. small details with outsized future impact

If a small detail changed relationships, leverage, timing, trust, or exposure,
it belongs in the recap even if it looked minor in the original scene.

## Guardrails

- Do not overload.
- Do not omit subtle details that now shape the chronicle.
- Do not make every bullet sound equally important.
- Do not confuse recap with teaser writing.

Think of this skill as:

continuity bundle in,
clear `previously` lines out.