AGENT SKILL

dsh-archive-agent-notes

Use when adding, auditing, pruning, archiving, restoring, or reviewing Agent Notes in deepseek-harness; checks every new note for superseded active records, classifies implemented notes by future decision value, deletes rejected notes that no longer prevent a tempting fallacy, and applies the frozen archived/{kind} triplet and manifest rules.

License 许可
MIT
最近更新
2026-09-10
Stars
★ 0
Forks
0

01 前言 Front Matter

name
dsh-archive-agent-notes
description
Use when adding, auditing, pruning, archiving, restoring, or reviewing Agent Notes in deepseek-harness; checks every new note for superseded active records, classifies implemented notes by future decision value, deletes rejected notes that no longer prevent a tempting fallacy, and applies the frozen archived/{kind} triplet and manifest rules.

02 资源文件 1

03 SKILL.md 正文

Archive DeepSeek Harness Agent Notes

Reduce the active decision corpus without erasing history that can still guide work. Judge every note semantically; word count and age are discovery aids, never archive criteria.

Read the contracts

Read the Agent Note rules, the archive instructions, and the applicable active lifecycle instructions before classifying. Use current code, configuration, package docs, generated catalogs, newer Agent Notes, and inbound links to establish whether a rationale still owns or constrains anything.

Check supersession when adding a note

Every new Agent Note triggers a scoped audit of active notes covering the same decision, mechanism, or rejected alternative. Classify each full or partial supersession while writing the new note: archive qualifying implemented triplets in the same PR, retain and cross-link partial supersessions or independently useful rationale, reject obsolete proposals, and delete rejected notes that no longer prevent a plausible mistake. Apply the Agent Note consolidation rule when the new owner absorbs every unique proposition; do not defer a known match to a later corpus audit.

Classify by future value

Apply these lifecycle-specific outcomes:

  • Implemented — keep active: retain a note when its rationale, alternatives, negative guarantees, durable/wire semantics, ownership boundary, security rule, or reintroduction condition is likely to guide a future change. Length does not matter.
  • Implemented — archive: archive a note when the shipped decision is complete and its body is unlikely to guide future work, such as one-off UI chrome, a narrow adapter, a minor closed bug, superseded implementation detail, or process history whose current behavior is obvious elsewhere.
  • Proposed — never archive: keep a live proposal active; if it is no longer worth pursuing, reject it with an honest reason and satisfy the rejected lifecycle format.
  • Rejected — keep only as a guardrail: retain a rejection only when the losing proposal remains a tempting, meaningful mistake and the note explains why it loses.
  • Rejected — delete: delete the whole triplet when the rejected idea is obsolete, superseded, no longer plausible, or unlikely to prevent re-litigation. Repair or delete inbound links.

Do not archive toward a quota. Inspect every note in scope, classify analogous groups under one principle, use best judgment for close cases, and record genuinely borderline decisions for the handoff.

Calibrated examples

These examples set the bar; the word counts demonstrate that size is not the test.

Archive implemented notes such as:

  • collapsed sidebar control rail — 533 words: closed, minor UI behavior;
  • Commander argument adapter — 1,498 words: substantial implementation detail with little future design leverage;
  • documentation graph atlas — 920 words: completed documentation machinery whose current generators are authoritative.

Keep implemented notes such as:

  • event-sourced sessions — 248 words: foundational authority and durability boundary;
  • single Harness-home resolver — 596 words: cross-product ownership rule;
  • project session directories — 628 words: durable storage and identity policy;
  • parallel pre-push gates — 400 words: borderline, but still guides gate scheduling and resource tuning;
  • dropped image content block — 334 words: keep until multimodal support lands, because it states the coordinated reintroduction condition.

For rejected notes:

  • keep folding the compaction package split — 426 words: the temptation to merge the packages remains meaningful;
  • delete streaming workflow progress through tool calls — 972 words: its ACP/UI premise is obsolete;
  • delete dropping ACP terminal metadata — 362 words: the later automation-only ACP decision resolved the question.

