Skill 06 — Docs Sync (Durable Memory)

Purpose: Convert ephemeral run outputs into durable, human-readable notes:

• •decisions
• •run summaries
• •“what changed and why”
• •pointers to evidence and artifacts

Protocols:

• •[[docs/PROTOCOLS/VAULT_PROBE]]
• •[[docs/PROTOCOLS/EVIDENCE]]
• •[[docs/PROTOCOLS/RUN_LOGGING]]
• •[[docs/PROTOCOLS/PATCH_GATE]]

Tools:

• •[[tools/repl/README]] — patch-gated edits (generate + check + apply)

Inputs (from Orchestrator)

• •Task slug
• •Paths to relevant summaries and artifacts (e.g., test report, changeset summary)

Outputs (must write)

• •updates under:
  • •docs/decisions/ (if a decision was made)
  • •docs/notes/ (run summaries / progress logs)
• •[[docs/skills/06_docs_sync/SUMMARY]]

Run log (recommended)

Create: artifacts/_runs/<timestamp>_06_docs_sync/

Steps

1. •Probe-open the relevant summaries/artifacts (slice only).
2. •If there was a decision, write a note using docs/templates/DECISION_TEMPLATE.md.
3. •Write a short progress note in docs/notes/ that links:
   • •[[../tasks/<task_slug>]]
   • •[[../research/<task_slug>]]
   • •[[../plans/<task_slug>]]
4. •Include evidence pointers and links to run logs.
5. •Write SUMMARY.md describing what notes were created/updated.

Definition of Done

• • Notes are updated/created without duplicating large logs
• • Notes include links and evidence pointers
• • Summary exists