resume-context

Estrelas1

Forks0

Atualizado3 de junho de 2026 às 09:48

Use at the start or resume of any task (especially long or multi-session tasks) to load the lessonbook before acting — read the read-only control rules and approved lessons plus the task's working state, and surface the active constraints for this run. Use when starting/resuming work, picking up a long task, or when continuity across sessions matters. Do not use for one-shot factual lookups with no prior state.

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

zhjai

zhjai/agent-lessonbook

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	resume-context
description	Use at the start or resume of any task (especially long or multi-session tasks) to load the lessonbook before acting — read the read-only control rules and approved lessons plus the task's working state, and surface the active constraints for this run. Use when starting/resuming work, picking up a long task, or when continuity across sessions matters. Do not use for one-shot factual lookups with no prior state.
license	MIT
metadata	{"version":"0.3.1","author":"zhjai","tags":"lessonbook, resume, context, active-constraints, long-task, continuity","related_skills":"correction-capture, lesson-propose"}

Resume Context

When to use

Starting or resuming a task that has prior state, rules, or lessons.
Long / multi-session / multi-stage work where chat context is unreliable.

Procedure

Read control/rules.md (read-only authority — you must obey, cannot edit).
Read control/approved_lessons/index.yaml; pull the lessons relevant to this task by their summaries (load full lesson files only as needed — progressive disclosure).
Read the task's state/tasks/<task_id>/run_state.yaml (working memory — what was believed/done so far; not ground truth) and its correction_journal.md if present.
Produce an active_constraints list (from rules + relevant approved lessons + any journal entries from earlier in this task) and a short relevant_lessons summary.
If state/lessonbook/inbox.md ($LESSONBOOK_INBOX) has UNREVIEWED placeholders left by a PreCompact hook, surface them — they may hold a correction from before a compaction. Hand them to correction-capture to triage.
Any unmet precondition or open question → record it in state/tasks/<task_id>/run_state.yaml (do not silently proceed past it).

Outputs

Updated run_state.yaml (resume marker, active_constraints).
A short "active constraints + relevant lessons" summary for this session.

Do not

Do not treat run_state.yaml as proof a condition is met — it records belief, not verified state.
Do not edit control/. If a rule seems wrong, file a candidate_lessons proposal; do not change authority yourself.

Mais deste repositório

mesmo repositório

correction-capture

zhjai/agent-lessonbook

Use the moment evidence appears that should influence FUTURE execution and would be wrong for the worker to treat as authority on its own — a user correction/clarification ("actually…", "you skipped X again"), exposed drift (a check fails, a miss is pointed out), a proven repo pitfall, a "never do X" constraint, or an authority-relevant architecture constraint. Record it to the task's correction journal with a type, and add active ones to run_state constraints. Do not use for routine progress, or for things that belong in the repo (test commands, conventions, env) or built-in memory. Captures evidence when something exposes it; it does not make the agent notice drift on its own.

2026-06-031

lesson-propose

zhjai/agent-lessonbook

Use at task wrap-up, after a mistake, or on a postmortem to turn the correction journal and observations into review PROPOSALS — classify each candidate lesson by target tier (working-only / approved-lesson / policy / gate-candidate) and write a proposal note, without self-approving. Use when wrapping up, after something went wrong, or when a correction should persist. Do not grant a lesson authority — the worker proposes, a human promotes.

2026-06-031

name	resume-context
description	Use at the start or resume of any task (especially long or multi-session tasks) to load the lessonbook before acting — read the read-only control rules and approved lessons plus the task's working state, and surface the active constraints for this run. Use when starting/resuming work, picking up a long task, or when continuity across sessions matters. Do not use for one-shot factual lookups with no prior state.
license	MIT
metadata	{"version":"0.3.1","author":"zhjai","tags":"lessonbook, resume, context, active-constraints, long-task, continuity","related_skills":"correction-capture, lesson-propose"}

Resume Context

When to use

Starting or resuming a task that has prior state, rules, or lessons.
Long / multi-session / multi-stage work where chat context is unreliable.

Procedure

Read control/rules.md (read-only authority — you must obey, cannot edit).
Read control/approved_lessons/index.yaml; pull the lessons relevant to this task by their summaries (load full lesson files only as needed — progressive disclosure).
Read the task's state/tasks/<task_id>/run_state.yaml (working memory — what was believed/done so far; not ground truth) and its correction_journal.md if present.
Produce an active_constraints list (from rules + relevant approved lessons + any journal entries from earlier in this task) and a short relevant_lessons summary.
If state/lessonbook/inbox.md ($LESSONBOOK_INBOX) has UNREVIEWED placeholders left by a PreCompact hook, surface them — they may hold a correction from before a compaction. Hand them to correction-capture to triage.
Any unmet precondition or open question → record it in state/tasks/<task_id>/run_state.yaml (do not silently proceed past it).

Outputs

Updated run_state.yaml (resume marker, active_constraints).
A short "active constraints + relevant lessons" summary for this session.

Do not

Do not treat run_state.yaml as proof a condition is met — it records belief, not verified state.
Do not edit control/. If a rule seems wrong, file a candidate_lessons proposal; do not change authority yourself.