What problem does it solve? When a delivery initiative closes, its lessons disappear unless someone deliberately extracts them. This Skill reads one closed initiative end to end — its documents, activity telemetry, recorded claims, and ledger row — decides which findings generalise beyond the team, mints platform-scoped knowledge nodes immediately, and proposes team-scoped nodes in a single gated handover document that a person must approve. ## Core Features & Use Cases - Telemetry computation: Mechanically derives end-to-end time, stage timings, question load, effort shape, rework signals, and post-acceptance noise from activity.jsonl before any judgement is made. - Two-shelf knowledge routing: Decides for each finding whether it is a fact about a registry entry (minted immediately with knowledge_add(scope: "platform")) or a fact about this team (proposed in handover.md and minted only after approval). - Two-pass gated workflow: Pass 1 writes the three-section handover.md with a machine-readable proposed_team_nodes count; Pass 2 mints exactly the approved team nodes, with a narrow exception for facts that became false between approval and minting. - Use Case: After an SDLC initiative closes with an outcome recorded in _ledger.md, run this Skill to produce an approvable handover that records plugin defects and refusal classes for every team while proposing stakeholder-specific conduct patterns for this team's own shelf. ## Quick Start Run the zz-handover skill on the closed initiative to compute its telemetry, mint platform knowledge nodes, and write its gated handover document.
