avn-context-reset
Keep a PROGRESS.md for long tasks and move to a fresh session or subagent that reads only that file when the context gets long or stale. Use when a task spans many steps or sessions, when the model starts repeating itself, forgets earlier facts, or re-tries old fixes, or when the context window is past about half full.
- License 许可
- MIT
- 所属仓库
- Aeven-AI/Aeven
- 最近更新
- 2026-11-15
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- avn-context-reset
- description
- Keep a PROGRESS.md for long tasks and move to a fresh session or subagent that reads only that file when the context gets long or stale. Use when a task spans many steps or sessions, when the model starts repeating itself, forgets earlier facts, or re-tries old fixes, or when the context window is past about half full.
02 资源文件 1
- 许可证LICENSE1.0 KB
03 SKILL.md 正文
avn-context-reset
Store the state of the work in a file, not in the chat, so a fresh context can continue without drift.
Steps
- At the start of a long task, create PROGRESS.md at the repo root with these sections:
- Goal: one or two sentences, plus the acceptance check for the whole task.
- Done: the verified steps, each with the command and result that proved it.
- Next: the ordered steps that remain. The first item is the exact next action.
- Open questions: unknowns and decisions that wait for the user.
- Key facts: paths, commands, versions, gotchas, and approaches that failed (with the reason).
- Update PROGRESS.md after every verified step. Do not update it for unverified ones. Commit the code and PROGRESS.md together with a descriptive message.
- Watch for reset signals: you repeat an earlier answer, you forget a fact that is in Key facts, you retry a fix that failed, the same file gets reread many times, or the context is more than about half full.
- When a signal appears, finish or revert the current step so the tree is in a known state.
- Rewrite PROGRESS.md as a complete handoff. A reader who has only this file and the repo must be able to continue. Remove chatter and keep the facts.
- Start a fresh session or subagent. Give it one instruction: "Read PROGRESS.md and
git log -5, run the acceptance check for the last Done item, then do the first item in Next." - In the new context, confirm that the baseline check passes before you make new edits. If it fails, fix that first.
Stop when
- The goal's acceptance check passes and PROGRESS.md shows every item as Done.
- You have done 3 resets on one Next item without progress. Stop and ask the user, with the file as your report.
Rules
- PROGRESS.md holds facts and evidence, not plans that nobody has checked.
- Keep it under about 150 lines. Move old Done items into a short summary line.
- Never put secrets or tokens in it.
- The fresh context reads the file, not the old transcript.
- Pair with avn-plan-loop for the Next list and with avn-unstick for the failed-approach notes.
04 同仓库更多 Skills
cv
Make a CV or résumé with the user in one of Aeven's forty templates, from bold portrait-cover designs (Black, Slate, Fresh) to classic one-page resumes (Harvard, Tang, Minimal Rule), and deliver it as PDF, Word (DOCX) and Pages. Use for any CV, résumé or curriculum vitae request, when the user picked a template on the Resumes page ("…with the Black resume template"), or when they want an existing CV rebuilt in a new design.
cv
暂无简介
user-only-skill
Prove model-disabled skills stay outside the model catalog.
snapshot-skill
Exercise project skill discovery and loading in snapshot tests.
model-only-skill
Prove user-disabled skills remain available to the model.
editing-cordis-compositions
Use when creating, changing, or validating a Cordis composition for this harness — writing or editing an agent preset, adding or removing a plugin row, deciding whether something belongs to the host composition or to one session, checking whether a preset you authored actually mounts, or diagnosing a row that mounted but contributed nothing.