Write a migration ledger entry for a configuration schema change in pipelex, so that a user's existing file can be repaired instead of thrown away. Use when make check-migration-schemas (alias cmig) or make check-ledger (alias cl) refuses a change, when the user says "add a migration", "write the ledger entry", "the…
Add a new AI model to the Pipelex inference system. Guides through all required steps: backend TOML configuration (OpenAI, Azure, Anthropic, Google, etc.), kit sync, test profile collections, and fixture regeneration. Use when the user says "add a model", "add GPT-X", "add Claude X", "new model", "register a model"…
Move this repo's exact mthds dependency pin to the latest release on PyPI (or a version you name), re-lock, adapt the engine source to whatever the new release broke, run the checks, and write the CHANGELOG entry — stopping before the commit. Use whenever the user says "bump mthds", "update mthds", "upgrade mthds"…
Use whenever writing, editing, or debugging Beagle source in any project: files with a current Beagle extension (beagle langs --view extensions), files beginning with #lang beagle, or anything under /code/beagle. Establishes proportional authoring-loop health, typed-Lisp semantic leverage, strict foreign boundaries…
Detailed graph-edit verbs, lossless projection commands, relational program reads, Datalog entry points, and scope limits for code-as-facts. Load when code-as-facts-distilled routes here or the user explicitly requests details.
Detailed Beagle Store RPC commands, recursive Term and occurrence semantics, paging limits, query relations, generated-source authority, and executable examples. Load when store-modeling-distilled routes here or the user explicitly requests those details.
Implement an existing plan from docs/agents/plans/. Use when the user asks to implement, execute, resume, or continue a plan, or references a plan file — the plan's Status line must be updated on completion.
Create an implementation plan for any task — feature, refactor, migration, fix — and save it to docs/agents/plans/. Use when the user asks to plan work, write an implementation plan, or prepare a task spec for claude/codex. (Implementing an existing plan is the implement-plan skill, not this one.).
Final-polish pass on the current PR or feature branch before it lands. Rebases on origin/main, force-pushes, drives CI to green, then reviews the diff for correctness/perf/security/reliability bugs, flaky test patterns banned by make lint-test-patterns, sloppy comments a senior engineer would not write, cross-crate…