菜单
When you finish a plan file in active/, automatically move it to completed/. If it's the last plan in its set, move the whole set. Use when completing any plan under .llm/plans/active/.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Canonical linear DB migrations under infra/k8s/base/ops/source/database/linear-migrations, ops bundles, env keys, and runners. Use when adding or changing SQL migrations, K8s DB bootstrap, or scripts/database in this repo.
When an E2E test verifies a specific element, pass it to the capture helper so the step screenshot is taken with that element vertically centered.
Create and use Metaboost git worktrees in sibling directories named metaboost_<branch_slug> (underscores). Use when starting feature work, moving WIP off the main checkout, or opening the correct worktree path for a branch.
Distributed tracing and OTLP export patterns. Use when adding trace context, log correlation, or Observability env — after Metaboost adopts a shared observability package.
User vocabulary abcmemory and abcremember — where Cursor guidance lives and how to persist new instructions. Use when the user says abcmemory or abcremember.
Common patterns for the Metaboost HTTP API (Express)
| name | plan-completion |
| description | When you finish a plan file in active/, automatically move it to completed/. If it's the last plan in its set, move the whole set. Use when completing any plan under .llm/plans/active/. |
When you finish executing a plan file that lives in .llm/plans/active/, archive it (and
optionally its whole set) without asking the user.
Metaboost also enforces COPY-PASTA progress tracking via the plan-execution-completion-tracking rule — follow both this skill and that rule during plan-set execution.
active/ to completed/, preserving subdirectory structure.COPY-PASTA.md to mark the corresponding agent prompt [x] (per
plan-execution-completion-tracking).Example:
mv .llm/plans/active/metaboost-podverse-parity-gaps/03-adopt-podverse-engineering-ops-skills.md \
.llm/plans/completed/metaboost-podverse-parity-gaps/
A set is any group of plan files that belong together, for example:
00-EXECUTION-ORDER.md or COPY-PASTA.md.md files under one active/<feature>/ directoryIf the plan you just finished is the last numbered plan in that set (no other numbered plans
remain in active/<feature>/), move all remaining plan-set files from active/<feature>/ to
completed/<feature>/ in one go. Preserve directory structure.
Keep COPY-PASTA.md and 00-* files in active/ until all numbered prompts are complete; then move
the whole directory.
Example (last plan in set):
mv .llm/plans/active/metaboost-podverse-parity-gaps .llm/plans/completed/
Always keep the same relative path under completed/ as under active/:
active/feature-name/01-part.md → completed/feature-name/01-part.mdIf .llm/LLM.md, LLM-PLANS-ACTIVE.md, or a 00-SUMMARY.md references the moved plan(s), update
paths from active/ to completed/ where appropriate.
When completing the last numbered prompt in a set:
| Situation | Action |
|---|---|
| Finished one plan in a set | Move only that plan file to completed/; mark [x] in COPY-PASTA |
| Finished the last plan in a set | Move the whole set directory to completed/ |
| Last plan in set (COPY-PASTA) | End response with all cumulative operator verification commands for the whole set (see response-ending-make-verify) |
| Don't ask | Archive automatically after the plan is done |
Dedupe verification commands across the set; order: build/lint → unit → API (if applicable) → E2E
(if applicable). Default E2E commands without E2E_API_GATE_MODE unless API code changed.