AGENT SKILL

compact

Write the resume point in docs/resume.md, every ruling verbatim, so the context can be compacted without losing anything. Use when the context window is half full or more, or when the user asks to compact or for a resume point; not after every merge. Last step of the methodical loop. Not for the compound write-up.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 0
Forks
0

01 前言 Front Matter

name
compact
description
Write the resume point in docs/resume.md, every ruling verbatim, so the context can be compacted without losing anything. Use when the context window is half full or more, or when the user asks to compact or for a resume point; not after every merge. Last step of the methodical loop. Not for the compound write-up.

03 SKILL.md 正文

Compact

Say Step: compact before anything else.

First, the compound check

If the host handles this request through its native compaction adapter, let the adapter own the action. Otherwise, check whether this stretch solved anything non-obvious that is not yet written up. Say in one sentence what you will do, never ask, and do it: if something is outstanding, run /methodical:compound checkpoint (it writes the write-ups, resume point and verified production checkpoint); if nothing is, say so in one line and run it anyway, because it writes no write-up and still finishes the handoff. Either way, checkpoint performs this skill's "How", so skip its duplicate writes. "Just compact" or another direct decline skips compounding and proceeds to the host's compact action; never force a replacement checkpoint, approval question or new user exchange after a decline.

Where the adapter intercepts compact or /compact, it uses a verified current handoff immediately or asks one question if the handoff is stale. It is not an offered skip: the user's own words or Esc compact as is, without another question. A menu choice or explicit request to compound and compact runs the checkpoint and then native compaction. The offer plugin option turns the question and offers off. Only a successful runtime finalizer with matching on-disk records establishes currency. Hosts without chaining use their supported manual compact action as described in the overlay.

What it produces

docs/resume.md (or docs/private/resume.md; read ${METHODICAL_ROOT}/rules/user-words.md and follow it), overwritten each time with the current state:

  • Where things are: the branch, the base commit, the last commit, what is merged.
  • Next action: the step the loop is on and the first thing to do on resuming.
  • Rulings: every ruling the user has given that is still in force, verbatim, with its date and what it rules on. Why: the summary a compaction writes is a paraphrase.
  • Open findings and owed items: review findings not yet fixed, open questions waiting on a ruling, entries in docs/device-verification-queue.md.

Write rulings into the resume point the moment they are given, not only at this step. Why: a compaction can happen before this step runs, and anything only in the chat is gone after it.

Where the user's words go

Read ${METHODICAL_ROOT}/rules/user-words.md and follow it before writing the user's words to any file.

How

  1. If a unit is in flight (not yet merged), record its in-flight state and commit it on the current branch.
  2. Write the resume point and commit its tracked files, honoring the private-location rule.
  3. Complete compound checkpoint's final publication using ${METHODICAL_ROOT}/reference/native-routing.md: prepare the explicit Work input and use the overlay's checkpoint-finalize as the final tool call. Proceed only on its successful current receipt.
  4. Tell the user the resume point is written and that they can run the host's manual compact action now. Only an already-requested Claude Code chain may run /compact for them. Why: compacting at half the window keeps headroom for the summary, and the resume point means nothing depends on what the summary keeps.

On resuming in a new or compacted session, read docs/resume.md before anything else, then announce the step it names.

When it hands on

The host owns the compact action. An already-requested native chain runs it after finalization. On hosts that require a manual action, the user runs it from the composer, using /compact where supported. The loop starts again at Step: brainstorm with the next unit, or at the step the resume point names.

04 同仓库更多 Skills

BigLeverVentures
BigLeverVentures/methodical-gated-engineering

phrase-outside

暂无简介

★ 0
BigLeverVentures
BigLeverVentures/methodical-gated-engineering

named-only

暂无简介

★ 0
BigLeverVentures
BigLeverVentures/methodical-gated-engineering

work

Build an approved plan from docs/plans/ on its own short-lived branch, or a change the user said to make without a plan. Use when a plan reads state: approved and the user wants it built, when resuming such a build, or when the user has waived the plan for a named change. Work step of the methodical loop. Not when no approved plan exists and the user has not waived one (run the plan step), and not for reviewing finished work.

★ 0
BigLeverVentures
BigLeverVentures/methodical-gated-engineering

work-review

Review a finished build on its branch against its plan, with reviewer seats matched to the code's language, before it merges. Use when the work step's tests pass and the plan's approach is done, or when the user asks for a review of a branch's changes. Work-review step of the methodical loop. Not for reviewing a plan.

★ 0
BigLeverVentures
BigLeverVentures/methodical-gated-engineering

plan

Write the plan file in docs/plans/ that code changes get before building, unless the user has said to build without one. Use when the user asks to build, fix, edit or change code and docs/plans/ has no approved plan for it, or when a plan must be revised after review. Plan step of the methodical loop. Not for questions or reading code, and not when the user has waived the plan for this change (go to work).

★ 0
BigLeverVentures
BigLeverVentures/methodical-gated-engineering

plan-review

Review a plan in docs/plans/ with reviewer seats matched to the project's language, before the user approves it. Use when a plan has just been written or deepened, when a plan was revised after review, or when the user asks for a plan review. Plan-review step of the methodical loop. Not for reviewing built code.

★ 0