# Operator New

> Initialize Operator Mode for this repository and maintain PROJECT_STATUS.md as working memory.

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

---


# Operator Mode (/operator-new)

You are being asked to initialize Operator Mode in the CURRENT repository.

Operator Mode uses a single persistent file as working memory:

PROJECT_STATUS.md (at the repo root)

This file is NOT documentation.  
It is working memory.

Treat it as the authoritative source for resuming work after context resets.

---

## Step 1 — Create or repair PROJECT_STATUS.md

Check whether PROJECT_STATUS.md exists at the repo root.

- If it does NOT exist → create it using the template below.
- If it DOES exist → ensure it follows this structure and normalize headings without deleting user content.

### PROJECT_STATUS.md Structure (Must Match)

# Project Status

## Intent
- The outcome we are trying to create.
- What success looks like (quality bar, not tasks).

## Overview
- 1–3 bullets describing the current direction.

## Recent work
- High-signal summary of meaningful progress.
- Reference files/functions by path/name only.
- Do NOT paste large content.

## In-progress
Active work mid-stream. Capture only what is needed to resume cleanly.

For each item include:

- Task: the objective being completed
- Progress: what has already been done
- Remaining: the work left to finish
- Next action: the immediate step to take next

Avoid narrative history.  
Avoid duplicating information found in source files.  
This section is a restart checkpoint, not a log.

## Next up
- The smallest concrete actions required to move forward.
- Write these so a fresh Claude instance can resume immediately.

## Risks / questions
- Unknowns, assumptions, or decisions needing human input.

## Parking lot
- Things intentionally NOT being worked right now.

---

## Step 2 — Read PROJECT_STATUS.md before any work

After creating or repairing the file, open and read PROJECT_STATUS.md fully.  
Do not begin task work until it is aligned.

---

## Step 3 — Operating Principles (Apply Throughout the Session)

PROJECT_STATUS.md is the single source of continuity.

Favor:
- Brevity over completeness
- Decisions over descriptions
- Direction over history

Never paste large code blocks into PROJECT_STATUS.md.  
Always summarize.

This file should remain readable in one screen.

---

## Step 4 — When To Update PROJECT_STATUS.md

Refresh PROJECT_STATUS.md whenever:

- A meaningful chunk of work completes
- You are about to begin a new subtask or refactor
- The conversation is becoming long or context-heavy
- You detect potential context compaction/reset
- You are unsure whether future-you would understand the state

Context discipline:

- Around ~70% context → pause and update PROJECT_STATUS.md
- Around ~90% context → do not begin new work; finalize status alignment only

---

## Step 5 — If PROJECT_STATUS.md Becomes Bloated

Rewrite PROJECT_STATUS.md to reduce length by ~40% while preserving:

- Intent
- Active work
- Immediate next steps

Delete historical narrative.  
Do not introduce new information.

This is a memory compaction step, not a summary.

---

## Behavioral Anchor

You are not acting as a project manager.

You are acting as an execution partner maintaining directional memory  
so work can continue cleanly across resets.

The goal is sustained velocity with minimal structure.