Archive one implemented triplet

  1. Move the complete foo.md, foo.zh.md, and foo.i18n.yaml triplet from implemented/<kind>/ to archived/<kind>/; implemented is deliberately absent from the archive path.
  2. Make no body edits. Insert only Archived: YYYY-MM-DD immediately below Status: implemented in both language files, using the archival date and the same value on both sides.
  3. Re-record the sidecar hashes mechanically for the two metadata-only edits. Do not translate, reformat, update facts, or repair links inside the note.
  4. Search for inbound links from active prose. Redirect them to current authority, retarget them to the archived path only when the historical snapshot is intentionally cited, or delete them. Never verify or repair links out of the archived note.
  5. Run pnpm run verify-archived-agent-notes --write. Its append-only mode first proves every existing seal still matches, then adds only the new triplet hashes. Run the normal verifier afterward.

After the triplet is sealed, never edit, move, translate, reformat, or delete it. Archived notes remain valid inbound-link targets but are historical snapshots, not authority for current behavior.

Validate and report

Run the archive verifier's focused test, pnpm run verify-archived-agent-notes, pnpm run doc-sync, pnpm run lint, and git diff --check; select any additional evidence through dsh-pre-push-checks.

Report active implemented notes kept, implemented notes archived, rejected notes kept/deleted, proposed notes rejected if any, and every genuinely borderline case with its word count and chosen outcome. Do not claim archived outbound links are valid: the archive verifier intentionally never checks them.

04 同仓库更多 Skills

Qiuzixiao
Qiuzixiao/deepseek-harness-desktop

short-drama-domain

Short-drama project object map and task routing. Use when the user works with screenplay artifacts, episode scenes, continuity, diagnosis, revision, or delivery. This skill provides operational vocabulary and questions, not a mandatory writing style.

★ 0
Qiuzixiao
Qiuzixiao/deepseek-harness-desktop

creative-project-organization

从梗概开始创作、生成设定/人物/大纲/正文等文件时,在首批落盘前规划内容分组和保存位置;新增独立交付物时复核布局。自动适配项目语言和命名习惯,也用于用户要求的项目整理。无需用户提出归档要求。

★ 0
Qiuzixiao
Qiuzixiao/deepseek-harness-desktop

skill-sink

技能沉淀机制:把创作中验证有效的经验、方法论与个人文风,提炼成可复用的 DSH skill。当创作中发现可复用经验、用户要沉淀个人文风、或要把反复出现的规则固化成技能时使用。

★ 0
Qiuzixiao
Qiuzixiao/deepseek-harness-desktop

short-drama-zonggang

短剧创作总纲与情绪账务引擎方法论。以「恨账—存债/付息/兑付」债务系统为内核,覆盖选题、故事骨架、压爽循环与卡点、付费闸门、台词正文格式、验收自检与失效模式库。当用户要创作短剧剧本、立项选题、写分集大纲、写正文台词、设计付费卡点,或评审/修改/验收短剧时,先加载本 Skill。

★ 0
Qiuzixiao
Qiuzixiao/deepseek-harness-desktop

short-drama-structure

把已确认的故事前提排成短剧四幕二十拍、分集节奏和场次骨架(4×5 节拍表、卡点与高潮兑现)。当用户已有故事梗概,要求拆成四幕/20 拍/分集/场次表、中段松散需要重排转折,或想设置悬念、反转、付费卡点及高潮兑现路径时使用。不适用于从零提炼创意、单场对白润色或平台投稿咨询。

★ 0
Qiuzixiao
Qiuzixiao/deepseek-harness-desktop

short-drama-scene

当用户提供剧本片段、分场或对白,要求更可拍/更有戏/减少解释/改得口语化时调用;重点处理单场冲突、动作进出、状态变化、信息差、潜台词和对白瘦身。不适用于从零搭故事结构、设计整部剧的悬念卡点或行业投稿咨询。

★ 0