Menú
Plan coding work before editing. Use for "make a plan for", "plan this", "decompose", and similar requests.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
How changes are classified, gated, approved, committed, and shipped in the Lamprey Harness repo. Load this BEFORE making any change — code, docs, config, or release — or when you see terms like P-SPR, STS, verify gate, era-lock, commit trailer, push policy, or when a commit/push is rejected by a hook.
How Lamprey runs and ships — run modes, userData layout, Windows release artifacts, the one-command "Bucket" pipeline, macOS/Linux CI mirroring, GitHub publication, CDN purge, and failure recovery. Load when the user says "ship", "release", "tag it", "Bucket", or when a release step fails partway.
The multi-provider LLM domain pack for Lamprey — OpenAI-compatible streaming across 17 built-in providers (frontier labs, open-source hosts, keyless local runtimes) plus user-defined custom endpoints, per-provider quirks (reasoning field names, Anthropic's compat-layer limits, base-URL overrides), capability flags, the native-vs-fallback tool-calling contract, retry/backoff, retired-model handling, and the checklists for adding a model or a provider. Load when touching electron/services/providers/, debugging provider HTTP errors, or adding/retiring models.
Lamprey's load-bearing design decisions, the invariants that must hold, what was deliberately deleted, and the honestly-stated weak points. Load before modifying electron/ipc, electron/services, the provider or tool layers, or the renderer stores — or when you need to know WHY the system is shaped the way it is.
Recreate the Lamprey dev environment from scratch and get past its known traps — Node/Electron/better-sqlite3 ABI story, the ELECTRON_EXEC_PATH dev-server workaround, esbuild antivirus blocks, the tsconfig node/web split, electron-vite and electron-builder specifics. Load when setting up a machine, when npm install / dev server / build fails, or before touching build configuration.
Catalog of every Lamprey configuration axis — AppSettings keys with defaults and readers, inert retired keys, keychain/keys.json, custom models, loop and timeout knobs, environment variables, per-conversation runtime state — plus the exact checklist for adding a setting without breaking the parity-lock test. Load when reading/changing settings.json, adding a setting, or wondering what a flag does or whether anything still reads it.
| name | Plan |
| description | Plan coding work before editing. Use for "make a plan for", "plan this", "decompose", and similar requests. |
| triggers | ["make a plan for","plan this","decompose"] |
Use this skill when the user wants a plan, decomposition, or implementation outline before code changes.
First call workspace_context to establish the active root, git state, package scripts, frameworks, instruction files, and likely verification commands. Read any listed instruction files that are relevant to the request before finalizing the plan.
Create or update the visible checklist with update_plan. Keep exactly one step in_progress at a time. Steps should be concrete actions, not vague phases: name the files or areas involved when known, and include the verification step as its own item.
Do not edit files unless the user explicitly asks you to proceed. If the plan depends on an unknown decision, state the assumption and keep moving when the risk is low; ask one focused question only when a wrong assumption would waste work or endanger user data.
Stop when the plan is actionable, ordered, and short enough for the user to approve or amend.
