memory-and-handoff
Two-mode skill: (1) session memory — load/persist durable workflow state under .cc10x/ (activeContext, patterns, progress) so context survives compaction; (2) handoff package — portable, secrets-redacted export for a coworker, different tool, or fresh non-cc10x session.
romiluz13 · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add romiluz13/cc10x --skill memory-and-handoff技能说明
name: memory-and-handoff description: | Two-mode skill: (1) session memory — load/persist durable workflow state under .cc10x/ (activeContext, patterns, progress) so context survives compaction; (2) handoff package — portable, secrets-redacted export for a coworker, different tool, or fresh non-cc10x session. allowed-tools: Read Write Edit Bash Grep Glob user-invocable: false
Memory & Handoff
Reference Files
Read only what's needed:
references/memory-model-and-ownership.md— memory surfaces, ownership, promotion, workflow markers; load when deciding which surface holds a piece of state or who may write itreferences/memory-operations.md— permission-free operations, router-only persistence, edit patterns; load when actually reading or writing.cc10x/filesreferences/memory-file-contracts.md— required headings, stable anchors, templates, auto-heal rules; load when creating a memory file or healing a malformed onereferences/context-budget-and-checkpointing.md— context-budget rules, warning signs, checkpoint triggers; load when context is getting heavy or before a compaction/checkpoint decision
Mode: SESSION MEMORY
Memory is an index, not a transcript. Distill decisions, learnings, references, and verification evidence into durable, reusable notes.
Memory Surfaces
| File | Holds |
|---|---|
.cc10x/activeContext.md | current focus, recent changes, decisions, learnings, references, blockers |
.cc10x/patterns.md | reusable project standards, gotchas, conventions, skill hints |
.cc10x/progress.md | current workflow, tasks snapshot, completed items, verification evidence |
.cc10x/workflows/{wf}.json + .events.jsonl | durable orchestration truth (machine-owned, verbatim) |
docs/plans/*, docs/research/* | detailed artifacts; memory points to them |
Ownership
- Router loads and auto-heals memory files before routing or resume
- WRITE agents read memory but do NOT edit
.cc10x/*.md(sole carve-out: bug-investigator's[DEBUG-N]lines) - WRITE agents emit structured
MEMORY_NOTESin their Router Contract - READ-ONLY agents emit
### Memory Notes (For Workflow-Final Persistence) - Router-owned memory-finalize task is the only final writer of memory markdown files
- Router-owned markers (
[DEBUG-RESET: wf:{...}],[cc10x-internal] memory_task_id) are read and respected; agents do not invent replacements
Load (MANDATORY at workflow start)
Read all three: activeContext.md, patterns.md, progress.md.
Re-read before: architectural decisions (patterns.md + activeContext.md ## Decisions), implementation choices (patterns.md + activeContext.md), debugging (all three), planning next steps (progress.md + activeContext.md), claiming completion (progress.md + plan/design/research refs), user says "continue" (all three).
Persist
Emit MEMORY_NOTES in Router Contract:
MEMORY_NOTES:
learnings: ["Key causal insight"]
patterns: ["Reusable gotcha or convention"]
verification: ["`npm test` -> exit 0"]
deferred: ["Non-blocking follow-up or risk"]
Keep each entry one line — memory reloads every session; each extra line is a recurring tax. Prefer stable nouns over temporary wording. Put verification truth in verification, not prose. Put non-blocking work in deferred, not ad-hoc tasks.
Persist only memory-worthy items: decisions that change direction, learnings that prevent mistakes, verification evidence with commands and exit truth, deferred non-blocking issues, plan/design/research references, clarified user standards.
Do not persist: whole diffs, verbose logs, celebratory narration, "looked correct" without evidence, duplicate notes, raw secrets/PII in outward artifacts.
Secret Redaction (OUTWARD artifacts only)
Before router persists cc10x-authored content into outward artifacts (docs/plans/*, docs/research/*, design docs, persisted memory notes): redact pasted tokens, API keys, connection-strings, credentials, PII. Replace with <redacted:secret> (PII: <redacted:pii>). Keep surrounding constraint intact. When unsure, redact. Does NOT apply to internal machine-owned .cc10x/ orchestration state — that stays verbatim for resume/dedupe keys.
Compaction KEEP / SUMMARIZE / DROP Rubric
| Tier | What | Rule |
|---|---|---|
| KEEP | user hard-constraints/prohibitions, exact next step, open failures + errors | preserve VERBATIM — never paraphrase a constraint or error |
| SUMMARIZE | resolved decisions with rationale, concluded attempts, discovered file/module boundaries | distill to one durable line each |
| DROP | decorative prose, step-by-step diary, superseded speculation, redundant prompt retellings | discard |
Persist user PROHIBITIONS verbatim into workflow artifact's intent field as soon as stated — compaction may fire before router's normal persist.
Project Skill Hints
After loading memory, check patterns.md ## Project SKILL_HINTS. Invoke listed skills when relevant and installed. Treat missing skills as non-fatal. Do not invent skill IDs. Do not edit ## Project SKILL_HINTS directly — surface recommendations in planner output or memory notes.
Mode: HANDOFF PACKAGE
A portable, human-readable export for when the next reader is NOT this cc10x session — a coworker, a different tool, or a clean session with no cc10x router.
cc10x's own resume is structural (.cc10x/ + router rehydrates). The handoff package is the bridge OUT to a reader who cannot read .cc10x/ orchestration state.
Rules
- Write to OS temp dir, never into the repo — a repo-committed handoff becomes a stale doc the next reader mistakes for current truth.
HANDOFF="${TMPDIR:-/tmp}/handoff-$(date +%Y%m%d-%H%M%S).md". Print the absolute path. - Reference artifacts by path/URL, never paste contents. The next reader has the repo. They need a map, not a copy. Prefer behavioral descriptions over
file:linewhere co