360 Secure SkillHub
360 安全技能中心

harvest

用于阶段、任务、评审收尾或切片收尾等连贯单元结束时的归档流程:分别梳理产出(工作增量、风险与后续动作)、经验(可复用指引)和未决事项(决策、问题、假设、约束),路由到各自的持久位置,并按规范维护所属切片的 Harvest 小节。

davidlee
热度 0.00
最近更新 2026-10-18 16:53:30
分类:知识依赖:读写文件应用场景:笔记整理 / 摘要总结 / 任务管理 / 工作流

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add davidlee/doctrine/harvest
Metadata
name
harvest
description
Use at the end of any coherent unit — a phase, task, review close, or slice wrap — to sweep what the unit produced, learned, and left open into their durable sinks, and to maintain the Harvest section of the governing slice's notes.

Harvest

The routed entry point for the end-of-unit harvest — the sweep of what the unit produced, learned, and left open into their durable sinks. The procedure, the three legs, and the sink table are owned by lib:reference/harvest.md; consult it and follow it. Do not re-derive the routing here — point there.

During execution, working notes belong in the active runtime phase sheet (state/.../phases/phase-NN.md) — disposable working context. The harvest is the wrap-up sweep that moves what matters into durable homes; the slice's notes.md (doctrine slice notes <ID> scaffolds it on demand) carries the durable prose. Honour the storage rule: live progress lives in the state tree, never in authored files.

If you don't know which slice owns the work, find it with doctrine slice list. No governing slice (an RFC, spec, or review close)? The harvest still happens — the legs route to their sinks per lib:reference/harvest.md §5; there is just no ## Harvest manifest to maintain.

The three legs

  • produced — the work delta. Be concise, but record:
    • what's done
    • any:
      • surprises encountered or adaptations required
      • potential rough edges, omissions, or refactorings for later
      • follow-up actions advisable
      • open questions relating to completed or upcoming work
      • durable facts, patterns, or gotchas that should become a memory
      • relevant commit hash(es), or: uncommitted work
      • whether .doctrine changes were committed promptly per repo doctrine, or are still pending and why
      • if committed, whether they went out with code or separately when that matters for the next agent
    • whether the verification gate (doctrine check gate) has run successfully since code was last modified, or: outstanding errors
  • learned — reusable guidance and citable epistemic observations, routed to their sinks per lib:reference/harvest.md.
  • open — the decisions, questions, assumptions, and constraints the unit carries forward. This is the leg a produced-only sweep silently drops: route it via /knowledge (→ DEC / QUE / ASM / CON).

Each leg's sink is owned by lib:reference/harvest.md's §2 table — cite it, don't restate it.

## Harvest maintenance

Update the ## Harvest section per lib:reference/harvest.md § Canonical output.