ericlitman/open-pstack

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Apply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references first, then build on the simpler base.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming…

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Configure pstack's provider-qualified models, per-family requested effort, and parent-owned routes per role. Verifies native and external Claude, Codex, and Grok lanes before writing the override sheet. Use for /setup-pstack, "configure pstack models", or changing pstack's model choices.

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping…

ericlitman/open-pstack

Skill Claude CodeCodex

Part of pstack

Fan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.