Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

context-tree-use-checkpoint

Estrelas0

Forks0

Atualizado20 de julho de 2026 às 08:55

Use when a consequential next step depends on earlier session context and may need an independent checkpoint-derived reviewer, checker, oracle, reflector, or planner.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

zhexulong

zhexulong/evobuddy

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	context-tree-use-checkpoint
description	Use when a consequential next step depends on earlier session context and may need an independent checkpoint-derived reviewer, checker, oracle, reflector, or planner.

Context Tree Use Checkpoint

Before a consequential next step, consider requesting a checkpoint-derived agent.

Use this when all are true:

the next step is substantive;
it depends on earlier session decisions, failures, or rejected directions;
getting it wrong could cause meaningful rework or a false claim;
an independent reviewer, checker, oracle, reflector, or planner could change the next action.

Request shape:

checkpoint: <checkpoint id or boundary label>
role: reviewer | checker | oracle | reflector | planner
question: <decision question>
targets:
- <plan/spec/diff/report/file ref>

Do not decide what context to recover. Context Tree owns checkpoint recovery, material-path selection, writeback, and known-loss recording.

Mais deste repositório

mesmo repositório

context-tree-discover-members

zhexulong/evobuddy

Use when a project has no suitable confirmed member, a user asks to discover or import reusable experts, or repeated prior-session needs suggest a member candidate may exist.

2026-07-220

context-tree-save-checkpoint

zhexulong/evobuddy

Use when a user gives durable constraints or rejected directions, a session reaches a stable decision, compact/prune pressure appears, or future work may need to resume or branch from this point.

2026-07-220

context-tree-use-checkpoint

zhexulong/evobuddy

Use when a consequential next step depends on what happened earlier in the session and may need an independent checkpoint-derived reviewer, checker, oracle, reflector, or planner.

2026-07-220

context-tree-save-checkpoint

zhexulong/evobuddy

Use when a session reaches a durable boundary that future work may need to resume, review, or branch from.

2026-07-200

name	context-tree-use-checkpoint
description	Use when a consequential next step depends on earlier session context and may need an independent checkpoint-derived reviewer, checker, oracle, reflector, or planner.

Context Tree Use Checkpoint

Before a consequential next step, consider requesting a checkpoint-derived agent.

Use this when all are true:

the next step is substantive;
it depends on earlier session decisions, failures, or rejected directions;
getting it wrong could cause meaningful rework or a false claim;
an independent reviewer, checker, oracle, reflector, or planner could change the next action.

Request shape:

checkpoint: <checkpoint id or boundary label>
role: reviewer | checker | oracle | reflector | planner
question: <decision question>
targets:
- <plan/spec/diff/report/file ref>

Do not decide what context to recover. Context Tree owns checkpoint recovery, material-path selection, writeback, and known-loss recording.